Magento Google Merchant Center suspended? The 7 most common causes (and the actual fix)

If you run a Magento or Adobe Commerce store and your Merchant Center got suspended, the cause is usually different from what hits Shopify or WooCommerce merchants. After auditing dozens of Magento stores after suspension, the same seven configuration mistakes show up again and again.

1. Tax display set inconsistently across catalog and feed

Magento has more tax-display flexibility than any other platform. Stores -> Configuration -> Sales -> Tax -> Price Display Settings controls whether catalog prices show with or without tax. If the feed exports prices excluding tax but the storefront displays them including tax, Google sees a price mismatch on every product. This single setting causes roughly 40% of Magento misrepresentation suspensions.

2. Catalog rules applied after feed generation

A catalog rule that gives 10% off after 8 PM, or a flash sale scheduled in advance, applies at checkout but is not in the feed at the moment of generation. The feed exports the regular price, Googlebot crawls during the discount window, and the mismatch triggers a disapproval. Either include rule-discounted prices in the feed via a sale_price attribute, or schedule feed regeneration to match rule activation times.

3. Customer-group pricing leaking into the public view

Tier prices and group prices for B2B customers sometimes get exposed in the public product page when a developer flips the "show tier prices to all customers" flag. Restrict tier price visibility to the relevant customer group in System -> Permissions -> Customer Groups.

4. Magento 1 stores still in production

Magento 1 reached EOL in June 2020. Stores still on M1 fail modern HTTPS handshakes, TLS 1.2+ requirements and Mixed Content checks. There is no patch for an end-of-life codebase that satisfies 2026 Merchant Center expectations. Migrate to 2.4 or Adobe Commerce.

5. Empty CMS policy pages

Magento ships with placeholder CMS pages for privacy-policy, returns and shipping. Many merchants launch with the default lorem-ipsum text still in place. Google's policy checker reads these pages and treats default text as missing content.

6. Robots.txt accidentally blocking products

Default Magento robots.txt correctly blocks /catalogsearch, /customer, /checkout and /sales. But some merchants add Disallow: /catalog/product to keep "duplicate" URLs out of the index, which blocks every product page. Googlebot cannot read the page, sees a 403, and the account gets suspended.

7. Configurable products without parent-child GTIN mapping

For configurable products, the GTIN must be set per child SKU, not on the parent. Many feed extensions export only the parent GTIN, which Google sees as a duplicate across every variant.

The April 2026 AI verification layer adds three checks on top

Since April 2026, every Merchant Center account also goes through automated identity verification before an appeal is approved. For Magento stores: the business name in your footer must match the WHOIS registrant, the registered address must match a public business registry, and the phone number must be answered when called.

The full guide

I wrote the full step-by-step fix process here, including the 7-step recovery and platform-specific configuration: https://www.gmcsuspension.com/google-merchant-center-magento-suspended.html

If you want to skip ahead and find which of these seven your store trips on, the free audit at https://www.gmcsuspension.com runs all 43 GMC policy checks against your live storefront in about 60 seconds.

Which of these have you seen most often in production?