Merchant Center suspended: common causes and a checklist for your appeal

If your Google Merchant Center account has been suspended, the cause is usually automated data consistency checks or missing business information. This guide explains the typical causes, how Google detects them and how to use a numbered checklist to review your account, fix problems and prepare your appeal.

A suspension is rarely based on deliberate deception. Often it comes down to inconspicuous contradictions between feed and landing page, or company details that are missing or hard to find.

Why was my Merchant Center account suspended?

Account suspensions usually result from automated risk assessments that detect repeated, serious policy violations or systemic inconsistencies. A single, harmless feed error is generally not enough. Google combines signals from feed diagnostics, crawl results, account history and domain checks. In the case of “critical severity”, the account is suspended immediately until the causes have been fixed and reviewed.

Google does not assess individual product errors in isolation but aggregates violations across the account or domain. Relevant signals include repeated feed errors, contradictory information on several product pages, missing business information, faulty landing pages or a negative compliance history. Technically, automated crawls, Merchant API responses and internal heuristics feed into a risk model. If the account exceeds an internal threshold, it is deactivated.

How to proceed systematically: export the diagnostics immediately (including example URLs and error messages) and group the findings into “critical” and “warning”. Check the account level, i.e. business information, linked domains, multi-client set-up or sub-accounts. Also check whether domain verification, business verification and tax or payment details are complete. This metadata influences the decision and the chances of a successful appeal.

Typical patterns are several product groups with the same feed errors, different information between landing pages and feed across different countries or subdomains, and pages that are intermittently unreachable (flapping). Decide by severity first: fix critical problems systemically and temporarily pause individual product errors until the system runs stably.

What role do price mismatches between feed and landing page play?

Price mismatches are one of the main triggers for disapprovals because they directly affect the purchase decision. Google automatically compares feed prices with the price visible on the product page.

Google reads the prices from the feed and crawls the target URLs, including structured data and rendered HTML. Problems arise when feed updates are delayed, sale logic calculates differently on the server, or prices are loaded via JavaScript. Other pitfalls are different currencies depending on location, personalised prices (for example for logged-in users), prices shown only in images, and shipping costs that only appear at checkout.

To check, call up the product URL once with a headless browser and once with a simple HTTP request (e.g. curl -I). This shows you the differences between server-side HTML and client-side rendered content. The URL inspection in Search Console or a Googlebot user agent shows what Google’s crawler actually sees. Also check the feed fields price, sale_price and, where applicable, sale_price_effective_date, as well as the timestamps of feed generation.

If prices are calculated dynamically, the feed must reflect the same logic, or you temporarily deactivate the products. If prices are only visible via JavaScript, server-side output or markup in structured data is the better choice. With variable shipping costs, document them clearly on the product page or pass the shipping details in the feed.

Which product data inconsistencies trigger suspensions?

Contradictions in core attributes such as title, availability, GTIN/MPN, variant mapping and description can lead to disapprovals or account suspensions because they undermine the reliability of the product data.

Google compares feed attributes with the visible product details and the structured data on the page. Unique identifiers (GTIN, MPN, brand) and the correct representation of variants via item_group_id are particularly sensitive. Errors in variant mapping (e.g. the same SKU for different colours) lead to contradictions in availability and price.

For error analysis, take a sample of problematic SKUs, load the corresponding pages with a renderer and extract the relevant fields (title, availability, gtin, mpn, brand, price). Compare these values automatically with the feed export. Use PIM exports for this and check whether template logic in the PIM changes titles or attributes after the fact.

Common causes and countermeasures:

• Automatically generated titles in the feed that do not appear on the landing page: correct the template logic or adjust the pages.
• Incorrect GTIN mapping: clean up the assignments in the PIM and document where the GTINs come from.
• Visibility of variants: all variants in the feed should be available on the page as selectable options. Remove unavailable variants from the feed.

How do missing or incorrect contact and business details affect a suspension?

AI-generated example image, may differ from reality.

Incomplete or contradictory contact and business details fall under the misrepresentation policy and can lead to account suspension because they undermine trust and transparency before purchase.

Google expects visible, easy-to-find information on the legal notice (Impressum), business address, telephone number and contact options, as well as matching details in the Merchant Center. Check all domain variants and subdomains, because deviating information on country-specific domains counts as inconsistent. Also pay attention to visibility in the language versions and in the mobile view.

Approach this like an anonymous visitor: open the contact page, check the footer and legal notice, test contact forms (is there a reply address?) and compare the details with the data in the Merchant Center. Also check whether redirects or ad landing pages show different contact details.

• Master data is only maintained in the Merchant Center, but microsites or international shop versions are forgotten: align all locations.
• Telephone numbers lead to redirects or call centre announcements and there is no clear business address: add the address visibly.
• Outdated data: set up a process for maintaining master data and document changes before an appeal.

Which other causes are common (returns, shipping, reachability, SSL)?

Unclear return or shipping conditions, unreachable URLs, missing or faulty HTTPS and problems in the checkout are common reasons for product and account suspensions.

Google requires easy-to-find return and shipping information, ideally also in structured form (e.g. via hasMerchantReturnPolicy and shippingDetails). Missing or contradictory information on shipping costs and delivery times can be considered misleading. On the technical side, recurring timeouts, redirect chains, robots.txt entries that prevent Google from crawling, and TLS errors are problematic.

How to check:

• Server logs: filter for Googlebot requests and check HTTP status codes and redirects.
• Synthetic checks: monitor the response of the URLs with monitoring tools, check the content with headless browsers and compare Google’s view with the user’s view.
• Security: all product pages should be delivered via HTTPS, without mixed content warnings.

Google detects cloaking (different content for Googlebot and users) automatically. Remove any conditional delivery of content. Staging or password-protected areas that are accidentally indexable must be protected or clearly marked. If there are checkout problems, test complete order processes and the accepted payment methods. Watch out for leftover test data and for A/B tests that serve Googlebot different content.

How do I get a Merchant Center suspension lifted and how does the appeal work?

A suspension is lifted once you have fixed the problems systemically and documented this clearly in your appeal. Google then reviews the account again and decides whether to reinstate it.

Here is how to proceed step by step:

1. Collect all diagnostics exports and group the errors by relevance.
2. Fix the causes permanently, not just in individual cases.
3. Document every change with evidence: updated feed files, screenshots of the product pages, extracts from server logs or deployment timestamps.
4. Submit the appeal in the Merchant Center and attach the documentation.

The reviewer wants to see that you have eliminated the causes and not just the symptoms. Repeated rejections often have the same reasons: incomplete evidence, changes that do not cover all affected URLs, or temporary fixes that cannot be traced. If you have fixed systemic errors (e.g. faulty PIM templates or automatic price updates), also describe the deployment and monitoring measures in the appeal.

After the appeal, Google reviews the account again, which can take a few days. Tolerance is lower for repeated violations. A short internal review before the appeal helps close gaps in the documentation.

What does the practical checklist contain?

Work through the checklist in order and document every change with a timestamp and evidence before submitting an appeal.

1. Feed and landing page: compare price, availability and currency automatically with scripts or tools that read rendered HTML. Note the feed timestamps and the time of delivery.
2. Strike-through prices and sale logic: submit sale prices in the feed via sale_price (with sale_price_effective_date if needed) and make sure the page shows the same price without login or geo-filters.
3. Product attributes: in a sample, compare title, description, gtin, mpn, brand and item_group_id between feed and page. Check PIM templates for unintended changes.
4. Contact information: align the details in the Merchant Center with the legal notice, footer and contact pages on all domains and subdomains. Document discrepancies and corrections.
5. Returns and shipping: cancellation information, shipping costs and delivery times should be clearly visible and present in structured data (e.g. hasMerchantReturnPolicy, shippingDetails).
6. Reachability: check HTTP status codes (200), HTTPS configuration, redirect chains and server-side timeouts. Export the relevant server logs for the issues raised.
7. Cloaking and redirects: call up the pages with different user agents and from different locations to find conditional content or geo-based redirects.
8. Checkout and payment methods: test complete order processes, check that the accepted payment methods are visible and that the checkout is reachable for external users.
9. Business information: business address and telephone number must match on the website, in the Merchant Center and in the billing details. Document the sources.
10. Diagnostics and logs: export Merchant Center diagnostics, API errors and server logs. Archive feed versions and deployment timestamps for the appeal.

To stop the error coming back, update feeds at the same time as changes in the shop and set up automated monitoring for prices and reachability (guideline: at least hourly for price data during ongoing sales).

Frequently asked questions

How long does the review take after submitting an appeal?

Google does not give a fixed deadline; the re-review usually takes several days. In critical cases or with repeated violations it can take longer. Only submit the appeal once all issues have been fully fixed and documented.

Can I keep advertising products if only parts of the account are suspended?

Google can deactivate individual products and partially restrict the account. With critical errors, however, the entire integration can be suspended. You can see which level is affected in the diagnostics in the Merchant Center.

Which logs and evidence should I send with the appeal?

Send concrete evidence: screenshots of the live product pages with price and timestamp, a feed export with timestamp, server logs on reachability and a clear description of the corrections.

Does a one-off violation always lead to a permanent suspension?

Not necessarily. Google assesses severity and frequency. Critical violations often lead to immediate suspension, but after the issues are fixed and the appeal is successful, the account can be reinstated. Repeated violations weaken your position.

Conclusion

First check that feed and landing page match (prices, availability, variants), then the business information and technical reachability. The diagnostics in the Merchant Center are the starting point; exports and screenshots prove your corrections.

Get in touch if you need support with the root cause analysis or the appeal. We check your feed and structured data and prepare the appeal with you. You can find more on feed management under Google Shopping feed, and articles on Shopware shops in our knowledge section.