Merchant Center recovery guide

Misrepresentation is rarely one obvious checkbox.

Google Merchant Center can flag a store when the business, website, product data, policies, or checkout do not present a consistent and trustworthy picture. Before you appeal, audit the whole customer journey—not just the product feed.

Useful answer

What “misrepresentation” usually means in practice

Google’s policy is broader than “your ad is misleading.” Google says it may review your listing, website, accounts, and third-party sources. That makes consistency across your entire store especially important.

Think of the suspension as a trust consistency failure, not just a feed error.

Recent Merchant Center and ecommerce community threads repeatedly show the same frustration: merchants can complete obvious fixes and still receive a broad policy label without a page-level explanation.

The safest response is not to keep changing random things. Build a clean evidence trail: make your legal/business identity consistent, keep contact details easy to find, make shipping and returns unambiguous, remove broken or placeholder content, verify that pricing and availability match, and complete a full checkout test.

01→

Your business

Legal name, real contact details, location, identity and operating information.

02→

Your storefront

Policies, navigation, product content, claims, domain quality and customer-facing transparency.

03→

Merchant Center

Business information, product feed, pricing, availability, shipping and account verification.

04Review

Consistency check

Google evaluates whether those signals tell the same truthful story.

Interactive pre-appeal audit

Check the store before you request another review.

Tick only what you have personally verified. This is a readiness tool, not a promise of approval.

0%
Audit readinessStart checking

Work through all eight checks before deciding whether your store is ready for a review.

✓

Business details match

Legal/business name, address, phone and email are consistent between the website and Merchant Center.

✓

Contact info is easy to find

Customers can clearly find a real contact method and business information without hunting for it.

✓

Shipping policy is specific

Processing times, destinations, delivery expectations and fees are clear and match your setup.

✓

Return/refund policy works

Eligibility, timeframes, method and customer steps are explained and operational.

✓

Product data matches the site

Price, availability, title, description and product identity do not conflict with landing pages.

✓

No broken or placeholder content

Navigation, product pages, images, forms and policy links work across desktop and mobile.

✓

Checkout works end-to-end

A shopper in the target country can add to cart, see total cost, and complete checkout without hidden blocks.

✓

Claims are accurate

No fake scarcity, unrealistic promises, hidden material terms, or misleading business/product statements.

AUDIT 01

Identity first

Start with business name, address, phone, email and verification. Inconsistency here undermines every other signal.

AUDIT 02

Customer promises

Compare shipping, returns, pricing and availability across the site, checkout and Merchant Center.

AUDIT 03

Technical reality

Test links, mobile layouts, product pages and checkout as a real customer would—not only as the site owner.

Before another appeal

Fix first. Document second. Appeal third.

1

Freeze random edits

Stop changing unrelated items just to “try something.” Make an audit list and record each change.

2

Make website + Merchant Center agree

Update product data and business information so the same facts appear everywhere.

3

Retest the customer journey

Use mobile and desktop, test navigation, policies, cart and checkout, and verify the target-country experience.

4

Submit an accurate appeal

Google’s current guidance says to be thorough, accurate and honest when you believe the issue has been fixed or applied in error.

Sources & community signal

Official policy first. Community reports second.

Community posts are useful for spotting recurring pain points, but they are not Google policy. Use them to improve your audit—not as proof that a specific workaround will succeed.