When Merchant Center suspends an account, Shopping stops, Performance Max stops, and the revenue tied to them goes dark the same hour. Google Ads disapprovals and account suspensions are the most common emergency we get pulled into, and the suspension email is vague by design. This is the diagnosis and repair sequence that comes from remediation work on real accounts, not from Google's policy page.
Google Ads disapprovals vs account-level suspensions
First, establish which problem you have, because the resolution paths are different.
Product disapprovals are item-level. Individual products in Merchant Center get flagged, they stop serving in Shopping and PMax, and the rest of the account keeps running. Annoying, revenue-relevant if your hero products are hit, but fixable through normal feed work. The Diagnostics tab tells you which attribute or policy each item failed.
Account-level suspension is the serious one. Every product stops serving at once, and the cause is rarely a single product attribute. It is Google's systems concluding something about your business as a whole, which is why fixing one product at a time gets you nowhere.
The diagnosis starts in Merchant Center under account issues: a named policy with a preliminary warning period means you have days to fix the cause before enforcement. A suspension already in effect means you are in appeal territory, and everything below applies.
The four suspension types and how to tell which one you have
Nearly every suspension lands in one of four buckets, and the bucket determines your fix.
- Misrepresentation is the most common and the vaguest. Google's systems decided your store might mislead buyers: missing business information, thin contact details, prices that do not match the site, or a brand-new domain with no trust history.
- Policy violation means specific products or claims are restricted: prohibited categories, regulated goods, or banned claim language in titles and descriptions.
- Website issue covers a broken or inaccessible destination: checkout errors, pages Google cannot crawl, malware flags, or a site under construction.
- Circumvention is the gravest: Google believes you opened a new account to dodge a previous suspension. These rarely come back, which is why you never spin up a fresh Merchant Center to bypass a ban.
The suspension email names the policy. Match it to the bucket before touching anything.
The disapproval and suspension causes we see most in e-commerce
Across remediation work, the same causes repeat. Price and availability mismatches between feed and site lead the list: the feed says 49 euros, the page says 54 after a theme update, and the feed crawler notices even when no human does. Feed hygiene is its own discipline, covered in our product feed optimization guide.
After parity, the pattern is trust gaps. Missing or hard-to-find return policy, no visible contact information beyond a form, checkout without clear shipping costs before payment. None of these feel like policy violations to a store owner. To Google's misrepresentation systems they are exactly that.
Then come restricted product surprises, where a supplement ingredient or a product description claim trips a policy the merchant never read, and finally the promotional overreach cases: countdown timers that reset, fake original prices, or claims a regulator would flag.
Note the overlap: most of these hurt conversion rates too. The feed is the foundation, and the trust signals Google checks are the ones buyers check.
The pre-appeal checklist: fix everything before you submit anything
The most expensive mistake in this process is appealing before the problems are fixed. Appeal attempts are limited in practice, each rejection makes the next review colder, and Google's reviewers check the whole account, not just the issue named in the email.
Before submitting, work through the store as a skeptical reviewer would. Return policy and shipping policy: present, findable, and matching what checkout charges. Contact details: a real address and reachable contact, not just a form. Prices, currency, and availability: identical between feed and live site, variant by variant. Checkout: complete a test purchase yourself, including payment page load. Business identity: matching across Merchant Center settings, the website footer, and any linked profiles.
Then go wider than the named policy. If the suspension says misrepresentation but three products also carry borderline claims, fix those now. A reviewer who finds a second issue does not approve the appeal with a note. They reject it.
How to write an appeal that gets reviewed
The appeal is not a defense. It is evidence of remediation. Appeals that argue the suspension was unfair fail even when the merchant is right, because the reviewer's job is to confirm the problem no longer exists, not to relitigate the decision.
The structure that works: state plainly what you understood the issue to be, list the specific changes made with where to verify each, and confirm the account now complies with the named policy. Concrete beats eloquent. "Added full return policy at /returns, corrected price mismatches on 14 products, added registered business address to footer and contact page" is a strong appeal. "We are a legitimate business and believe this is an error" is a rejection template.
Keep it short, factual, and free of frustration. The person or system reading it processes volumes of these, and the easiest appeals to approve are the ones where verification takes minutes.
Timeline expectations and what to do while you wait
Product-level disapprovals usually clear within a few days of a fixed feed re-crawl, and you can request re-review per item from Diagnostics. Account suspensions are slower: an appeal review takes roughly one to four weeks depending on the policy and whether a human gets involved, and chasing support daily does not move the queue.
Use the gap deliberately. Search campaigns on standard text ads are unaffected by Merchant Center, so demand capture does not have to go to zero while Shopping is dark. It is also the window for the deeper feed, policy, and site work you never prioritize while everything runs.
What you must not do is create a second Merchant Center for the same store, swap domains to dodge the flag, or push the same feed through a relative's account. All of it converts a recoverable suspension into a circumvention case, the one bucket with no realistic way back.
Prevention: the health checks that catch issues early
Reinstatement is the wrong goal. Never being suspended is the goal, and the checks are not demanding once they are routine.
Weekly: open Merchant Center Diagnostics and read it, even when campaigns look fine. Disapproval counts trend upward before they become account problems. Monthly: verify price parity on your top sellers after any theme, app, or currency change, confirm policy pages survived redesigns, and re-check checkout end to end. After any site migration or replatform: treat the feed as broken until proven otherwise.
Merchant Center health is not bureaucratic overhead. It is load-bearing for the whole paid program: the glamping brand that grew revenue 283% did it on Shopping and PMax campaigns that never had to stop, because the foundation stayed clean.
If you want your account checked before Google checks it, our free 48-hour audit includes a Merchant Center health review, and if you are currently suspended, it tells you which bucket you are in and what the appeal needs to contain.