Google Merchant Center account suspended? How to fix it
First, a distinction that decides everything that follows. An account suspension is not the same as a product disapproval. A product disapproval stops one or a handful of individual SKUs from serving ("Image too small", "Mismatched price") while the rest of your catalog keeps running. An account suspension stops the entire account: nothing shows in Shopping ads or free listings, regardless of how clean any single product is.
If only some products are rejected and most of your catalog still serves, your account is not suspended, you have item-level disapprovals, and you are in the wrong place. Go to common Merchant Center disapprovals instead. This article is about the harder case: the whole account has stopped serving. Account suspensions are almost always triggered by account-level or site-level policy, not by a single malformed feed row, and that changes what actually fixes them.
Is your suspension cause feed-fixable?
Start here. Find the cause that matches your warning or suspension email, then read the column that tells you whether a feed change can touch it at all. "No (site-level)" means the fix is on your website or your business, full stop.
| Suspension cause | Where it lives | Feed-fixable? |
|---|---|---|
| Misrepresentation: false identity / impersonation | Business | No (site-level) |
| Insufficient contact information | Website | No (site-level) |
| Missing return / refund policy | Website | No (site-level) |
| Missing terms / shipping disclosure | Website | No (site-level) |
| Untrustworthy promotions: deal not actually live | Site + feed | Partly |
| Price mismatch (feed vs. page) | Feed | Yes |
| Availability mismatch (feed vs. page) | Feed | Yes |
| Circumventing systems / cloaking | Site / business | No (site-level) |
| Promotional overlay / generic image, if systematic | Feed / image | Yes |
| Restricted / prohibited products | Business | No (can filter out) |
The pattern is worth naming out loud: the dominant account-suspension causes are about who you are (a verifiable business with real contact details and clear policies) and whether your offers are true (price, availability, and promotions that match between your feed and your live storefront). Only that second half is something a feed touches.
The causes, in plain English
Google groups most account suspensions under Misrepresentation, but the Merchant Center interface often shows a more specific sub-label such as "Untrustworthy promotions". Do not let the wording throw you: it is the same Misrepresentation policy underneath. Here are the named causes that send most people searching for this article.
Misrepresentation
The big one. Google's framing is that customers should not feel misled by your offers, which means being upfront, honest, and giving people the information they need to decide. In practice it covers a few distinct patterns:
- Unacceptable business practices , hiding or misrepresenting information about your business or product, impersonating other brands, presenting a false business identity or contact details, or enticing customers to part with money or information under unclear pretenses.
- Misleading or unrealistic offers , false claims implying improbable results ("miracle cures"), or falsely implying affiliation with or endorsement by another person, organization, product, or service.
- Omission of relevant information , failure to clearly disclose the payment model and full cost, or missing merchant terms, shipping information, or a return / refund policy.
- Unavailable offers , promoting products that are not stocked, or a deal that is no longer active.
Insufficient contact information
A site-level cause. Customers need to be able to find out how to contact you on your website in at least one way. A storefront with no phone, email, address, or contact page can trip this. There is nothing in a product feed that satisfies it: the fix is on the website.
Missing return and refund policy
Also site-level. Google wants a clear, discoverable return and refund policy published on your store. The feed has no field that stands in for a real policy page, so this is a storefront task.
Circumventing systems and abuse of the network
This is the policy that catches "show Google a clean page, show shoppers a different one". Named examples include cloaking, using dynamic DNS to switch the page or product, manipulating product data or site content to bypass automated checks, and restricting crawler access to landing pages. It is treated as egregious, which, as the next section explains, means it can suspend you with no warning at all. A tool that did this for you would not be solving your problem, it would be the violation. Emberfeed does not cloak, and you should not want it to.
Restricted, prohibited, counterfeit, and dangerous products are separate policy areas that can escalate to an account suspension when the problem is systematic. They overlap the item-level policy disapproval page. For an account-level suspension, though, Misrepresentation and its site-information cousins are what most readers are actually facing.
Warning first, or suspended outright
There are two enforcement modes, and knowing which one you are in tells you how much runway you have.
Warning first (most violations)
For most policy issues, Google emails a warning before suspending. The email describes the problem, how to fix it, and a timeframe to do so. During this warning period your products may keep appearing, sometimes in a limited-visibility state, until the period ends. Critically, the grace period is 7 or 28 calendar daysdepending on the issue, not a flat 7 days. A lot of third-party guides flatten this to "you get 7 days", which is wrong and can cost you weeks of planning. Read your own warning email for the exact window that applies to your case.
If you fix the issue and the violating products are removed during the warning period, you do not need to request a review or take any further action. If the warning period ends without a fix, the account may then be suspended.
Suspended without warning (egregious)
For severe violations, Google suspends immediately. In its own words, for the most serious policy breaches your Google accounts will be suspended upon detection and without prior warning, and Google may not issue a warning for egregious violations at all. Cloaking and the other circumventing-systems behaviours sit here. If you were suspended with no prior email, this is almost certainly the bucket you are in.
How to request reinstatement
Before any of these steps: fix the root cause first.A review request that finds the same unresolved problem is a failed review, and failed reviews have consequences (see the cool-down below). Treat "Request review" as the last button you press, not the first.
- In Merchant Center, open Products, then the Needs attention tab.
- Above the summary cards, click View setup and policy issues.
- On the account issues area, use the Request review button. (For a single disapproved product instead, you would select the product and click Fix in its status column, but that is the item-level path, not an account reinstatement.)
- Wait. A review takes up to 7 business days (one Google page phrases the same window as 3 to 7 business days). You get an email when the request is submitted and again when the review is done.
A few realities to set expectations honestly. During a warning period you can request one courtesy review at any time. If you want to disagree with the decision and claim it was an error, you may only have one chance to do so. Once you have exhausted the option to disagree and attempted to fix the issue, a cool-down period begins: the review button is disabled, your account stays suspended, and with each unsuccessful re-review afterwards the cool-down may get longer.
What a feed can and cannot do here
Now the honest close. Look back at the boundary table. The causes marked "Yes" are the consistency class: when your feed price or availability drifts away from what your storefront actually shows, Google reads that as misrepresentation. A feed kept honest closes that gap: the same price, the same stock state, and compliant images as your live store, refreshed hourly so nothing goes stale. That is the slice Emberfeed genuinely helps with, and it removes a real and common suspension trigger.
Everything marked "No (site-level)" is not a feed problem. A feed tool cannot make you a verifiable business, cannot write your returns policy, cannot add a contact page to your storefront, and must never cloak on your behalf. For prohibited products it can only exclude them from the served feed so they stop dragging the rest of the account down, it cannot make a prohibited product compliant. And no tool can argue your appeal for you: reinstatement is a discretionary human review that Google reserves to itself.
Related
- How to fix the 20 most common Google Merchant Center disapprovalsA field guide to the rejections that account for the bulk of suspended Google Shopping listings. The cause, the manual fix, the bulk shortcut, and the canonical Emberfeed error page for each one.
- How to create a Google Shopping feed XML manually (2026)You can write a Google Shopping feed by hand, it is just RSS 2.0 with a g: namespace. Here is the minimal working skeleton, the 7 required attributes (and which extras you actually need), and how to validate it before Google rejects it.
Ship better catalog ads this afternoon.
Free for 3 months on one feed up to 1,000 products. Connect your XML feed, design a template, paste the new URL into Meta / Google / TikTok.