Misrepresentation and account suspension
The most serious Merchant Center disapproval class, what triggers a misrepresentation flag or account suspension, the trust signals Google checks, the reinstatement path, and how to prevent it.
Misrepresentation is the account-level disapproval that suspends everything at once; no product serves regardless of how clean the feed is. It's triggered by patterns that make Google distrust the merchant: inconsistent prices, missing business information, contact-detail gaps, or feed data that contradicts the website. Reinstatement is slow and unforgiving, so prevention is the whole game.
Why this class is different
Every other disapproval in this channel is about a product: a bad GTIN, a mismatched price, a promotional image. Misrepresentation is about the merchant. It's Google deciding it can't trust the business behind the feed, and the consequence is proportionate: the account is suspended and nothing serves, no matter how clean any individual product is. You cannot fix a suspension by fixing products. You fix it by rebuilding trust in the business.
This is also the class where working order matters most. If Diagnostics shows an account-level suspension, item-level work is wasted effort until the account clears. See the disapproval taxonomy and Diagnostics for why account issues always come first.
What triggers a misrepresentation flag
Google keeps the exact triggers vague to stop merchants gaming them, but the known pattern is consistency and transparency. Flags come from:
- Inconsistent or misleading pricing: a sustained pattern of price and availability mismatches is the most common on-ramp to misrepresentation. What starts as item disapprovals becomes an account-level trust judgement. See price and availability mismatch.
- Missing or unverifiable business information: no clear business name, no physical address, no verifiable identity behind the store.
- Contact-detail gaps: no reachable phone, email or contact form; a shopper (or Google) can't get in touch.
- Feed contradicting the website: the feed advertises products, prices or claims the site doesn't back up, or the landing pages don't match the offers.
- Missing trust pages: no returns policy, refund terms, delivery information, or terms and conditions where shoppers expect them.
- Unrealistic or unsupported claims: pricing too good to be true, health or performance claims the site can't substantiate.
None of these is a single field. Misrepresentation is the sum of trust signals falling below a threshold, which is why the fix is comprehensive, not surgical.
The trust signals Google checks
| Signal | What Google looks for |
|---|---|
| Business identity | Clear name, physical address, verifiable ownership |
| Contact | Working phone, email or form; reachable support |
| Policy pages | Returns, refunds, delivery, terms, present and findable |
| Price consistency | Feed, site and crawl all agree, sustained over time |
| Website / feed agreement | Advertised offers match what the site actually sells |
| Secure checkout | HTTPS, a real, completable purchase flow |
Deep dive The reinstatement path, and why prevention is the only sane strategy
Reinstatement is deliberately slow and unforgiving, and understanding why reshapes how you should treat this entire class.
When an account is suspended for misrepresentation, the path back is: identify every trust deficit, fix all of them, then submit a single request for review. Each review takes up to several days. Crucially, failed reviews add escalating cooldowns: request again too soon, or request with the problems only partly fixed, and the cooldown lengthens. A merchant who treats reinstatement like item disapprovals (fix one thing, resubmit, see what happens) can burn through their attempts and be locked out for weeks while trading grinds to zero.
So the review is not iterative. You get, in practice, very few real attempts, and the vague notice gives you little to aim at. The only strategy that works is to fix comprehensively before the first request: walk the entire trust-signal list, close every gap, verify the site backs every feed claim, confirm price consistency has been stable for a meaningful window, not just corrected an hour ago, and only then request review. Google is looking for evidence the business is durably trustworthy, not that a symptom was patched.
Which is why prevention is the whole game. The triggers are cumulative and slow-building: a drift of price mismatches here, a stale contact page there, so they're catchable long before they cross the suspension threshold, if something is watching. The preventive posture: keep feed and site in genuine agreement (structured data, tight refresh cadence), keep business and policy pages complete, and monitor the leading indicator (price and availability consistency) continuously, because that's the pattern most likely to escalate. /tools tracks the consistency and identifier signals that feed a misrepresentation judgement and flags products drifting toward the patterns Google penalises before they compound into an account-level problem. And because BidSmart is approval-first, nothing it does (bids, budgets, incubator moves) executes without your explicit sign-off, so automated activity never introduces a claim or change you didn't approve. Catching the drift early is vastly cheaper than the reinstatement queue.
Prevention checklist
Run this before you ever see a flag, not after:
- Keep feed and site in agreement. Price and availability consistency is the leading indicator: fix mismatches while they're item-level, before they become a trust judgement.
- Complete your business information. Name, physical address, verifiable identity in Merchant Center and on the site.
- Make yourself reachable. Working contact details a shopper can actually use.
- Publish the trust pages. Returns, refunds, delivery, terms: present and easy to find.
- Back every claim. The site must sell, at the stated price, what the feed advertises. No unsupported claims.
- Monitor continuously. The triggers build slowly; catch the drift before it crosses the threshold.
If you are already suspended, don't rush the button. Fix the whole list, verify the fixes are live and stable, then request review once, and only once you're confident. See how to fix disapproved products for the mechanics of requesting a re-review.
Frequently asked questions
My products are fine but the whole account is suspended. How?
Misrepresentation is account-level, not item-level. It's a judgement about the business's trustworthiness, so it suppresses every product at once regardless of individual feed quality. Clean products don't serve while the account is suspended, so you have to clear the account flag first.
Google gave no specific reason for the suspension. What do I do?
Misrepresentation notices are deliberately vague to prevent gaming. Work the known trigger list systematically, business info, contact details, price consistency, website/feed agreement, returns and policy pages. Fix everything, then request review. There's no single field to correct.
How long does reinstatement take and how many tries do I get?
Reviews take up to several days each, and failed reviews add escalating cooldowns, so a scattershot fix-and-resubmit approach can lock you out for weeks. Fix comprehensively before the first request; you effectively get few real attempts.