Merchant Center suspended for misrepresentation: the checklist, in the order we find them

A Merchant Center misrepresentation suspension almost never means Google thinks you are a fraud; it means something in your product record contradicts something else Google can see: price mismatches between feed and landing page, missing or contradictory policy pages, brand or GTIN conflicts, or claims in titles the page does not support. Google will not itemize the cause. Work the checklist in the order these causes most often turn up, fix everything found rather than the single most likely item, and appeal once with the full remediation described.

If you are reading this with Shopping at zero, go to step 3. Everything below is ungated.

What does a misrepresentation flag actually mean?

Misrepresentation is Google's label for a gap between what your product record claims and what a shopper would find. It is a policy category applied to a data condition, not a judgement about your intent.

Google builds its picture of an item from the feed, the landing page it crawls, its structured data, and the prices read through automatic item updates. When those disagree in a way that would change a shopper's decision, that is the violation under Google's Shopping ads policies. Item-level disapprovals name a reason and a SKU; account-level actions do not, because one label is covering many different conditions.

Why won't Google tell you which product or which field?

Google does not itemize misrepresentation causes, and support will typically restate the policy rather than name a SKU or a field. Plan an audit that does not need a diagnosis, because you are not getting one.

So audit every mismatch class rather than the one you suspect. An account can be failing two at once, and a partial fix that leaves the second standing reads as a remediation that did not work.

What triggers a Merchant Center suspension for misrepresentation?

Four conditions account for nearly every case we audit, and this is the order we most often find them: price and availability disagreement between feed and landing page, thin or unreachable business and policy information, identity conflicts, and unsupported title claims. The notice reads identically in every case, so your signal is what changed just before it.

One sentence covers six problems. Find the row matching when yours landed, and check that column first.

The checklist, in the order to work it

Work these nine steps in sequence. Steps 3 to 5 cover the classes we most often find at fault; with one day, spend it there.

1. 1.Freeze and export the feed first. Snapshot the exact file that was live when the suspension landed; you cannot rebuild it after a re-push.
2. 2.Read the notice for scope and date. Confirm whether the action is account-level or item-level, then export every item-level issue from Products → Needs attention (Diagnostics in the older interface). Those are itemized, and they often point at the same condition.
3. 3.Reconcile price and availability, feed against live page. For top sellers by clicks plus everything edited in the last 30 days, compare price, sale_price and availability to what the page renders now. Log every disagreement; fix nothing yet.
4. 4.Check the structured data, not just the visible price. Google reads the Offer markup on the page, as set out in Google's product structured data documentation, so a correct on-screen price above a stale price, priceCurrency or availability is still a contradiction.
5. 5.Walk the path to checkout and watch every number that moves. Mandatory fees, handling charges, currency switching, a tax treatment that differs from the feed.
6. 6.Make the policy surface real. Shipping, returns, contact and business identity: findable from the homepage, crawlable, specific, consistent with your account settings. A returns page saying 30 days while the settings say 14 is a detectable contradiction.
7. 7.Resolve identity conflicts. Check brand, gtin, mpn, identifier_exists and condition against the product actually on the page, and confirm link lands on that variant. Borrowed supplier GTINs turn up repeatedly in our audits; the product attributes working spec has the field detail.
8. 8.Read your titles and descriptions as claims. "Free shipping," "authentic," "lowest price," condition words, warranty language. Either the page states it plainly or it comes out of the copy.
9. 9.Fix everything, verify, then appeal once. Push the corrected feed, confirm a successful fetch, re-check a fresh sample against live pages, then appeal.

The same discipline underpins product feed optimization.

What if you sell luxury, designer or resale inventory?

Luxury, designer and resale catalogs draw misrepresentation flags for a reason unrelated to price: the record implies a brand relationship the site cannot evidence. Make the relationship provable on the page rather than stripping the brand name and hoping.

If you are an authorised retailer, say so and name the categories it covers. If you are a reseller or marketplace, describe the authentication process in detail and set conditions honestly instead of defaulting everything to new. Grey-market and parallel-import stock is hardest: the claim being read is not about quality but about your right to represent the item. Nobody writes this section because it is uncomfortable, and it resolves what everything else missed.

How do you write the Merchant Center suspension appeal?

Write one appeal, after remediation is complete and verified, structured as a record: what you found, what you changed, how you verified it, what prevents recurrence. Spend your effort on making the remediation complete rather than on polishing the wording; a reviewer is checking whether the account now complies, not how the sentences read.

What we found. Every mismatched class is audited, including the clean ones: price parity, availability parity, Offer markup, checkout integrity, policy surfacing, identity fields, title claims.

What we changed. Field level, with counts and dates. "Updated price and sale_price on \[n\] SKUs, corrected availability on \[n\], republished the returns page."

How we verified. The sample re-checked, the method, the date of the last successful fetch, and confirmation that markup was checked too.

What prevents recurrence. The monitor you put in place and who owns it. This is the block we most often find missing; it is what separates a real fix from a rushed one.

Do not argue, do not ask which product was at fault, and do not submit mid re-crawl.

How long does reinstatement take?

Reinstatement runs through a review queue rather than an instant check, so it takes as long as the queue takes, and resubmitting does not shorten it. Repeat appeals buy nothing and cost you a clean record.

While you wait, keep pushing the corrected feed so the fixed data is what gets re-crawled, move spend to surfaces still live, and hand finance the reconciliation report.

How do you stop it happening again as the catalog churns?

Suspensions recur because the conditions that caused them regenerate every time the catalog changes, and catalogs change daily. Treat agreement between record and page as a monitored invariant, not a project you closed in September.

Watch four things continuously: price and availability parity, policy-page reachability, identity-field conflicts on new SKUs, and claim linting when titles are generated. A quarterly audit will not catch a promotion that expired on Tuesday.

Shopping, paid social, onsite search and AI assistants read the same product-language record, which is why one contradiction takes down a revenue line and fixing the input once fixes it everywhere. That record has to be maintained continuously, because a catalog churning daily cannot be governed by a quarterly spreadsheet. The newer Merchant Center conversational attributes ride that same record, and the delivery layer is covered in product feed optimization.

The check worth keeping is the one that survives a finance review. Pick ten SKUs at random tomorrow and show that record and page agree on price, availability, identity, and every claim in the title. If they do, and it happens again next Tuesday without anyone remembering, you are done.

Frequently asked questions

What does "misrepresentation" mean in a Merchant Center suspension?

Misrepresentation is Google's label for a gap between what a product record claims and what a shopper would find, which in our audits is most often a feed-to-page price or availability disagreement. It describes a data condition, not a conclusion that the merchant is dishonest.

Can I get a Merchant Center suspension lifted without knowing the exact cause?

Yes, and that is the normal case, because account-level notices name neither the SKU nor the field. Audit every mismatch class in the order we most often find them, fix everything found rather than the likeliest item, then describe the remediation in one appeal.

How many times can I appeal a misrepresentation suspension?

Treat the first appeal as the one that counts and submit it only after remediation is complete and verified. Repeat appeals for partial fixes read as failed remediations, and resubmitting does not move you through the queue faster.

Does a price mismatch between my feed and my website really cause suspension?

Yes, and it is the trigger we find most often, including when the on-screen price is right but the Offer markup is stale. Google compares feed, rendered page and markup, so all three must agree through checkout.

Do my shipping and returns policies need to be on the site itself?

In practice yes: findable from the homepage, crawlable rather than JavaScript-only, specific about timeframes and costs, and consistent with your account settings. A returns page contradicting the configured return window is detectable without a human.

Why was my account suspended when all my products were approved?

Item-level approval and account-level compliance are separate checks, so a catalog of approved products can sit under a suspended account. Account-level misrepresentation points at business information, policy pages or a catalog-wide pattern rather than any single item.

Product Data Enrichment: What It Means When the M…