How to Fix Google Merchant Center Misrepresentation in WordPress and WooCommerce

Many WordPress and WooCommerce store owners experience Google Merchant Center account suspension, product disapproval or restrictions that prevent their products from appearing in Google Shopping ads and free listings.

Merchant Center may display a general issue such as:

• Misrepresentation.
• Account suspended due to policy violation.
• Website or online store needs improvement.
• Missing business information.
• Price mismatch.
• Availability mismatch.
• Missing return and refund policy.
• Products have limited visibility.

The most challenging part is that Google does not always identify the exact page, product or technical setting responsible for the suspension.

As a result, merchants may make random website changes, install a different product feed plugin or submit repeated review requests without correcting the underlying problem.

Fixing Google Merchant Center for a WooCommerce store requires a complete review of the website, business information, policies, product data, structured data, shipping settings and checkout experience.

This guide explains the most common reasons for Merchant Center suspension on WordPress and WooCommerce and how to prepare the store correctly before requesting another review.

WordPress allows store owners to install different themes, product feed tools, SEO plugins, currency converters and checkout extensions.

This flexibility is valuable, but it can also create conflicting information.

For example:

• WooCommerce may show one price while a feed plugin submits another.
• The product page may show an item as available while Product Schema says it is out of stock.
• Two plugins may submit the same products to Merchant Center.
• A currency plugin may display a different currency to Googlebot.
• A cache plugin may prevent Google from seeing updated prices.
• A multilingual plugin may submit the wrong product URL.
• A security plugin may prevent Google from crawling product or policy pages.

A proper WooCommerce Merchant Center audit should therefore include:

• Business information.
• Website policies.
• WooCommerce settings.
• Google integration plugin.
• Product data sources.
• Product Schema.
• Product prices.
• Product variations.
• Inventory.
• Currencies and taxes.
• Shipping settings.
• Cart and checkout.
• Googlebot accessibility.

Misrepresentation is a Google Merchant Center policy classification used when a store, business, product or purchasing condition is not presented with sufficient accuracy, consistency or transparency.

A Misrepresentation suspension does not always mean that a merchant is intentionally deceiving customers.

The issue can also occur when Google cannot verify the business or finds conflicting information between the website, Merchant Center, product data and checkout.

Potential causes include:

• Missing business information.
• An unverifiable business address.
• Different business names across the website and account.
• Incomplete shipping information.
• An unclear return and refund policy.
• Unexpected checkout fees.
• Incorrect product prices.
• Incorrect availability information.
• Misleading discounts.
• Unclear subscription conditions.
• Unauthorized brand claims.
• Products that cannot be purchased in the target country.
• Fake reviews or trust badges.

Google’s official Misrepresentation policy explains the types of business and offer information merchants must present accurately.

Before making changes, determine whether the issue affects individual products or the complete account.

The Merchant Center account remains active, but one or more products cannot appear because of issues such as:

• Price mismatch.
• Availability mismatch.
• Invalid image.
• Incorrect GTIN.
• Missing product attributes.
• Broken landing page.
• Restricted product.
• Incorrect shipping information.

These errors usually appear in the Needs attention section inside Merchant Center.

A group of products may be rejected because they share the same error, such as:

• Missing size or color.
• Incorrect product category.
• Unsupported product variations.
• Broken image URLs.
• Incorrect brand or GTIN data.
• An outdated product feed.

A full suspension affects all or most products and can prevent the store from using Shopping ads and free listings until the website and account pass another review.

One of the most common WooCommerce problems is using multiple product feed integrations at the same time.

Examples include:

• Google for WooCommerce.
• Google Product Feed.
• An XML product feed plugin.
• A third-party catalog integration.
• A custom Content API connection.
• A product source created automatically by Google.

This may result in the same product being submitted more than once with different IDs, prices, currencies or availability values.

Select one primary product data source and investigate any old or duplicate sources.

Do not immediately delete a product source without identifying the products and advertising campaigns connected to it. Removing the wrong source may cause active products to disappear from Google Shopping campaigns.

The official Google for WooCommerce extension can automatically synchronize WooCommerce products with Google Merchant Center.

According to WooCommerce documentation, synchronization depends on WooCommerce’s Action Scheduler system.

Synchronization may fail because of:

• WP-Cron not running.
• Failed scheduled actions.
• A REST API error.
• A security plugin blocking external requests.
• Incorrect server configuration.
• A PHP compatibility problem.
• A plugin conflict.
• A database issue.
• An expired Google account connection.
• Low WordPress memory limits.
• A server timeout.

Review scheduled actions from:

WooCommerce → Status → Scheduled Actions

Look for failed, pending or overdue tasks related to Google product synchronization.

Fix the underlying WordPress or server problem before forcing another complete product sync.

WooCommerce explains the synchronization process in the official Google for WooCommerce documentation.

The price should match across:

• WooCommerce product page.
• Product structured data.
• Product data source.
• Shopping cart.
• Checkout.
• Google Merchant Center.

A price mismatch can occur because of:

• Taxes being added during checkout.
• A multi-currency plugin.
• An expired sale price.
• An outdated cache.
• Incorrect variable product pricing.
• Customer-role pricing.
• Location-based pricing.
• Automatic cart discounts.
• Product bundles.
• Mandatory fees.
• Product Schema showing an old price.
• Product feed synchronization delays.

After updating a price:

1. Clear WordPress page cache.
2. Clear object cache.
3. Clear CDN cache.
4. Check the product’s visible price.
5. Test Product Schema.
6. Update or synchronize the product source.
7. Confirm the corrected price inside Merchant Center.
8. Test the final checkout total.

Automatic item updates may temporarily help Google correct some price differences, but they should not be used as a replacement for accurate source data.

Each purchasable product variation should include accurate information.

For example, every color or size variation may need:

• A valid landing page.
• A correct price.
• Accurate availability.
• A suitable image.
• A unique SKU.
• A valid GTIN, when available.
• Color and size information.
• A shared item_group_id.

If the white variation is out of stock, it should not be submitted as available simply because the main variable product is still active.

The product URL should also select or clearly identify the submitted variation where required.

Google must be able to match the submitted price, color, size and availability with the same variation on the landing page.

This is not always an error.

A variable WooCommerce product may contain several separately submitted variations.

For example:

10 simple products
1 variable product with 5 variations

Merchant Center may receive:

15 individual items

However, if the product count is significantly higher than expected, check for:

• Duplicate product data sources.
• Multiple feed plugins.
• Products submitted for several countries.
• Products submitted for several languages.
• Old products that were not removed.
• Duplicate Content API connections.

If a product is submitted as:

in_stock

the customer should be able to add it to the cart and complete the purchase.

Availability mismatches may be caused by:

• Delayed feed updates.
• Failed synchronization.
• External inventory systems.
• Old cached product pages.
• Incorrect variation stock.
• Backorders not configured correctly.
• A product available in WooCommerce but unavailable in the target country.
• Stock managed at the parent product level instead of the variation level.

Use the correct availability values:

in_stock
out_of_stock
preorder
backorder

If a product is permanently discontinued, remove it from the product data source rather than continuing to submit it as out of stock indefinitely.

Google explains the correct use of product availability in its official availability attribute documentation.

Product structured data helps Google understand the information displayed on WooCommerce product pages.

Important properties include:

• Product name.
• Description.
• Image.
• Price.
• Currency.
• Availability.
• Condition.
• Brand.
• SKU.
• GTIN.
• MPN.

The most important values for automatic price and availability updates include:

price
priceCurrency
availability
condition

Product Schema conflicts may occur when:

• The theme generates Product Schema.
• An SEO plugin generates another Product object.
• A review plugin generates duplicate Product Schema.
• A custom code snippet contains an old price.
• A currency plugin modifies the visible price but not the Schema.
• An AMP version shows different product data.
• The sale price is missing from Schema.
• A cache plugin serves outdated structured data.
• Schema represents the parent product instead of the selected variation.

Test product pages using Google’s Rich Results Test, then compare:

• Visible product price.
• Product Schema price.
• Submitted product price.
• Merchant Center price.
• Checkout price.

Google states that accurate structured data helps automatic item updates and reduces product disapprovals caused by price and availability mismatches. Review Google’s structured data requirements for Merchant Center.

A currency switcher may show prices in USD, SAR, AED, EGP or another currency depending on the customer’s location.

This can create a mismatch if:

• WooCommerce uses one base currency.
• The product feed submits another currency.
• Googlebot sees a third currency.
• Product Schema contains the store’s default currency.
• Checkout changes the currency again.
• Location detection does not work consistently.

Review:

• WooCommerce base currency.
• Target country currency.
• Submitted product currency.
• Product Schema currency.
• Currency visible to Googlebot.
• Checkout currency.
• Tax inclusion settings.

The official Google for WooCommerce documentation currently explains that product synchronization primarily uses the store’s main currency and may not provide full compatibility with every multi-currency extension.

Do not assume that currency conversion is configured correctly simply because customers can change currencies manually.

WordPress stores may use multilingual plugins such as:

• WPML.
• Polylang.
• TranslatePress.
• Weglot.

Potential problems include:

• Only the primary language being submitted.
• Duplicate products.
• An Arabic landing page with an English description.
• Incorrect canonical URLs.
• The same product ID used across several language versions.
• Different availability between translations.
• Incorrect language-country combinations.
• A translated page displaying an outdated price.

Check the actual products and URLs inside Merchant Center instead of assuming that every translated version is synchronized correctly.

For international stores, each submitted language and country combination should lead to a compatible product page and purchasing experience.

Your website should clearly identify the business operating the store.

Provide:

• Business or legal name.
• Valid business address.
• Working phone number.
• Professional email address using the store’s domain.
• Contact Us page.
• About Us page.
• Business registration information where applicable.
• Customer service hours where relevant.

The details should be consistent across:

• Website footer.
• Contact page.
• About page.
• Merchant Center.
• Google Ads.
• Payment profiles.
• Customer invoices.

Do not use a fake address to appear established in the target country. All business information should be accurate and verifiable.

Google provides additional guidance for resolving missing contact information.

A WooCommerce store should include:

• Shipping and delivery policy.
• Return and exchange policy.
• Refund policy.
• Order cancellation policy.
• Privacy policy.
• Terms and conditions.
• Subscription and cancellation policy, if applicable.
• Contact Us page.
• About Us page.

Place links to these pages in the website footer so customers can access them from every page.

Do not rely on default WooCommerce policy templates without reviewing them.

Remove:

• Placeholder company names.
• Brackets requiring information.
• Incorrect business addresses.
• References to another country.
• Conflicting refund periods.
• Unfinished sections.
• Lorem Ipsum.
• References to products or services you do not sell.

The return policy should explain:

• Return request period.
• Accepted product condition.
• Non-returnable products.
• Return request process.
• Return address or instructions.
• Who pays return shipping.
• Restocking fees, if applicable.
• Inspection period.
• Refund processing time.
• Refund method.
• Damaged or incorrect order procedure.
• Buyer’s remorse returns.

If your store does not accept returns or refunds, state that clearly.

Your Merchant Center return policy should match the information available on the website.

Google’s return policy requirements state that return information should be clear, accessible and consistent.

Compare the information under:

WooCommerce → Settings → Shipping

with the shipping settings inside Merchant Center.

Review:

• Target countries.
• Shipping zones.
• Shipping methods.
• Shipping costs.
• Free shipping conditions.
• Order processing time.
• Estimated delivery time.
• Remote area charges.
• Oversized product charges.
• International duties.
• Local pickup options.

If Merchant Center advertises free shipping while WooCommerce adds a shipping fee during checkout, the product information is inconsistent.

The shipping estimate should also be realistic. Do not advertise a delivery period that your store cannot meet.

Google evaluates the complete purchase journey.

Test:

Product page → Cart → Address → Shipping → Payment → Order confirmation

Look for:

• Checkout errors.
• No functioning payment method.
• Mandatory WhatsApp contact.
• Unexpected shipping fees.
• Unexpected taxes.
• The target country being unavailable.
• Mandatory account registration.
• Insecure payment pages.
• Payment gateway errors.
• A disabled Place Order button.
• Different prices during checkout.
• Products becoming unavailable after entering an address.

Test the website on desktop and mobile and, where possible, from the target country.

Security or performance settings may prevent Google from reviewing the store.

Check:

• Robots.txt.
• Accidental noindex tags.
• WordPress search engine visibility settings.
• Cloudflare firewall rules.
• WordPress security plugins.
• Country blocking.
• IP blocking.
• Password protection.
• Maintenance mode.
• CDN configuration.
• JavaScript challenges.
• HTTP 403 errors.
• HTTP 404 errors.
• HTTP 500 errors.
• Redirect loops.

Product pages, policy pages and business information should be accessible without requiring a login.

Prices and availability should not depend entirely on JavaScript that Google may fail to process consistently.

Remove all unfinished theme and demo content, including:

• Lorem Ipsum text.
• Demo products.
• Default theme contact information.
• Empty category pages.
• Broken social media links.
• Missing images.
• Fake customer reviews.
• Coming Soon sections.
• Incomplete translations.
• Broken policy pages.
• Test payment methods.
• Placeholder email addresses.
• Non-functional menu links.

A visually attractive website can still fail Merchant Center review if important pages are incomplete or non-functional.

Some products may be legal to sell but restricted or unsupported in Google Shopping.

Before requesting a review:

• Check the policy for each product category.
• Remove prohibited products from the submitted source.
• Separate restricted items from eligible products.
• Review medical, healthcare, adult, weapons, tobacco and financial product policies carefully.
• Do not disguise a restricted product using a different title or category.
• Do not submit services as physical products.
• Clearly disclose subscription offers.

The ability to sell an item through WooCommerce does not automatically mean it is eligible for Google Shopping.

The official Google for WooCommerce extension can connect a WooCommerce store to Merchant Center and synchronize eligible products.

The general process is:

1. Create or select the correct Google account.
2. Install Google for WooCommerce.
3. Connect the intended Google account.
4. Select or create the correct Merchant Center account.
5. Verify and claim the website domain.
6. Select the store’s primary language.
7. Choose target countries.
8. Configure shipping and tax information.
9. Review eligible products.
10. Start product synchronization.
11. Review all issues under Needs attention.

The extension uses an API connection instead of requiring a traditional standalone feed file.

However, connecting the extension does not guarantee approval. The website, products, policies and checkout must still comply with Google requirements.

• WordPress is updated.
• WooCommerce is updated.
• The theme is updated.
• Required plugins are updated.
• WP-Cron works.
• Scheduled Actions have been reviewed.
• REST API works.
• Product synchronization works.
• Duplicate sources are removed.
• Cache is cleared.
• Product Schema is valid.
• Broken links are repaired.
• SSL works.
• Maintenance mode is disabled.
• Googlebot is not blocked.
• The mobile store works correctly.

• Prices match.
• Currencies match.
• Availability matches.
• Sale prices are active and genuine.
• Product images work.
• Product URLs work.
• Product descriptions are accurate.
• Brand information is correct.
• GTIN values are valid.
• MPN values are accurate.
• Variations are submitted correctly.
• Restricted products are removed.
• Products can be purchased in the targeted country.

• The business name is consistent.
• The address is accurate.
• The telephone number works.
• The email uses the store’s domain.
• The Contact Us page is complete.
• The About Us page is complete.
• Contact details are visible before checkout.
• Business information matches Merchant Center.

• Shipping policy is complete.
• Return policy is complete.
• Refund policy is clear.
• Cancellation policy is available.
• Privacy policy is available.
• Terms and conditions are available.
• Subscription terms are clear.
• All policy links appear in the footer.
• No policy contains unfinished template text.

• The domain is verified and claimed.
• Business information is complete.
• The target country is correct.
• Currency is correct.
• Shipping settings match WooCommerce.
• Return settings match the website.
• The product source is working.
• Duplicate products are removed.
• Old products are removed.
• All Needs attention issues have been reviewed.
• Corrected product data has reached Merchant Center.

Submitting a review request after one small or random change is not recommended.

Before requesting a review:

1. Audit the complete store.
2. Fix all policy and transparency issues.
3. Correct product data and Product Schema.
4. Remove prohibited or non-compliant products.
5. Fix prices and availability.
6. Update the product source.
7. Confirm that Merchant Center received the new data.
8. Test a complete order.
9. Verify shipping and returns.
10. Submit the review only after completing the corrections.

Google explains the official process in its guide to requesting a review of Merchant Center issues.

Creating another account does not solve the original problem.

If the website still contains the same product data, policies, business details or technical problems, the new account may also be suspended.

Attempting to create accounts to bypass an enforcement decision may make the problem more complex and can affect other connected accounts.

The correct approach is to fix the website and product data and then use the official review process.

IT LISTA provides Google Merchant Center auditing and suspension recovery services for WordPress and WooCommerce stores.

Our service may include:

• Merchant Center suspension analysis.
• Misrepresentation policy review.
• WordPress and WooCommerce audit.
• Google for WooCommerce inspection.
• Duplicate product source detection.
• Product and variation review.
• Price and inventory comparison.
• Product Schema audit.
• GTIN and MPN review.
• Currency and tax analysis.
• Shipping and return policy review.
• Checkout testing.
• Googlebot accessibility review.
• Restricted product assessment.
• Preparation for another Merchant Center review.
• Review result analysis and next-step recommendations.

Google for WooCommerce provides direct product synchronization. A reliable product feed plugin may also be used when more advanced feed controls are required.

The most important point is to use a correctly configured primary product source and avoid unnecessary duplication.

Each product variation can be submitted as a separate item. Duplicate product sources, target countries and old products may also increase the number of items.

Common causes include:

• Cached pages.
• Taxes.
• Multiple currencies.
• Variable products.
• Outdated Product Schema.
• Expired sale prices.
• Synchronization delays.
• Location-based pricing.
• Checkout fees.

Compare the visible price, structured data, product source and final checkout total.

An SEO plugin does not automatically cause suspension.

However, it may contribute to price or availability problems if it creates Product Schema that conflicts with WooCommerce, the theme or another Schema plugin.

Test the actual structured data instead of disabling plugins randomly.

Yes. Google may crawl an outdated cached version of a product page while the product source contains the new price.

Clear page, object, server and CDN cache after major product updates.

Not necessarily.

Changing the theme may solve a technical or layout problem, but it will not fix missing business information, incomplete policies, restricted products or incorrect Merchant Center settings.

No company outside Google can guarantee reinstatement because Google makes the final decision.

A professional audit can identify technical, product data and policy issues and prepare the store correctly before another review request.

Fixing Google Merchant Center suspension in WordPress and WooCommerce requires more than installing a new plugin or reconnecting the account.

A complete audit should review:

• Business information.
• Website policies.
• Product data sources.
• Product prices.
• Product inventory.
• Product Schema.
• Product variations.
• Currencies and taxes.
• Shipping settings.
• Cart and checkout.
• Googlebot access.
• Conflicting WordPress plugins.
• Restricted products.

The more accurate, transparent and consistent your store is, the stronger your chances of passing Google’s review and restoring your products to Shopping ads and free listings.

For a broader explanation covering Shopify, WooCommerce, Salla, Tager and custom-developed stores, read our:

[Complete Guide to Fixing Google Merchant Center Misrepresentation and Account Suspension]

If your WooCommerce store has been suspended or its products have been disapproved, contact IT LISTA for a complete WordPress and Merchant Center audit before submitting another review request.