Google Merchant Center Misrepresentation: Suspension Fix & Appeal Checklist (2026)
Short answer: a Google Merchant Center misrepresentation suspension means Google believes an offer, business identity, product claim or important purchase condition may be misleading, incomplete or impossible to verify. It does not automatically mean you intentionally scammed anyone. Treat it as an account-level trust and data-consistency problem: read the exact issue, audit the store and feed together, complete identity verification if requested, then request one evidence-based review.
Google's Misrepresentation policy says it may review information from your products, website, accounts and third-party sources. It also says account suspensions can happen without a prior warning for serious violations. The policy is strict, so a persuasive appeal cannot substitute for a store and feed that are actually accurate.
First, identify which problem you have
Do not use a product-disapproval fix for an account suspension. The labels can look similar, but the scope is different:
| Merchant Center status | What is affected | First action |
|---|---|---|
| Product disapproval | One product or a group of offers | Open the product issue, fix the attribute or destination, then request the product review shown in Merchant Center |
| Account-level misrepresentation suspension | The account's ability to show products or listings | Audit the business, website, feed and account together before requesting an account review |
| Warning or limited visibility | Visibility may be reduced while the issue remains | Fix every issue named in the account and product diagnostics; do not assume a warning is harmless |
For product-level issues, see how to fix disapproved Google Shopping products. This guide focuses on the account-level Google Merchant Center misrepresentation search intent.
Do not appeal first: run the fix-first audit
The most common failure pattern is simple: a seller fixes one visible issue, clicks Request review, and leaves three other inconsistencies live. Google then reviews the same store and the appeal has not changed the evidence. Use this order instead:
- Save the suspension notice, account issue text, affected country and date.
- Record the business details currently shown in Merchant Center, the payment profile and the website.
- Audit the public store as a shopper and as a crawler: homepage, product page, policies, cart and checkout.
- Compare the exact feed values with the landing pages.
- Remove or repair offers that are not compliant or cannot be fulfilled.
- Complete identity verification if Merchant Center asks for it.
- Request a review only after the evidence is consistent.
Google Merchant Center misrepresentation checklist
Use the Evidence to save column as your appeal file. A green check is not a promise of reinstatement; it means you can explain and demonstrate the fix.
| Area | What to verify | Evidence to save |
|---|---|---|
| Business identity | Legal or operating name, address, phone and support email are accurate and consistent across Merchant Center, payment profile and site | Screenshots or exports of the matching settings and the live Contact/About page |
| Identity verification | Any requested business or identity verification is complete and readable | Confirmation in Merchant Center and the submitted document reference |
| Contactability | A customer can find a real support route without guessing; the email and phone actually work | Live URL, test message and response owner |
| Shipping | Destinations, costs, handling time and delivery expectations are stated before purchase and match the feed or settings | Policy URL, shipping settings and a test checkout |
| Returns and refunds | Eligibility, window, process, exclusions and who pays return shipping are clear and operational | Policy URL and a tested support workflow |
| Terms and privacy | Terms, privacy and any required legal notices are present and discoverable | Live links from the footer and rendered-page check |
| Product truth | Product identity, condition, material, size, compatibility, claims and included items are accurate | Product-page capture, SKU record and supplier evidence where relevant |
| Price and currency | The feed, structured data, product page, cart and checkout show the same current price and currency | Feed export plus a test product-page and checkout capture |
| Availability | In-stock, out-of-stock and variant states agree across the feed and destination | Feed status, inventory record and live variant test |
| Promotions | Discounts, bundles, memberships and required conditions are disclosed before the buyer commits | Promotion settings, terms and checkout test |
| Brand and partnerships | You do not imply authorization, certification or affiliation you cannot prove | Authorization or partnership evidence, or corrected wording |
| Checkout | HTTPS works, the product can be purchased, required costs are visible and no important condition appears only at the last step | A complete test order or documented checkout test |
| Technical access | Key pages return 200, are not intermittently 5xx, and important policy/product information is present in the rendered HTML | URL checks, crawl output and mobile screenshots |
| Feed hygiene | Invalid, unavailable or non-compliant offers are removed or corrected before review | Feed change log and the next successful fetch or upload |
Google's request-a-review guidance specifically calls out identity verification, visible and matching business details, functional shipping and return policies, and exact price, availability and product-attribute consistency. Those are the minimum audit lines; category-specific Shopping policies can add more.
The five areas that cause most failed appeals
1. Business identity does not line up
Compare the business name, address, phone number, support email and payment profile character by character. A brand name can be customer-facing, but do not use a different legal or operating identity in Merchant Center without understanding how the fields are meant to work. If you are an authorized partner, disclose the relationship accurately and keep proof.
Also check the public site. A footer that only says “Contact us” and opens a form is weaker than a clear support email, phone number and business details that a customer can actually use. Do not publish a made-up address or borrow another business's identity to look established.
2. Policies exist, but the buying conditions are still hidden
A policy link is not enough if it is empty, contradictory or impossible to follow. Check that a customer can answer these questions before paying:
- How much will shipping cost, and where do you ship?
- When will the order be dispatched and delivered?
- How many days does the buyer have to request a return?
- Which items are excluded, and who pays return shipping?
- How does the buyer request a refund, replacement or cancellation?
- Is there a subscription, membership, minimum order or other condition?
Do not copy a generic policy template and leave placeholders, a different brand name or a different country in the text. An inaccurate policy can create the same trust problem as a missing one.
3. The feed and destination disagree
This is the fastest way to turn a plausible store into an untrustworthy offer. Test the exact URL Google receives, not just the product preview in your admin:
| Field | Feed or Merchant Center | Destination and checkout |
|---|---|---|
| Price | Current value and currency | Product page, cart and payment step |
| Availability | In stock, out of stock or variant state | What a buyer can actually select |
| Product identity | Title, brand, condition, GTIN or identifier where applicable | The same product and included items |
| Shipping | Settings, cost and destination | The promise visible before payment |
| Returns | Account or policy settings | The public process a buyer can follow |
If the page changes price or availability after JavaScript loads, or the feed updates on a different schedule, document the timing and fix the mismatch before the review. If a product is not really available, remove it from the data source instead of hoping the crawler misses it.
4. Claims or relationships overstate what you can prove
Google's policy examples include false identity, impersonation, unsupported certification or authorization, products that cannot be delivered, and offers that hide important conditions. “Official,” “certified,” “clinically proven,” “guaranteed,” and similar language needs evidence and must be permitted for the product and market.
Do not use a competitor's brand name to make a different product look affiliated. If a comparison is legitimate, make the relationship clear and keep the claims factual. If you cannot support a claim, remove or rewrite it before appealing.
5. The store is technically available but not verifiable
Check the public URLs from outside your admin session. A temporary 5xx, a broken policy link, a redirect to the wrong country, a blocked product page or a checkout that cannot complete can turn a compliant-looking store into an unavailable offer. Review the homepage, one representative product per category, robots rules, canonical URLs, mobile rendering and the full checkout path.
This is not a request to hide content from Google. The goal is the opposite: make the same essential business, product and policy information available to shoppers and crawlers.
Worked example: a small mismatch can block a clean appeal
Consider this illustrative audit for one US SKU. The numbers are not a Google threshold; they show how to document a contradiction.
| Checkpoint | What the seller expects | What the buyer actually sees | Result |
|---|---|---|---|
| Product feed price | $49.00 USD | — | Baseline |
| Product page | $49.00 USD | $49.00 USD | Pass |
| Cart | $49.00 USD + $0 shipping | $49.00 USD + $0 shipping | Pass |
| Checkout | $49.00 USD total | $49.00 + $8 shipping = $57.00 | $8 mismatch |
| Returns | 30-day returns | Product page says “final sale” | Policy contradiction |
The arithmetic is simple: $49.00 + $8.00 = $57.00, while the feed and cart communicate a $49.00 delivered price. The seller should correct the shipping setting or disclose the $8 before the buyer commits, then make the returns language consistent across the site. A screenshot of the feed, product page, cart and checkout gives the appeal reviewer a much stronger change record than “we fixed our website.”
The same method works for identity and availability: write down the value in each system, mark the first disagreement, fix the source of truth, and retest the complete path.
How to request the review in Merchant Center
The UI can change, so follow the exact labels in your account. Google's current workflow is:
- Open Products → Needs attention or the account-level issue banner.
- Open the relevant setup or policy issue and read the affected country and explanation.
- Complete identity verification if the account asks for it.
- Choose I fixed the issue when you made the required changes. Choose I disagree with the issue only when your audit supports that conclusion and the issue is genuinely incorrect.
- If prompted, attach the requested documentation and submit one concise, specific explanation.
- Wait for the review and monitor the account email and issue status.
Google says account reviews typically take 7 business days, but complex reviews can take longer. Treat that as a current process note, not a guaranteed SLA. A review can apply to all issues for the country, so fixing only one product or one policy page may not be enough.
Appeal template: make it evidence-based
Do not paste a generic “please reinstate my account” paragraph. Replace every bracket with a fact you can verify and delete anything that is not true.
Hello Google Merchant Center team,
I reviewed the account-level misrepresentation issue for [business name], Merchant Center ID [ID], country [country]. Before requesting this review, I audited the website, product data and account details together.
I corrected the following items:
- Business name, address, phone and support email now match across [Merchant Center / payment profile / website URLs].
- Identity verification was completed on [date], if requested.
- Shipping, returns/refunds, privacy and terms are live in the footer and state [specific conditions].
- Product prices, currency, availability and attributes were reconciled between the feed and [representative product URLs].
- I removed or corrected [specific offers] that were unavailable, inaccurate or unsupported.
- I tested [product URL] through cart and checkout on [date].
Supporting URLs and documents: [list only relevant public URLs or requested files].
I believe the store and product data now accurately represent the business and the offers shown to customers. Please review the account based on these changes. I will follow the applicable Shopping policies and keep the site, feed and account information synchronized.
Thank you,
[name and role]
The template is useful only when the statements are true. Google says appeals should be thorough, accurate and honest; unsupported assurances can hurt more than a short, precise explanation.
What not to do after a rejection
- Do not submit the same appeal repeatedly without a new audit or new evidence.
- Do not open a new Merchant Center account or switch domains to bypass a suspension. Google's policy help warns that deleting an account does not fix the underlying suspension.
- Do not remove compliant products temporarily and upload them again after approval to create a gap in enforcement.
- Do not make your policies less specific just to pass a crawler; make them accurate and usable for customers.
- Do not rely on a third-party “guaranteed reinstatement” timeline. Google controls the review and any cooldown period.
If the issue remains, compare the latest account message with your audit, resolve any newly identified problem, and use Google's support path. Do not interpret an unchanged status during the stated review window as proof that the site is permanently blocked.
Prevention: a monthly Merchant Center trust check
Once the account is reinstated, keep a small change log. Before changing a theme, payment profile, shipping program, domain, product feed or promotion, test one product end to end. Then verify:
- identity and contact information still match;
- the footer links still work;
- feed prices and availability match the live destination;
- shipping and return promises still apply to every targeted country;
- claims, discounts and subscriptions disclose their conditions; and
- the site, sitemap and product URLs return stable responses.
This is the practical difference between an appeal fix and a durable compliance system: the next feed refresh should not reintroduce the same mismatch.
Frequently asked questions
Does “misrepresentation” mean Google thinks I am a scam?
Not necessarily. It is a serious Shopping policy category covering misleading, incomplete or unverifiable business and offer information. Audit what Google and a customer can verify rather than guessing at intent.
Can I appeal without changing anything?
Only if your audit shows the issue is genuinely incorrect and you can explain why with evidence. If there are visible mismatches, fix them first; an appeal does not replace the fix.
How long does a Merchant Center misrepresentation review take?
Google's current help guidance says account reviews typically take 7 business days and may take longer for complex reviews. There is no reliable universal reinstatement promise.
Do I need an About Us page?
The useful requirement is transparent, accurate and accessible business information. An About page can help explain the business, but it is not a magic checkbox; make the contact, identity, policies and product claims verifiable across the site.
Should I delete the account and start again?
No. A new account or domain does not solve the underlying policy or identity problem and can create additional account-linkage risk. Resolve the existing issue through the official workflow.
What is the difference between a product disapproval and misrepresentation?
A product disapproval is normally scoped to an offer or product issue. Misrepresentation is an account-level trust and transparency problem, although product and feed errors can contribute to the overall review. Diagnose the exact scope shown in Merchant Center.
Sources checked (August 17, 2026)
- Google Merchant Center: Misrepresentation policy — prohibited practices, review scope and appeal standard.
- Google Merchant Center: Request a review of your issues — identity verification, transparency audit, data consistency and review workflow.
- Google Merchant Center: Misrepresentation for Shopping ads — examples of omitted information, unavailable offers and unsupported relationships.
This is an operational SEO guide, not legal advice and not a guarantee of reinstatement. Use the current issue text in your Merchant Center account and the official policy pages as the final authority. For the related feed problem, start with Google Shopping feed optimization.
The EshopPick operations desk covers TikTok Shop onboarding, eligibility, fulfillment, account health, appeals and payouts. Policy articles state their market scope and verification point so sellers can turn rules into executable steps.
Related reading
Ready to act on it? Let AI run your ads
GrowthGPT generates ad creative, analyzes competitors, and launches + optimizes your ads around the clock.
