Common Google Merchant Center Setup Mistakes WooCommerce Stores Make

Common mistakes when setting up Google Merchant Center

Setting up Google Merchant Center may initially appear straightforward.

You create an account, enter your business details, connect your online store and submit your WooCommerce products. However, completing these steps does not automatically mean that the account and products are ready to appear across Google.

Merchant Center evaluates more than the product information submitted through a feed or API.

Google may also review:

• The identity of the business
• The information displayed on the website
• The product pages
• Prices and availability
• Shipping conditions
• Return and refund information
• Contact details
• Checkout functionality
• Website security
• Product images
• Product identifiers
• Target countries
• Data sources
• Compliance with Shopping policies

A store can therefore submit technically valid product information and still encounter limited visibility, product disapprovals or an account-level restriction.

Many Merchant Center problems begin with small setup mistakes. The business name may be written differently on the website and in Merchant Center. A return policy may exist but be difficult to find. Shipping costs may be configured in WooCommerce but not accurately communicated to Google. An old product source may continue updating the same catalogue.

The safest approach is to treat Merchant Center setup as a complete store-readiness process rather than a simple product-upload task.

This guide explains the most common Google Merchant Center setup mistakes made by WooCommerce store owners and how to correct them before they develop into larger account problems.

Starting before the WooCommerce store is ready

One of the most common mistakes is opening Merchant Center while the online store is still under construction.

The website may contain:

• Placeholder text
• Demonstration products
• Broken links
• Empty categories
• Missing product images
• Unfinished policy pages
• Incomplete contact information
• Non-working buttons
• Test payment methods
• Pages copied from the theme demonstration
• Products that cannot be purchased
• Maintenance notices
• Inconsistent languages
• Default WooCommerce content

Google’s professional and editorial requirements identify unfinished websites, broken links, placeholder content and incomplete product information as examples of websites that may need improvement. Google Merchant Center editorial and professional requirements

Before connecting the store, browse it as a new customer.

A visitor should be able to understand:

• Who operates the store
• What the store sells
• How to contact the business
• Where the business operates
• How much each product costs
• Whether products are available
• How delivery works
• How returns and refunds are handled
• Which payment methods are accepted
• What happens after placing an order

Merchant Center should not be used as a testing environment for an unfinished ecommerce website.

Entering inconsistent business information

The business information submitted to Merchant Center should agree with the information available on the website.

Common inconsistencies include:

• Using a brand name in Merchant Center and another company name on the website
• Entering an old business address
• Displaying different telephone numbers
• Using an email address that is not associated with the business
• Omitting the legal business name
• Showing conflicting addresses in the footer and contact page
• Leaving customer-service fields incomplete
• Using different spellings of the business name

For example, Merchant Center may identify the store as “Example Commerce Ltd,” while the website footer shows only “Best Price Store.” If no page explains the relationship between these names, customers and Google may have difficulty confirming who operates the business.

Google advises merchants to provide business details such as the business name and registered address in Merchant Center. Its guidance for missing contact information also emphasises consistency between Merchant Center, the website footer and the contact page. Google business information guidance, Google missing contact information guidance

Check the following locations together:

• Merchant Center business information
• Website header or footer
• Contact page
• About page
• Terms and conditions
• Privacy policy
• Return and refund policy
• WooCommerce store address
• Invoice information
• Customer-service email
• Social-media business profiles

The information does not need to be repeated unnaturally on every page, but it should tell one consistent business story.

Failing to verify the online store

Merchant Center needs confirmation that the account has authority over the submitted online store.

A website-verification problem may occur when:

• The wrong domain is entered.
• The www and non-www versions are confused.
• HTTP is used instead of HTTPS.
• A verification tag is missing.
• A theme update removes the verification code.
• The Google Analytics account belongs to another user.
• The required Google account lacks permission.
• An agency or old Merchant Center account has already claimed the domain.
• A staging domain is entered instead of the production domain.
• The store changes domains without updating Merchant Center.

Google explains that verification and claiming are important parts of Merchant Center setup and supports methods including an ecommerce platform, email, an HTML tag or file, Google Tag Manager and Google Analytics. Google online store verification guidance

Confirm the exact public domain before submitting products.

If the store operates at https://www.example.com, the Merchant Center configuration, product links and image links should consistently use the intended live website.

Do not create multiple Merchant Center accounts merely to overcome a domain-verification problem. Another account may already have a higher-level claim over the same domain. Identify and resolve the existing claim instead. Google unverified store URL guidance

Providing insufficient contact information

Customers should be able to contact the business before completing a purchase.

A social-media profile alone may not provide enough confidence. Likewise, a contact form that never confirms submission or an email address hidden only in the privacy policy creates a poor customer experience.

Useful contact information may include:

• Business name
• Physical business address
• Customer-service email
• Telephone number
• Working contact form
• Customer-service hours
• Expected response time

The contact page should be easy to reach from the main navigation or footer.

Test every contact method. Send a message through the form, check whether the notification arrives and confirm that the displayed telephone number is correct.

Google lists insufficient contact information among common warning and suspension causes. Its guidance states that customers should be able to find contact details and that Merchant Center business information should also be completed. Google warning and suspension guidance

Using an unclear return and refund policy

A return policy should explain the real process followed by the business.

A short statement such as “Returns are accepted” is often insufficient because it does not answer essential customer questions.

A complete policy should clarify:

• Whether returns are accepted
• The return period
• When the return period begins
• Which products cannot be returned
• Required product condition
• How to request a return
• Where the product should be sent
• Who pays return delivery costs
• Whether original shipping costs are refunded
• How refunds are issued
• How long refunds take
• How damaged or incorrect products are handled
• Whether exchanges are available
• What happens when returns are not accepted

The policy must also reflect the business’s actual practices and applicable law.

Do not copy a return policy from an unrelated store. It may mention another country, currency, company name, return address or product category.

Google’s misrepresentation guidance identifies unclear, missing or difficult-to-find return and refund information as a potential problem. It also refers to missing terms and shipping information. Google Merchant Center misrepresentation policy

Place the policy where customers can find it before purchasing, normally in the website footer and relevant checkout areas.

Leaving shipping information incomplete

WooCommerce shipping settings and Merchant Center shipping settings serve related but different purposes.

WooCommerce calculates the amount customers see and pay. Merchant Center needs shipping information that accurately represents those customer-facing conditions.

Common mistakes include:

• Configuring shipping only in WooCommerce
• Forgetting to add shipping information in Merchant Center
• Selecting the wrong delivery country
• Submitting a lower shipping cost than the website charges
• Advertising free shipping when conditions apply
• Omitting remote-area surcharges
• Using unrealistic delivery times
• Confusing processing time with transit time
• Applying one shipping rule to products that require different delivery methods
• Failing to update Merchant Center after changing WooCommerce rates

For example, Merchant Center may show free delivery while checkout charges $9. Customers then encounter a commercial condition that differs from the listing.

Google’s product-data specification requires applicable shipping information, and Google also provides country-specific shipping requirements for free listings. Google product-data specification, Google free-listing requirements

Test several realistic orders:

• A low-value order
• An order above the free-shipping threshold
• A heavy product
• A remote delivery address
• An international destination
• A product with a special shipping class

The Merchant Center estimate should not promise a better condition than the customer actually receives.

Selecting the wrong target country, language or currency

Products should be submitted for the market they genuinely serve.

A store may incorrectly:

• Target a country it does not deliver to
• Submit EUR while the landing page defaults to USD
• Use English product information with an unrelated landing-page language
• Redirect Google’s visitor to another country
• Display location-based prices that differ from the submitted amount
• Use delivery information belonging to another market
• Apply the wrong tax treatment
• Send all countries through one uncontrolled product source

The submitted product, landing page and checkout should provide a consistent experience for the target customer.

If a product targets Germany in EUR, the visitor should be able to see the correct EUR price and complete delivery to Germany under the submitted conditions.

International selling should be introduced carefully. A store that is not ready for several countries should begin with the market it can serve accurately.

Submitting products with incomplete information

A published WooCommerce product is not automatically ready for Merchant Center.

Common missing or inaccurate fields include:

• Price
• Availability
• Main image
• Brand
• GTIN
• MPN
• Condition
• Description
• Colour
• Size
• Age group
• Gender
• Item group ID
• Product URL
• Variation attributes

Requirements vary according to product type and target country.

A handmade product without a genuine GTIN should not be assigned an invented number. Conversely, a branded retail product that has an official GTIN should not have that identifier omitted.

Product information should describe the real item rather than simply completing every field with a guessed value.

PW Merchant API can transfer WooCommerce product information, but the original WooCommerce record must first be accurate and complete.

Using weak product titles and descriptions

A title such as “New Product 01” does not help Google or the customer understand the offer.

Product titles should naturally identify relevant characteristics such as:

• Brand
• Product type
• Model
• Material
• Colour
• Size
• Capacity
• Intended use

Descriptions should explain the product accurately without keyword repetition, exaggerated claims or unrelated promotional language.

Avoid:

• Writing titles entirely in capital letters
• Repeating the same keyword unnaturally
• Adding “free shipping” to every title
• Using excessive symbols
• Copying one description across unrelated products
• Hiding essential variation information
• Making claims unsupported by the product page

The product title submitted to Merchant Center should also describe the product available on the linked page.

Sending the parent price for every variation

Variable WooCommerce products require special care.

Consider a product with three variations:

Variation	Price	Stock
Small, black	$40	In stock
Medium, black	$50	In stock
Large, white	$65	Out of stock

Submitting every variation at $40 and marking all of them in stock would be inaccurate.

Each genuine variation should preserve its own:

• Variation ID
• Price
• Sale price
• Availability
• Image
• Colour
• Size
• Product link or selectable state

The customer should be able to reach and identify the same option that was submitted.

A parent product’s lowest displayed price should not automatically become the price of every variation.

Allowing website and submitted values to disagree

Google may compare submitted information with the customer-facing website.

Common conflicts include:

• Merchant Center price differs from the product page.
• Submitted availability differs from WooCommerce.
• Structured data contains an old price.
• The cart changes the product price.
• Checkout applies mandatory charges not clearly disclosed.
• An expired sale remains active in Merchant Center.
• The public page is cached.
• A currency plugin displays another currency.
• Location-based pricing changes the amount.
• A variation cannot be selected at the submitted price.

After updating a product, compare:

Source	Information to confirm
WooCommerce	Price, sale price and stock
Public product page	Visible price and availability
Structured data	Price, currency and availability
PW Merchant API	Prepared product value
Merchant Center	Submitted and processed value
Cart and checkout	Final product price

The values should describe the same offer.

Using poor or inaccessible product images

Product images should clearly show the advertised item.

Common problems include:

• Placeholder images
• Broken URLs
• Images blocked by the CDN
• Images accessible only to logged-in users
• Very small images
• Blurred photographs
• Excessive promotional text
• Unrelated background graphics
• An image belonging to another variation
• Watermarks that obscure the product
• Temporary image URLs
• HTTP images on an HTTPS website

Open the submitted image URL in a private browser window.

If the image cannot be viewed without authentication, Google may also be unable to process it.

Each variation should use an appropriate image when colour, pattern or another visible characteristic changes.

Connecting more than one product source without a plan

Merchant Center can receive products from several sources, including:

• Merchant API
• XML files
• Google Sheets
• Manual products
• Ecommerce integrations
• Website-discovered products
• Previous plugins

Multiple sources are not automatically wrong. The problem begins when two primary sources attempt to control the same products.

For example:

1. PW Merchant API submits a product at $80.
2. An old XML feed later submits it at $90.
3. The website still shows $80.
4. Merchant Center processes conflicting information.
5. The product develops a price mismatch.

Review every active data source before completing the setup.

If PW Merchant API will manage the WooCommerce catalogue, establish whether any older feed or integration still has a legitimate purpose. Do not leave duplicate sources running simply because products appear to have been submitted successfully.

Leaving a staging store connected

A staging copy may retain:

• Google authorisation
• Merchant Center account details
• Product IDs
• Scheduled jobs
• Old stock quantities
• Old prices
• PW Merchant API settings

The staging website can then update production products with outdated information.

Merchant Center operations should be disabled on development and staging copies. Only the intended live WooCommerce store should control the production catalogue.

Requesting a review before correcting everything

When Merchant Center displays an account or product issue, merchants may immediately request a review.

This can be a mistake if the website still contains incomplete information.

Before requesting a review:

• Read the exact issue.
• Inspect the entire website.
• Correct every related problem.
• Test contact methods.
• Test checkout.
• Confirm shipping costs.
• Confirm return information.
• Remove placeholder content.
• Fix broken links.
• Correct product data.
• Clear caches.
• Confirm the public result while logged out.

Google states that products or accounts may receive warnings, disapprovals or suspension when the website or submitted product information does not meet applicable requirements. A review should therefore follow the completed correction, not replace it. Google Merchant Center review guidance

Do not repeatedly request reviews without meaningful changes.

Assuming API success means approval

A successful PW Merchant API operation means that Google accepted the product information for processing.

It does not guarantee:

• Product approval
• Account approval
• Free-listing eligibility
• Shopping-ads eligibility
• Immediate visibility
• Impressions
• Clicks
• Sales

Google still evaluates the processed product, website, account and applicable policies.

PW Merchant API helps manage the communication between WooCommerce and Merchant Center. It cannot convert incomplete, contradictory or misleading store information into an approved offer merely by sending it successfully.

How to check your setup before submitting products

Use the following process before activating full catalogue submission.

1. Inspect the website as a customer

Browse the store while logged out.

Confirm that navigation, categories, product pages, cart, checkout and policy links work correctly.

2. Compare business information

Ensure the business name, address, telephone number and email are consistent across Merchant Center and the website.

3. Verify the live domain

Confirm that the correct production website is verified and that no obsolete account controls the domain.

4. Review policy pages

Check shipping, returns, refunds, privacy, terms and contact information.

Make sure the policies describe the real business.

5. Test several products

Select a simple product, a sale product and a variable product.

Compare their price, availability, images, identifiers and checkout behaviour.

6. Check shipping and delivery

Test several order values and delivery locations. Confirm that Merchant Center does not display a lower cost or shorter delivery time than the store provides.

7. Review product sources

Identify every system capable of adding or updating products.

Remove or disable obsolete conflicts.

8. Submit a controlled group

Begin with a manageable selection of complete products instead of using an unreviewed catalogue as the first test.

9. Read Merchant Center results

Check products that need attention, account issues, processing status, countries and marketing methods.

10. Correct the source

When an issue appears, correct WooCommerce, the website or the applicable configuration. Then update the existing product while preserving its stable identity.

How PW Merchant API supports a safer setup

PW Merchant API provides a WooCommerce-focused method for communicating product information through Google Merchant API.

Its role may include:

• Reading WooCommerce products
• Distinguishing simple and variable products
• Preparing supported product information
• Preserving stable product IDs
• Sending products to the selected Merchant Center account
• Updating existing products
• Processing controlled workloads
• Showing operation results
• Identifying failed submissions
• Helping merchants review products needing correction
• Reducing dependence on manually maintained feed files

The intended structure is:

WooCommerce stores the real product information, PW Merchant API communicates that information, and Google Merchant Center processes and evaluates it.

The plugin is one part of a complete Merchant Center setup.

The website must still be trustworthy, accessible and functional. Business details must remain consistent. Policies must be clear. Shipping must be accurate. Product pages, structured data, cart and checkout must confirm the submitted information.

Frequently asked questions

What is the most common Google Merchant Center setup mistake?

There is no single cause for every store, but beginning with an incomplete website is one of the most damaging mistakes. Missing policies, inconsistent business information, broken pages and non-working checkout can affect the entire account.

Does WooCommerce automatically make a store ready for Merchant Center?

No. WooCommerce provides ecommerce functionality, but the merchant must correctly configure products, payments, shipping, taxes, policies, contact information and the public customer experience.

Why was my Merchant Center account rejected after products were submitted?

Product submission and account approval are separate stages. Google may identify website, business-information, policy, checkout or product-data problems after receiving the catalogue.

Can PW Merchant API guarantee Merchant Center approval?

No. It can send and update WooCommerce product information through Merchant API, but Google determines final approval and visibility.

Do I need a return policy if I do not accept returns?

The website should clearly explain that returns are not accepted and describe any exceptions or legally required customer rights. Leaving the subject unanswered is not a clear policy.

Should my business address be displayed on the website?

Business information should be complete, accurate and consistent with Merchant Center. Applicable disclosure requirements may also depend on the business location and relevant law.

Can incorrect shipping information cause product disapproval?

Yes. Missing or inaccurate shipping information can limit products and create a customer experience that differs from the advertised offer.

Can I use several Google Shopping plugins together?

Technically, different tools may serve distinct purposes, but two systems should not unknowingly control the same Merchant Center products. Conflicting sources can overwrite price, availability and other product information.

Should I submit every WooCommerce product immediately?

A controlled first submission is safer when the catalogue has not been audited. Review a representative group of complete products before expanding the operation.

Does successful product submission mean the product will appear on Google Shopping?

No. It means the information was accepted for processing. Google must still evaluate the processed product and determine eligibility for the intended marketing method.

Should I request a review immediately after receiving a warning?

First identify and correct every applicable issue. Requesting a review before the website and product information are genuinely ready can waste the review opportunity.

Can an old Merchant Center account affect a new setup?

Yes. An old or automatically created account may still claim the domain or contain an active product source. Check existing accounts before creating duplicates.

Final Google Merchant Center setup checklist

Before considering the setup complete, confirm that:

• The WooCommerce store is publicly available.
• The website does not contain placeholder content.
• Broken links have been corrected.
• The store works on desktop and mobile.
• The correct live domain is used.
• The domain is verified.
• No unwanted account controls the domain.
• The business name is accurate.
• The business address is accurate.
• Contact information is visible.
• Contact methods work.
• Merchant Center and website details agree.
• The return and refund policy is complete.
• Shipping information is easy to find.
• Terms and conditions are available.
• Privacy information is available.
• Product pages are publicly accessible.
• Products have valid prices.
• Availability information is accurate.
• Products can be added to the cart.
• Checkout works correctly.
• Required payment methods work.
• Shipping costs match the advertised conditions.
• Delivery times are realistic.
• Target countries are intentional.
• Currency is consistent.
• Tax treatment is appropriate.
• Product titles are accurate.
• Product descriptions are useful.
• Product images are accessible.
• Genuine product identifiers are submitted.
• Invented identifiers are not used.
• Variations have their own correct information.
• Structured data agrees with the visible page.
• Old product sources have been reviewed.
• Staging websites cannot update production products.
• The correct Merchant Center account is selected.
• PW Merchant API uses the intended account.
• Initial test products have been reviewed.
• Product and account issues have been corrected.
• A review is requested only after meaningful corrections.

Build Merchant Center on a reliable store foundation

A successful Google Merchant Center setup begins before the first product is submitted.

The online store should clearly identify the business, provide working contact methods, explain delivery and returns, display accurate product information and allow customers to complete a secure purchase.

WooCommerce should remain the reliable source of commercial product information. PW Merchant API should communicate that information through Google Merchant API. Merchant Center should then receive values that the product page, structured data, cart and checkout can confirm.

Avoid treating individual warnings as isolated technical messages.

A missing shipping cost may reveal an incomplete delivery structure. A price mismatch may reveal a caching or variation problem. A domain-verification error may reveal that an older account still controls the website. A misrepresentation concern may indicate that the overall business information is incomplete or inconsistent.

Correcting these foundations creates more than a technically valid Merchant Center account.

It creates a clearer ecommerce experience for customers.

By preparing the WooCommerce store carefully, using consistent business information, publishing transparent policies, testing checkout, managing product sources and submitting accurate product data, merchants can reduce avoidable setup errors and build a more reliable connection between their store and Google Shopping.