Google Merchant Center Suspended on WooCommerce: The Fix Guide

A Merchant Center suspension on WooCommerce looks the same as on any other platform: a notice, an issue name such as Misrepresentation or Website needs improvement, and products that stop showing. The fix is different. WordPress gives you more control, which also means more places for something to go wrong: themes, caching, security plugins, and the Google for WooCommerce extension itself.

This guide works in order: understand the review flow, fix store details and policies, let the data sync, rule out plugin conflicts, then request a review.

How the Google for WooCommerce review flow works

WooCommerce's documentation on Google reviews and approvals explains the flow:

• Initial review. When you upload products for the first time, Google reviews your products and website. WooCommerce says this can take 3 to 5 days, and products show as Pending in the meantime. If the review finds that the site doesn't comply with Shopping ads policies, the account can be suspended straight away.
• Warnings. A warning email gives you details of the issue and a time frame to fix it, usually seven days.
• Suspension. If issues aren't fixed, you receive emails with the details of the policy and the suspension.

Where you request a review depends on how the account was created:

• If you created your Merchant Center account during the extension's setup, you can request a review in WP Admin under Marketing → Google for WooCommerce → Product Feed.
• If you linked an existing Merchant Center account, you must request the review in Merchant Center itself.

WooCommerce also notes that you can only request a review when no other request is pending, that one review covers all issues for the same country of sale, and that a suspended account has two opportunities to request a review. If a second review is disapproved, the account enters a cool-down of about seven days, and the Request review button is disabled.

Google's own pages are similar: Request a review of your issues says to allow 7 business days, and Fixing warnings and account suspensions says the cool-down can increase with each unsuccessful review. Our guide to rejected reviews and cool-downs covers the rules in detail.

The takeaway: attempts are limited, so fix everything first.

Step 1: Read the actual issue

Start in Merchant Center under Products → Needs attention, or in the extension's Product Feed section, which lists each affected product, the issue, and a suggested action. Write down the exact issue name. "Misrepresentation", "Website needs improvement", and an individual product disapproval need different fixes. If the issue is account-level, our recovery guide explains how to tell the types apart.

Also check for an identity verification request. Google's review page says identity verification must be completed before you can request a review in these cases.

Step 2: Fix the store address and business details

WooCommerce asks for the store address in two separate places, and both matter.

1. WooCommerce settings. Go to WooCommerce → Settings and complete the store address. WooCommerce's common errors page says the extension's setup can't be completed until the street address, city, postcode, and country are filled in.
2. Merchant Center contact details. WooCommerce's requirements page says you must also give Google Merchant Center your phone number and business address for verification, under Google for WooCommerce → Settings → Contact information. These aren't shown to customers.

Then make the public details match. Google's fix page for missing contact information says your business name, address, and phone number should be identical in your website footer, on your contact page, and in Merchant Center. Google's business information requirements ask for the address where your business is registered and an email address on your own domain.

On WordPress, contact details often live in a footer widget, a contact page, the theme header, and WooCommerce email settings. Check each one.

If the extension shows "Unable to update your contact information", WooCommerce's common errors page explains that this usually means your site's XML-RPC URL is blocked by your host, firewall, or a security plugin. Open yourdomain.com/xmlrpc.php in a browser. A working URL shows "XML-RPC server accepts POST requests only."

Step 3: Fix your policy pages

WooCommerce's requirements page says that if Google's review team can't find your refund and return policies, your account may be suspended. It lists what to explain:

• Policies (mandatory): how you handle returns and refunds, what the customer must do, the time frame for returns, and when the customer can expect a refund.
• Return address (mandatory): where returns should be sent.
• Rules (recommended): any additional rules.

If you don't offer returns or refunds, say so explicitly.

WooCommerce creates a draft Refund and Returns Policy page for new stores. Its compliance policy documentation describes this draft as a sample to edit, not a standard. Find it under Pages → All Pages, rewrite it for your store, and publish it. Google's return and refund fix page asks for a policy that is easy to find, for example linked in the footer of every page, and consistent wherever it appears.

Also check:

• Terms and conditions. Assign a page under WooCommerce → Settings → Advanced → Page setup, so customers accept your terms at checkout.
• Shipping information. Publish delivery times and costs that match your Merchant Center shipping settings. WooCommerce's FAQ notes that if shipping and tax charges differ significantly between Google and your store, Google may pick up on it.
• Payment methods. WooCommerce's requirements page says all accepted payment methods should be displayed on your website. The FAQ adds that Google recommends showing them in the footer or under the buy button.
• Live, working site. WooCommerce's compliance documentation says your site must be live and accessible to everyone, not in maintenance mode, with a complete checkout and a valid SSL certificate.

Google's fix page on checking that your store is fully functional adds the website-quality items reviewers look for: an About page, return policy, shipping information, and business information. It also asks you to remove placeholders such as "Lorem ipsum" and fix broken links, including social links. For more on this issue, see our page on website needs improvement, and our policy pages guide for a policy structure you can adapt to any platform.

Step 4: Give the product feed time to sync

Google for WooCommerce doesn't use a feed file. According to WooCommerce's FAQ, it syncs products through Google's Content API, and a created or updated product syncs straight away through a background job. It may take a while for the update to appear in Merchant Center, though.

Points that matter for a suspension:

• Allow time after fixes. WooCommerce's reviews page says that after you edit products, your product feed syncs automatically within 1 to 2 days. Don't request a review the moment you save.
• Check that jobs actually run. Sync relies on Action Scheduler. Background jobs are listed under WooCommerce → Status → Scheduled Actions, and errors under WooCommerce → Status → Logs.
• Force a full sync if needed. The FAQ and common errors page describe a hidden test page at wp-admin/admin.php?page=connection-test-admin-page with a Sync All Products with Google Merchant Center option.
• Keep products in place. Google's guidance for review requests says your product data source shouldn't be empty. WooCommerce's steps for a Merchant Center review also say to make sure in-stock products are uploaded.

Step 5: Rule out plugin and theme conflicts

Some problems that look like policy issues are partly technical. Common sources in WooCommerce's own documentation:

• Security plugins or hosts blocking requests. XML-RPC blocking stops contact details reaching Merchant Center. The FAQ says site verification can fail if Google can't reach your site, for example because of IP or country blocking.
• Caching. The FAQ says heavy caching can stop the site verification meta tag appearing to Google. You may need to disable caching briefly.
• Multi-currency and translation plugins. The FAQ says the extension supports WPML and WooCommerce Multilingual & Multicurrency for market-specific feeds. Other multi-currency tools aren't supported for product sync, so prices on the page may not match what Google receives.
• Non-Latin characters. The FAQ says product names or image URLs with non-ASCII characters are likely to be unsupported.

To find a conflict, WooCommerce's conflict testing guide recommends:

1. Back up the site, or use a staging copy.
2. Update all plugins and themes.
3. Switch to a default theme such as Storefront or a Twenty-series theme and test again.
4. Deactivate all plugins except WooCommerce and the extension you're testing, then reactivate them one at a time.
5. Check must-use plugins and host drop-ins, such as caching, which you can't deactivate from the plugin list.

Step 6: Request the review once

When the site, policies, and product data are fixed and synced:

1. Open your store in a private browser window and check the footer, contact page, policies, and checkout as a shopper would.
2. Request the review from the extension or Merchant Center, depending on how the account was created.
3. Choose I fixed the issue if you made changes, and read the requirements in the pop-up before confirming.
4. Wait for the result email before changing anything else.

If you need wording for the review request, our appeal templates are written to be specific and factual.

FAQ

Does Google for WooCommerce cause suspensions? The extension syncs your data. It doesn't decide policy. Suspensions come from Google's review of your site and products, but a misconfigured sync, blocked requests, or a caching conflict can create mismatches that a review then flags.

Should I disconnect and reconnect my accounts? Only for connection errors. WooCommerce documents disconnecting and reconnecting for problems such as lost website claims or setup errors. It won't remove a policy suspension, so fix the underlying issue first.

How long should I wait between fixing and requesting a review? WooCommerce says the product feed syncs within 1 to 2 days after edits. Google's contact information fix page says new crawls usually finish within 24 to 48 hours after fixes go live. Wait until your changes are visible before you request a review.

Check your WooCommerce store before you request a review

Store addresses, footer widgets, policy pages, and caching all live in different places on WordPress, so a mismatch is easy to miss. UnlockMerchantCenter scans your store's public pages for missing contact details, unclear policies, broken links, and the other signals Google's reviewers look at.

Run a free store scan → Find the problems before your next review request.

UnlockMerchantCenter is an independent tool and isn't affiliated with Google or WooCommerce. Only Google can decide whether to reinstate an account.