Google Merchant Center Suspended? Find the Real Cause Before You Request a Review

Identify the exact policy cited, find the specific cause behind it, fix it properly, verify the fix is live, and then request a single well-prepared review. The step most businesses skip is the second one: requesting a review before the real cause is fixed wastes a limited attempt and lengthens the wait before the next. If a request is refused, that usually means a second cause exists rather than that the first fix was wrong.

The notice names a policy rather than a cause, which is why diagnosis matters. The most common reasons are misrepresentation, which is usually about site trust signals rather than products; policy violations on restricted items; website requirement failures around checkout, contact details or security; and price or availability mismatches between your feed and your landing pages. A pattern of unaddressed disapprovals often precedes account-level action.

Usually that Google cannot satisfy itself a real, contactable business stands behind the store, or that what a shopper sees does not match what they get. In practice it is most often thin contact information, an unclear or hard-to-find returns policy, prices that differ between feed and landing page, missing business identity, or promotions that cannot be honoured as written. It is rarely about the products, and the fix is usually adding information rather than removing claims.

Review times vary by account and by the type of issue, so we do not quote a fixed figure. What we commit to is submitting one properly prepared request rather than several hopeful ones, and tracking each product until it serves again. Where a review is refused, we investigate the second cause rather than resubmitting the same correction.

No, and anyone who does is either guessing or misleading you. Google makes the decision. What we control is the quality of the diagnosis and the review request, and whether the underlying problem is genuinely fixed. Where an account or a product category is unlikely to be reinstated, we will tell you before taking the work.

More urgent than it looks. Disapproved products are invisible in Google Ads reporting — you see what served, not what could not — so retailers routinely lose a slice of their catalogue without any alarming number appearing. A pattern of unaddressed disapprovals is also the usual prelude to an account-level suspension.

Usually yes, at least to view it. A significant share of suspensions, misrepresentation above all, are caused by the website rather than the feed — contact details, returns policy, checkout and security. We can diagnose from the public site, but access to staging or to whoever can deploy changes makes the fix considerably faster.

Most of the time, yes. Feed rules and supplemental feeds let us correct titles, add attributes and fix categorisation at the Merchant Center end, which means changes ship in days rather than waiting for a development release. Where a source change genuinely is needed, we write the specification for your developers rather than describing the problem and leaving them to interpret it.

No, not any more. Merchant Center Next was the rebuilt interface that replaced the classic platform, and in July 2026 Google dropped "Next" from the name. It is simply Google Merchant Center. The main practical issue is that older guides written for the classic interface describe menus that no longer exist, which matters when you are troubleshooting against one.

Both, and most of our work is the second. Ongoing google merchant center management means weekly disapproval checks, feed health monitoring, catalogue reviews when policies change and a check after every website release. It exists to make the rest of this page unnecessary.