Merchant Center Says “Missing Return & Refund Policy” — But You Already Have One?
You open Merchant Center and see:
Missing return and refund policy
That seems strange.
Your store already has a returns page.
Maybe it even says:
30-day returns
So why is Google still complaining?
I would not start by creating another return policy.
First, I would check whether the policy you already have is actually easy to find, complete and consistent.
Because those are different things.
A return policy can technically exist on your website and still be difficult for customers — and Google — to understand.
First, Pretend You’re a New Customer
Open your store in an incognito window.
Do not use the admin account.
Do not use a bookmark that goes directly to the return page.
Start on a product page.
Now ask:
Can I find the return policy without hunting for it?
Google's current Merchant Center guidance specifically says the return and refund policy should be easily accessible to customers.
A common solution is a permanent footer link such as:
Returns & Refunds
or:
Return Policy
that appears across the store. 谷歌帮助
If the only way to reach your policy is:
Homepage → Help → FAQ → Orders → Returns → another link
I would simplify that.
The customer should not need detective skills to learn whether they can return a product.
“We Accept Returns” Is Not a Complete Policy
This is another problem I see in ecommerce sites.
A returns page says:
We accept returns. Contact us for more information.
Technically, you have a return statement.
But it leaves almost every important question unanswered.
A useful return policy should clearly explain things like:
How long does the customer have to return the product?
What product condition is accepted?
How does the customer start the return?
Who pays return shipping?
Is there a restocking fee?
How and when is the refund processed?
Google's current guidance specifically calls for the policy to explain relevant requirements and timelines, and its Merchant Center return-policy setup includes return windows, methods, fees and refund-processing details. 谷歌帮助
So if your policy is only two sentences long, the problem may not be that Google failed to find it.
The problem may be that it doesn't clearly describe how returns actually work.
If You Don’t Accept Returns, Say That Clearly
Some merchants make another mistake:
They don't accept returns, so they simply don't create a return-policy page.
That is not the cleanest approach.
Google explicitly says that if your store doesn't accept returns or refunds, you should clearly state that on the website. 谷歌帮助
For example:
All sales are final. We do not accept returns or exchanges except where required by law.
The exact wording should match your real business policy and applicable law.
The important part is that the customer is not left guessing.
“No returns” is still a return policy.
Silence is not.
Check Whether Your Website Contradicts Itself
This is one of the most useful checks.
Imagine your dedicated returns page says:
30-day returns
but your footer banner says:
14-day returns
And an old FAQ says:
Returns accepted within 7 days
Which one is correct?
Google specifically recommends that return and refund information stay consistent throughout the website, including places such as the footer, dedicated returns page and promotional or informational banners. 谷歌帮助
So I would search the entire site for phrases like:
return
refund
exchange
restocking fee
Then look for old information.
This happens frequently after a store changes policy but only updates one page.
Give the Return Policy Its Own URL
I would also avoid burying the policy inside one giant page called:
Terms, Privacy, Shipping, Returns & FAQ
Google's current best-practice guidance recommends a separate return-policy URL, rather than combining it with FAQs, terms or privacy information. 谷歌帮助
Something like:
yourstore.com/returns
is much easier to understand than:
yourstore.com/legal-information
with the return section hidden 4,000 words down.
This helps customers too.
They usually want one answer:
“Can I return this?”
They should not have to read your privacy policy first.
Make Sure the Policy Page Works Without Login
This sounds obvious, but it matters.
Your return-policy page should be publicly accessible.
A customer should not need to:
sign in
create an account
enter an email address
or:
submit personal information
just to read your return terms.
Google's current best-practice documentation specifically recommends making the return-policy URL accessible to all users without requiring sign-in or personal information. 谷歌帮助
Test it in an incognito window.
If you cannot read the policy as a completely new visitor, fix that first.
Check the URL You Gave Merchant Center
Now move from the website to Merchant Center.
Go to:
Products & store → Shipping and returns → Return policies
Open the return policy.
Check the URL.
Does it still point to the correct page?
Stores change domains.
Pages get renamed.
Platforms migrate.
A URL that used to work may now redirect somewhere unexpected — or return a 404.
Google currently requires return-policy URLs to point to a valid, reachable policy page. For product-level return-policy URLs, Google also requires the policy domain to match the product domain and the URL to represent the actual policy for that product. 谷歌帮助
So test the exact URL Merchant Center has stored.
Not just the page you remember creating.
Your Merchant Center Policy Must Match Your Website
Suppose Merchant Center says:
30-day return window
Free returns
But your website says:
14-day return window
Customer pays return shipping
Now you have a bigger problem.
Google's current guidance says the return policy configured in Merchant Center should match the policy on your website.
Even details such as fees matter.
Google gives the example that if your site applies a restocking fee, the Merchant Center return information should reflect it too. 谷歌帮助
I would compare these side by side:
Return window
Return method
Return shipping cost
Restocking fee
Refund processing time
Product condition requirements
They should tell the same story.
Watch for Product-Specific Return Policies
Not every product necessarily has to follow the same policy.
Imagine:
Most products:
30-day returns
Clearance products:
Final sale
Electronics:
14-day returns
Google supports additional return policies for specific groups of products through return_policy_label.
It also now supports product-level return configuration using the returns attribute in product data. 谷歌帮助
That flexibility is useful.
It also creates another place where things can go wrong.
For example:
You create a special return policy called:
final_sale
but the feed contains:
return_policy_label = clearance
Those don't match.
Google says if a product's return-policy label does not correspond to an existing policy, the default policy may apply instead. 谷歌帮助
If only one product group has the wrong return information, I would inspect labels and product-level overrides before changing the storewide policy.
One Mistake I Would Avoid
Do not create a fake generous return policy simply to satisfy Merchant Center.
For example, don't tell Google:
30-day free returns
if your actual website only accepts:
7-day customer-paid returns
That may clear one configuration problem while creating a policy-consistency problem.
The goal is not:
“What return policy does Google want me to have?”
The goal is:
“Does Google clearly understand the return policy my business actually offers?”
Those are different questions.
A Quick Example
Imagine the store has this page:
yourstore.com/refunds
It says:
Returns accepted within 30 days.
But Merchant Center still reports an issue.
I would keep reading.
Maybe the page does not explain:
- how to request the return
- whether used products are accepted
- who pays return shipping
- when refunds are issued
Then I check the footer.
It contains:
14-day returns.
Then Merchant Center.
It says:
30 days, free return shipping.
Now the real problem is obvious.
The store doesn't have one clear return policy.
It has three slightly different versions.
Creating a fourth page won't fix that.
Consistency will.
What I’d Check in About 10 Minutes
If Merchant Center says the return and refund policy is missing or unclear, I would check:
Website footer
→ Is there an obvious Returns / Refunds link?
↓
Policy page
→ Does it explain window, method, conditions and fees?
↓
Incognito
→ Can anyone read it without signing in?
↓
Site consistency
→ Do FAQ, footer and banners say the same thing?
↓
Merchant Center URL
→ Does it point to the exact current return-policy page?
↓
Merchant Center details
→ Do the return window, fees and method match the website?
↓
Product overrides
→ Are any return_policy_label or product-level return settings changing the policy?
That usually tells you whether you have:
a missing policy
a visibility problem
an incomplete policy
or:
a consistency problem.
One Important Detail: Merchant Center Setup Does Not Replace the Website
This deserves its own section because it is easy to misunderstand.
You can configure a return policy perfectly inside Merchant Center.
That does not mean your website no longer needs a visible return and refund policy.
Google explicitly says the website policy requirement is separate from setting up returns in Merchant Center. 谷歌帮助
You need both sides to make sense:
Website
Customers can understand the real policy.
Merchant Center
Google receives a matching representation of that policy.
That distinction is important.
How Long Can a Return Policy Review Take?
After you change Merchant Center return-policy information, don't assume the result will update instantly.
Google's current best-practice guidance says review of a newly updated return policy may take up to 10 business days. 谷歌帮助
So avoid this cycle:
Change policy.
Wait two hours.
Change it again.
Wait one day.
Delete it.
Create another one.
You can make troubleshooting harder by constantly changing the evidence while Google is still reviewing it.
Fix the actual inconsistencies first.
Then allow the review process to complete.
Where Mingche Fits — And Where It Doesn't
A missing return-policy warning is mainly a store-policy and Merchant Center configuration issue.
Mingche's free Product Page Check is not a dedicated return-policy audit.
But if you're also seeing problems involving:
- price
- availability
- variants
- structured data
you can still check three public product pages from the same store.
Check 3 Product Pages for Free →
That answers a different question:
“Do my public product pages contain inconsistent machine-readable product information?”
For a pure return-policy problem, focus first on:
website policy → policy URL → Merchant Center policy → product-level overrides.
Bottom Line
When Merchant Center says your return policy is missing, don't ask only:
“Do I have a returns page?”
Ask:
“Can a new customer clearly find, understand and verify the same return policy that I gave Google?”
Then check:
visibility
→ policy details
→ website consistency
→ policy URL
→ Merchant Center settings
→ product-specific overrides
A return policy is not just another box to tick.
It is part of the purchase information a shopper uses to decide whether your store is trustworthy.
And Google wants the policy it shows to match the policy the customer will actually get.
Disclaimer
Mingche is an independent product-data readiness service and is not affiliated with or endorsed by Google.
Product-data auditing or correction does not guarantee approval, visibility, ranking, traffic or sales. Google independently determines Merchant Center eligibility and how products appear across its services.
Comments
Post a Comment