What Google Reviewers Actually Check in a Misrep Appeal (2026)

When you submit a Google Merchant Center misrepresentation appeal, a human reviewer (after algorithmic triage) sits down at a monitor and runs through a specific checklist. They are not reading your prose deeply. They are clicking your cited URLs, opening your policy pages, comparing your business name across properties, and looking for any one item that still fails. Their goal is to find a violation, not discover compliance.

This article reverse-engineers that process based on patterns observed across recovered accounts. The 14 checks below are what reviewers actually look at, in roughly the order they do it. Making this process easy for them is what moves appeals from denied to approved.

The review pipeline (algorithm then human)

Every appeal flows through this sequence:

1. Automated triage (seconds). Filters obvious cases: no changes since last appeal, no specific URLs cited, account in a perma-blocked category. Failing triage = automatic denial within 24 hours.
2. Human review (5-45 minutes). The reviewer reads the appeal, opens cited URLs, verifies changes against the policy, makes the approve/deny call.
3. Quality assurance (sampled). A small percentage of human reviews get spot-checked by a senior reviewer. Affects training the next batch; does not change individual outcomes.

The 14 checks below happen during step 2.

The 14 reviewer checks in order

1. Has anything actually changed since the last appeal?

First check, every time. Reviewer compares cited URLs against the cached state from the previous review. If the cited pages return identical content, the appeal is denied within minutes. This is the single biggest reason appeals fail on subsequent attempts.

How to pass: ensure Google has re-crawled your site between appeals. Trigger via Search Console URL Inspection and your platform's Google channel re-sync.

2. Does the business name match across properties?

Reviewer opens: your website footer, your contact page, your GMC business info, your Google Business Profile (if claimed), your LinkedIn. They look for variants. "Olivia The Label" vs "Oliviathelabel" is a violation.

How to pass: pick one canonical name, use it character-for-character on every property.

3. Is the physical address present and consistent?

Reviewer scrolls site footer and contact page. They check for: street, city, state/region, postcode, country. P.O. boxes fail. Missing addresses fail. Different addresses across pages fail.

How to pass: registered business address, identical across footer, contact, GMC, GBP.

4. Is the phone number present in international format?

+country-code format. Same number across pages.

5. Are the four policy pages real, linked, and specific?

Reviewer clicks footer links for: return policy, shipping policy, privacy policy, terms of service. They check that each page exists, has substantive content, and includes business name in body text. Template-only pages fail [4].

6. Does the return policy specify a window?

"30 days from delivery" passes. "Contact us for returns" fails. The window must be a number.

7. Does the privacy policy mention the business name in body text?

Reviewer searches the rendered HTML of the privacy page for the business name. Template placeholders like [STORE_NAME] fail. Customized content with the business name in the paragraph text passes.

8. Is the About page substantive?

Reviewer reads at least the first paragraph. "We sell great products" fails. Specific founding year + what you sell + where you operate + who runs it passes.

9. Are subscription options pre-selected on product pages?

Reviewer opens 1-3 product pages in incognito. They look at the purchase form. Pre-selected subscription radios fail — see hidden subscription triggers on Shopify for the full pattern.

10. Is the price visible in raw HTML?

Reviewer's crawler reads server-rendered HTML. If the price element is empty until JavaScript executes, the reviewer's automated check flags the page as price-mismatch even if you see the price.

11. Does product schema validate?

Reviewer's tool tests Product JSON-LD against schema.org. Missing required fields (name, image, offers.price, offers.priceCurrency, offers.availability) fail. Two conflicting schemas on the same page fail.

12. Are policy violations present elsewhere?

Reviewer scans for related violations even if the original suspension cited only one. Untrustworthy promotion patterns (fake strikethroughs, hidden subscriptions) found during a misrepresentation review get added to the denial reason (see how Google distinguishes misrep from untrustworthy from unacceptable).

13. Has Google Business Profile been claimed?

Reviewer searches business.google.com for your business name. An unclaimed or unverified GBP weakens the appeal even if not the primary cause.

14. Are third-party signals consistent?

Reviewer checks Trustpilot, Sitejabber, Google Reviews. Patterns of complaints about specific bad behaviors (non-fulfillment, ghost customer service) trigger the unacceptable-business-practices review on top of the misrepresentation review.

What makes a reviewer approve quickly

Reviewers approve fast when:

• The appeal lists specific URLs they can open and verify in seconds
• The changes are real and live (no caching issues)
• The cross-property signals (GBP, LinkedIn, third-party reviews) are consistent
• The site visually looks like a real business (not a hastily-built funnel)
• The appeal text is short, evidence-based, and free of apologetic prose

What makes a reviewer deny

Reviewers deny when:

• The cited URLs return the same content as the last review
• The appeal cites generic changes without verifiable evidence
• Any of the 14 checks above still fails
• The reviewer finds a new violation during the check
• The appeal is long, defensive, or blame-shifting

Subtle signals reviewers weight

Beyond the 14 checks, reviewers note:

• Appeal frequency. Multiple appeals in 30 days without substantive changes signal lack of understanding.
• Cross-property change timing. If GBP and LinkedIn were updated the day before the appeal, that suggests prep specifically for the review rather than ongoing business identity.
• Customer-facing tone. Sites with high-pressure copy, fake urgency, exaggerated claims get stricter interpretation on borderline cases.
• Product page substance. Pages with 80 words of generic copy get less benefit of the doubt than pages with 250+ words of specific content.

Writing appeals reviewers respond to

The structure reviewers respond to:

Misrepresentation suspension review.

1. Business name: identical across yoursite.com/footer, /contact, GMC business info, business.google.com/[gbp-id], linkedin.com/company/yourbrand. Standardized 2026-05-12.

2. Physical address: 123 Main Street, Suite 100, City, State 12345, USA on /contact, footer, GMC, GBP.

3. Phone: +1 555 123 4567 on /contact, footer, GMC, GBP.

4. Return policy at /policies/refund-policy: 30-day window, eligibility, refund process, refund timeline. Updated 2026-05-12.

5. Privacy policy at /policies/privacy-policy: customized with "[Your Brand Pty Ltd]" in body, specific data collection (Shopify payments, Google Analytics, Klaviyo), third parties named. Updated 2026-05-12.

6. Subscription default on /products/*: changed to one-time purchase. Verified in incognito.

7. Product schema validates clean on 3 sample products (tested via Rich Results Test 2026-05-13).

8. Google channel resync 2026-05-13; GSC URL Inspection re-crawl requested same day.

Please re-review.

That structure gets read, verified, and approved at a higher rate than apologetic prose by a factor of 2-3x in our observation.

Make the reviewer's job easy

The reviewer is not your enemy. They are someone doing a job under time pressure with a checklist. Make verification easy and they approve. Make it hard and they deny by default.

For the escalation playbook when reviewers keep denying, see misrepresentation appeal denied 3+ times. For the day-by-day recovery framework, see 7-day GMC recovery plan.

Frequently asked questions

FAQ block is rendered by the page using the faqs field above.

Sources

Sources block is rendered by the page using the sources field above.