What triggers a Google Merchant Center account suspension (and how to get reinstated)

One product disapproved is an item-level issue: that product stops showing and the rest of your catalog is fine. A suspension is account-level: Google stops showing all of your products, usually after a warning period, and in the worst cases closes the account to Shopping. The fixes overlap, but a suspension almost always points at something about your store or your account, not one stray attribute. Treating a suspension like a single bad product is how merchants stay suspended.

• Disapproval: one or more products hidden, catalog otherwise live.
• Suspension: the whole account stops showing, often with a warning first.
• The cause of a suspension usually lives on your website, not just in the feed.

Most suspensions come from a short list of causes, and misrepresentation is the one that catches honest stores off guard. Google is not only reading your feed; it visits your storefront and checks that you look like a real, trustworthy business. Missing contact details, an unclear return policy, prices that do not match the landing page, or claims it cannot verify all read as misrepresentation. The rest are policy violations and a pile-up of unresolved disapprovals that eventually tips the account over.

• Misrepresentation: thin contact info, missing or vague refund policy, price or availability that differs between feed and page.
• Policy violations: restricted or prohibited products, unsafe or misleading content.
• Unresolved disapprovals accumulating until the account itself is flagged.

Because misrepresentation is about trust signals on your site, the fix often lives outside the feed entirely. Before you touch a request, make your storefront look like a business Google can verify: real contact details, a clear return and refund policy, consistent pricing between the product page and the feed, and no claims you cannot back up. Only then reconcile the feed so every flagged attribute is corrected and live on the page, since Google re-crawls the page, not just the feed file.

• Add visible, complete contact information: business name, address, a working contact method.
• Publish a clear return, refund, and shipping policy the buyer can actually find.
• Make price and availability match between the live page and the feed.
• Then correct the flagged feed attributes and confirm they are live on the storefront.

You usually get one meaningful request, and repeated requests without real change can slow you down or count against you. Fix every cause first, confirm it is live on the storefront, then submit a single factual request from the account issues area. Name what was flagged, state what you changed for each, and point to where it is now correct. Do not argue policy, do not promise future behaviour, and do not pad it with reassurance. A reviewer wants to see that the specific problem is gone.

• Resolve every cause before requesting, not just the obvious one.
• Submit one clear request from the account-level issue, not several partial ones.
• Keep it factual: the issue, the change, and where it is now live. No guarantees.

Reinstatement is not the finish line, and a second suspension is harder to recover from. The account that stays healthy is the one that catches new disapprovals early, before they pile up into another account-level flag. That is the quiet value of monitoring: a record of what was wrong and what you changed, an alert the moment something new is flagged, and a draft reinstatement request ready when you need it. Fixing a suspension once is survivable. Seeing the next problem coming is what keeps the account open.