What “misrepresentation” really means (not a single flag)
In practice, misrepresentation is an aggregation of signals that suggest: “this store may be unclear, inconsistent or hard to verify”.
You don’t need malicious intent to trigger it. A combination of ambiguous pages, weak seller identity, or contradictory product data can be enough.
What Google wants to confirm
- Who sells (legal identity, location, contactability).
- How refunds and returns work (clear, specific procedures).
- How shipping works (costs, times, tracking).
- Whether product pages match prices/availability/data.
What increases risk
- Policies that are thin, broken, hidden or contradictory.
- Hard-to-reach support or missing seller info.
- Domain/subdomain confusion (looks like two businesses).
- Price/stock mismatches (page vs feed vs structured data).
Goal: make your store “self-explanatory”. A reviewer should understand the essentials in under a minute.
Common triggers and signals that raise the risk
Think of misrepresentation as a “confidence score”. The more uncertainty you introduce, the more likely you fall below the acceptance threshold.
Ambiguity
Generic legal pages, vague guarantees, unclear inclusions/exclusions, “too good to be true” claims without conditions.
Inconsistency
Different pricing/availability between product page, structured data and feed; domain/subdomain identity mismatch; conflicting copy.
Unverifiable support
No working support channel, missing email, broken forms, no response expectations, no company details.
Checkout opacity
External checkout without explanation, confusing payment steps, important conditions revealed only at the end of the funnel.
Policy pages that must be clear, reachable and consistent
Having a policy page is not enough. It must be readable, specific, and operational — and it must match what you actually do at checkout and post-purchase.
Recommended structure
Use an “In short” section (3–5 bullets) at the top, then the full policy below. Reviewers often scan the summary first.
Returns & refunds (must include)
- Return window (days) and condition requirements.
- How to request a return (steps, address, RMA/contact).
- Who pays return shipping and when it applies.
- Refund timing and method (original payment method, store credit rules).
- Exceptions (hygiene items, custom products, sealed software, etc.) if applicable.
Shipping (must include)
- Costs, delivery times and serviced areas.
- Carriers and tracking availability.
- Handling time vs delivery time (especially for pre-orders/backorders).
- International shipments and duties/taxes if relevant.
Contact/support (must include)
- Support email or helpdesk that works.
- Expected response time (e.g. 24–48 hours).
- Seller identity references (company name, address, VAT/registration where applicable).
Seller identity: domain/subdomain, legal info and contactability
Many modern setups use a “corporate site” plus a store on a subdomain. That’s fine — until it looks like two different sellers.
Your job is to remove confusion.
How to reduce ambiguity
- Repeat seller identity (legal name, VAT/registration, address) on the store footer and contact page.
- Bidirectional links: corporate → store and store → corporate (About, Support, Policies).
- Keep policies in the same “perimeter” users purchase in (avoid policies on one domain and checkout on another without explanation).
- Avoid unexpected redirects (geo redirects, forced currency changes) without a clear notice.
Reviewer heuristic: if your store feels “hard to reach” or “hard to verify”, risk increases even when products are fine.
Product pages: non-ambiguous content, condition, warranty, included items
Misrepresentation often becomes visible on product pages: unclear condition, unclear inclusions, unclear warranty, misleading images or “too aggressive” claims.
Build product pages like a reviewer will audit them.
Near the price / buy button
- Condition (new / used / refurbished) and grade if applicable.
- What’s included / not included (charger, box, accessories).
- Warranty summary (duration + key terms link).
- Quick links to shipping and returns.
In the details section
- Clear specs and compatibility notes.
- Limitations or exclusions (if any), written plainly.
- Non-deceptive images (no accessories in photos unless clearly stated).
- No “absolute” claims without conditions (avoid ambiguity).
Simple “safe” template line
“Refurbished device, tested and cleaned. Grade A: minimal cosmetic signs. Includes: device. Excludes: original box.
Warranty 12 months. Returns within 14 days according to policy.”
Consistency checks: price/availability, variants, structured data
A high-frequency misrepresentation trigger is contradiction: the page shows one thing, structured data declares another,
and the feed sends a third. Variants and caching make this worse.
High-impact checks
- Price: visible price matches Offer price and feed price (currency + taxes included logic).
- Availability: UI “in stock/out of stock/preorder” matches Offer availability.
- Variants: switching variant updates price/stock (and does not leave stale structured data).
- Duplicate markup: avoid multiple Product/Offer JSON-LD blocks with different values.
- Caching/CDN: ensure price/stock isn’t served “stale” to crawlers/users.
If you can’t keep JSON-LD in sync with variant selection reliably, prefer stable URLs per variant or a single “page truth” per offer.
Tracking & cookie banners: trust mistakes (not only GDPR)
This is not just a privacy issue — it’s a trust experience issue. Inconsistent cookie banners, broken consent flows,
or tags firing in confusing ways can contribute to an overall “opaque” feeling.
- Use a clear CMP with consistent policy text and correct link destinations.
- Ensure checkout and support pages are not blocked by consent mistakes.
- Avoid banner behavior that makes the site feel broken or deceptive.
- Keep privacy/cookie pages aligned with what is actually loaded.
Review-proof checklist (before requesting a review)
A) Transparency
- Support contact works and is visible.
- Returns/refunds policy is specific, complete and easy to find.
- Shipping policy has costs, times, tracking and areas.
- Terms and seller identity are consistent across the store.
- External checkout (if any) is clearly explained.
B) Consistency
- Price and availability match across page + feed + structured data.
- Variants are handled correctly (price/stock per variant).
- Condition (new/used/refurbished) is explicit and consistent.
- Images and copy are non-ambiguous (no misleading accessories/claims).
- No duplicated Product/Offer structured data with conflicting values.
Want a quick risk baseline before your next review request?
Generate a free report: trust signals, policy visibility, product-page consistency and structured-data red flags — in ~60 seconds.
No credit card · Audit ~60s · Shareable link