Why Google Reads Your Return Policy as a Trust Signal
Google Shopping is a marketplace, and Google wants every shopper on it to know their rights before they buy. Your return policy carries that information: how long they have to send an item back, how they get their money returned, and what it costs them. When that page is clear and honest, it signals a real business. When it is missing or murky, Google reads risk.
The policy has to satisfy two audiences at once. A human shopper needs to understand it, and Google's crawler needs to read it, verify it, and match it against your Merchant Center settings. A mistake that trips up either one can surface as a misrepresentation flag, even when your products and prices are perfect.
Leaving Out a Return Policy Entirely
The simplest mistake is having no policy at all. Google requires a clear return and refund policy, reachable from your product pages and checkout, as a condition of running Shopping ads and free listings. A store without one reads as a store that does not stand behind what it sells.
Stating that you offer no returns does not get you out of it. Google still expects the policy written plainly, even when the answer is no returns, and it reads the silence itself as the violation. Write the policy, publish it, and link it where shoppers and Google can both find it.
A Return Window Without a Number
Google wants a specific return window measured in days, counted from the delivery date. Phrases like a reasonable time, contact us to discuss, or returns handled case by case fail the test, because they promise nothing a shopper can hold you to. The window has to be a number: 14 days from delivery, 30 days from delivery, something concrete.
The same specificity applies to the rest of the policy. Google's review looks for the refund method, whether that is the original payment, store credit, or an exchange, and the time it takes to process a refund once you receive the return. Leave any of these vague and the policy can be rejected, which puts the whole account at risk.
A Website That Doesn't Match Merchant Center Settings
This mistake causes more suspensions than almost any other. Google compares the return policy on your website against the one configured in your Merchant Center settings, and it expects them to match completely. Not roughly. Completely. When your Merchant Center return window says 30 days and your website says 14, the gap reads as misrepresentation.
The match has to hold across every detail: the return window, the refund processing time, return fees, restocking charges, and your contact information down to the format. A phone number written one way in Merchant Center and another way on the site counts as a mismatch. Before you appeal, copy each value from your Merchant Center settings and confirm the exact same value appears on your policy page.
Product Pages That Contradict the Policy Page
Your policy page can be flawless and your account can still fall over a claim somewhere else on the site. A trust badge app that stamps free 30-day returns on every product page, while your actual policy states a 15% restocking fee or a shorter window, creates a contradiction Google treats as misrepresentation. The product page makes a promise the policy breaks.
These claims often come from places you did not write by hand: a theme template with built-in return language, a third-party app, imported supplier descriptions, or a seasonal banner that updated the product pages but not the policy. Google does not separate an honest mistake from a deliberate one. When two parts of your site disagree, the account pays for it. Audit your product pages, your banners, and your apps for any return claim, and make every one of them match the policy page.
Not Sure Which Policy Detail Triggered the Flag?
Google names the policy but rarely the specific gap. Send us your suspension notice and your store URL, and within 48 hours you get a written verdict on which signal caught your account and whether the case has a real path forward.
A Policy Google's Crawler Can't Read or Reach
A policy only helps if Google can actually read it and a shopper can actually reach it. Three technical mistakes break this. Publishing the policy as an image or a PDF hides the text from Google's crawler, which needs readable HTML. Burying the policy so it lives only in the homepage footer, unreachable from a product page without navigating back, fails Google's accessibility check. Merging the return policy into your FAQ, terms, or privacy page, instead of giving it its own dedicated URL, muddies what Google is trying to verify.
One version of this mistake crosses a harder line. Serving Google's crawler a clean, compliant policy while showing users a different one moves from a technical slip into cloaking, which Google treats as circumventing its systems. If a circumventing flag is part of your suspension, our guide on how to Resolve Circumventing Systems Policy covers that recovery. Keep the policy as live HTML text, on its own URL, linked from every product page and the checkout, and identical for crawler and customer alike.
Vague Non-Returnable Exclusions
When some of your products cannot be returned, Google requires you to say so clearly and specifically. A catch-all line like some products may not be returnable backfires, because Google reads a vague exclusion as an attempt to wriggle out of returns and flags it as misrepresentation. Name the categories or products that are final sale, and explain why, whether the reason is hygiene, perishability, or a custom build.
Clarity protects you here. A shopper who knows upfront that a particular item is final sale cannot feel misled at checkout, and Google can verify that the exclusion is honest rather than a loophole. Spell out what cannot come back, and the exclusion strengthens the policy instead of weakening it.
A Policy That Doesn't Match How You Operate
A written policy that your business does not actually honor is worse than no policy. Google's misrepresentation rules specifically cover denying a return or refund when your posted policy allows for one. When your page promises 30-day refunds but your team turns customers away at day 20, the gap between the promise and the practice is exactly what Google watches for.
Complaints feed this. Google weighs customer reports and third-party signals alongside your site, so a pattern of shoppers saying they could not get a promised refund can trigger a review on its own. Write a policy you can deliver every single time, then deliver it. The safest policy is one your operation already matches without straining.
How to Fix Your Return Policy Before You Appeal
Appealing before the policy is fixed wastes the attempt. Google reinstates misrepresentation accounts only in compelling circumstances, and a review that still finds a gap almost always fails. Work through the policy first, then appeal once.
- Publish a complete policy. State the return window in days from delivery, the refund method, the processing time, return fees, conditions, and any final-sale exclusions, in readable HTML on a dedicated URL.
- Match every value to Merchant Center. Copy each detail from your Shipping and returns settings and confirm the identical value on your website, including your contact information.
- Reconcile the whole site. Check your product pages, banners, and apps for any return claim that contradicts the policy, and bring them all into line.
- Document and appeal once. Note what you changed, with dates, then send a single clear appeal rather than several rushed ones.
If the flag still feels unclear after a self-review, a structured Free Diagnosis of your store can pinpoint the exact policy signals Google objects to before you spend an appeal on guesswork. For a full walkthrough of the reinstatement process, our guide to Resolve Google Merchant Center Misrepresentation Policy covers each step in depth.
Keeping Your Return Policy Compliant
A return policy is not a set-and-forget page. Every theme change, catalog update, seasonal promotion, and legal shift can knock your policy out of sync, and Google's enforcement keeps tightening. After the 2026 verification changes, reviewers read a thin or inconsistent policy more strictly than they did a year ago.
Build a habit around it. Review the policy whenever you change your site or your Merchant Center settings, keep the website and the account in lockstep, and give Google up to ten business days to review any update before you expect it to take effect. A policy you maintain on purpose keeps the misrepresentation flag away for good.