How to Recover a Google Merchant Center Account Suspended for Misrepresentation

Google suspends Merchant Center accounts for misrepresentation without warning, and the notice rarely says which specific claim on your site triggered it. In Google's own words, accounts flagged under this policy are "reinstated only in compelling circumstances" (Google Merchant Center Help, Misrepresentation policy), and a rushed appeal that doesn't fix the underlying issue burns one of the two or three review attempts you typically get before the account becomes permanently ineligible. This is a step-by-step sequence for diagnosing what actually triggered the suspension, fixing it on your storefront and in your feed, and submitting a review request that has a real chance of passing. It is written for the person who owns Merchant Center day to day, an e-commerce manager or agency account lead, not for someone deciding whether to try Google Shopping at all.

What "Misrepresentation" Actually Covers

Misrepresentation is an account-level policy, not a per-product disapproval. Google's policy page groups violations into four buckets: unacceptable business practices (false business identity, impersonating another brand, phishing for customer data), misleading or unrealistic offers (fake urgency, false endorsements, promising results you can't back up), omission of relevant information (hidden fees, missing shipping or return terms), and unavailable offers (advertising stock or deals that don't exist). Any one of these can suspend the entire account, not just the product rows involved.

That distinction matters because most public troubleshooting content, including item-level guides on general Merchant Center errors or GTIN and identifier rejections, doesn't apply here. You can have a perfectly formatted feed and still be suspended for misrepresentation, because the policy is about whether your storefront and business identity match reality, not whether your feed attributes are well-formed.

Step 1: Read the Suspension Notice for What Policy It Actually Cites

Before touching anything, confirm the suspension is genuinely a misrepresentation violation and not a different policy dressed up in similar language (identity verification, prohibited content, or an unrelated data quality suspension). The notice and the "Needs attention" tab in Merchant Center both name the specific policy. If it names misrepresentation, everything below applies; if it names something else, you're fixing the wrong problem by following a misrepresentation checklist.

Step 2: Audit the Storefront Against Google's Transparency Requirements

Google's own contact-information policy requires that your site display at least one of: a business address, phone number, email address, contact form, or verified social media business profile, visible before checkout, and consistent with what's entered in Merchant Center's Business Info settings (Google Merchant Center Help, missing contact information). Beyond contact details, the misrepresentation policy also expects an "About us" page describing who you are, current business branding (not a reseller using someone else's brand identity without disclosure), and written proof on file if you claim a partnership or certification.

Step 3: Reconcile Your Feed With What the Storefront Actually Shows

This is the step feed teams skip because it feels like a marketing problem, not a data problem, but availability and price mismatches between your feed and your live site are themselves a form of misrepresentation, and they're the easiest part of this to get wrong at scale. A single SKU showing availability: in_stock in the feed while the product page reads "temporarily unavailable, restocking in 6 weeks" is exactly the kind of unavailable-offer violation the policy names.

Before: <g:availability>in stock</g:availability><g:price>349.00 USD</g:price>, product page shows "Backorder, ships in 6 weeks" and a different price after a coupon auto-applies at checkout.
After: <g:availability>backorder</g:availability><g:price>349.00 USD</g:price><g:sale_price>329.00 USD</g:sale_price>, matching what the page and checkout actually show.

This is where a feed platform earns its keep: a rules engine that enforces "feed price must equal displayed price" and "feed availability must equal live stock status" across every row catches this class of mismatch before it becomes a suspension, rather than after. Feedance's feed protection rules and its Google Merchant Center integration can be configured to hold or flag rows where feed values drift from source-of-truth inventory and pricing data, which is a narrower job than fixing your business identity but a real part of preventing this specific trigger from recurring.

Step 4: Build an Evidence Package Before You Touch the Review Button

Google's official guidance says to fix identifiable issues first and only then request a review; it doesn't publish an exact evidence checklist. Merchant Center's own community guidance (not official policy, but written by people who've been through the process) recommends assembling proof that the business is real and operating as represented: a documented order history (commonly cited as roughly 300 completed orders over three to six months), screenshots of the site before and after fixes, and a clear written explanation of what was wrong and what changed (Merchant Center Community, misrepresentation fix guide). Treat this as a starting point, not a guarantee, since Google doesn't publish a minimum order count, and reviewers weigh the specifics of each case.

Step 5: Submit the Review Request Correctly

In Merchant Center, use the "Review and fix," "Fix," or "Request review" action on the Home page, the account banner, or the Diagnostics tab, not a generic support ticket. Google states reviews "typically take up to 3-7 business days" for policy suspensions, though the contact-information-specific fix can complete in as little as 24-48 hours (Google Merchant Center Help, fixing warnings and suspensions). Submit only once you've genuinely fixed the issue. Submitting to ask what's wrong instead consumes an attempt without addressing anything.

What Happens If You're Rejected Again

Google is explicit that repeated failed reviews can extend the account's cool-down period, during which the review button is disabled and no further request can be submitted until it lapses. If the underlying issue is something you genuinely cannot change (a business location, ownership structure, or historical pattern Google has already flagged), no amount of feed or storefront cleanup will reverse the suspension, and the account may be permanently ineligible for Merchant Center. In that scenario, the realistic options are a new, fully compliant storefront under accurate ownership, or shifting near-term spend to a channel with a different review process (Meta's catalog policies, for instance, use a separate commerce eligibility check) while the Google appeal runs its course.

Where This Breaks Down

No feed management platform, Feedance included, and the same is true of DataFeedWatch, Channable, Productsup or Feedonomics, can fix a misrepresentation suspension by itself, because the policy is about business identity and storefront honesty, not feed formatting. A feed tool can stop your feed from contradicting your own site (Step 3 above) and can make your data consistent across channels, but it cannot write your About Us page, verify your business registration, or manufacture an order history. If your business genuinely doesn't match what your storefront claims, this playbook won't help; that's a legal and operational fix, not a technical one. And if Google has already flagged the same underlying issue on a prior account, no appeal template will reverse that.

FAQ

Is a misrepresentation suspension the same as a product-level disapproval?
No. Product-level disapprovals (missing GTIN, wrong category, image policy) affect individual items and leave the rest of your feed live. Misrepresentation is an account-level policy violation that can take your entire account offline.

How long does a review request take?
Google states most policy reviews take up to 3-7 business days; the specific missing-contact-information fix can resolve in 24-48 hours once corrected.

How many times can I appeal?
Google doesn't publish a fixed number. Community guidance describes typically getting two or three review attempts before an account is treated as permanently ineligible, so each submission should follow a genuine fix, not a guess.

Will fixing my feed alone resolve this?
Only if the trigger was a feed-to-site mismatch (Step 3). If the cause is business identity, missing policies, or storefront claims, the feed was never the problem.

My business is legitimate. Why was I still suspended?
Automated enforcement flags patterns, not intent. Inconsistent business names across your site and Merchant Center settings, an outdated About Us page, or a stale "in stock" flag can trigger this even for compliant businesses; that's exactly what Step 2 and Step 3 are meant to catch.

Does this affect my Google Ads account too?
It can. Merchant Center and Google Ads policy enforcement are linked for Shopping and Performance Max campaigns, so a Merchant Center suspension typically stops related ad campaigns from serving product data.

Should I create a new Merchant Center account instead of appealing?
Only as a last resort, and only under genuinely different, accurate ownership: Google's enforcement looks at patterns across accounts, and a new account with the same underlying issue is likely to be suspended again.

Can a feed management tool prevent this from happening again?
It can prevent the feed-to-storefront mismatches described in Step 3 by enforcing rules that hold price and availability consistent with source data. It cannot police your business identity, policy pages, or marketing claims; that part is a manual, ongoing discipline.

Run a free feed audit to check whether your price and availability data actually match your storefront before you submit your next review request.