Fixing Google's "Missing field hasMerchantReturnPolicy" warning
Published October 4, 2026 · Updated November 11, 2026
Google's “Missing field hasMerchantReturnPolicy” warning points to missing returns information in product markup. Compare your public terms, Merchant Center settings and page markup to choose a fix. This guide also covers the related priceValidUntil and aggregateRating warnings.
Jump to a section
What the warning means
Google's merchant listing markup requires only price and priceCurrency on an Offer. hasMerchantReturnPolicy is recommended, so its absence is a warning, and the page still qualifies for merchant listing results. What you lose is the return window and return cost Google can show next to the product when it has them.
As with shipping, Google's broader merchant-listing guidance puts product-level Merchant Center feeds ahead of Content API settings, Merchant Center or Search Console settings, product Offer markup, and Organization markup. The return-policy markup page lists the latter four account and markup sources. A feed's `return_policy_label` assigns a configured non-default Merchant Center policy to a product; the label itself is not the return terms. Google recommends site-wide forms when one policy covers most products.
Five-minute self-check
- Open one product page and its linked returns page. Record the return window, eligible condition, method, fees, and any product-specific exception visible to a shopper.
- Paste the product URL into Google's Rich Results Test. Inspect its Offer for
hasMerchantReturnPolicy, then compare any window and fee in the markup with the public policy. A missing-field warning describes the markup, not whether a usable policy exists. - If you use Merchant Center, compare its return policy with the public page. For a product with special terms, also inspect any `return_policy_label` assigned in your product data.
- Choose the next step: make the customer-facing policy clear first; correct a mismatched Merchant Center policy or product label; then correct markup that conflicts with the terms you actually offer. If an account setting already supplies accurate terms, the markup warning alone need not drive a theme change.
Check another product with different terms before treating one result as store-wide. This is a content and markup check, not legal advice or a way to create a return policy through markup.
Fix 1: set returns in Search Console or Merchant Center
If Google recognises your site as an online merchant, Search Console offers returns settings alongside shipping; Merchant Center has the same. Set the default return window, fee and method there, then check any product-specific policy labels or exceptions. Account settings are read ahead of markup, so the missing-field warning may remain even when Google has a correctly configured policy for that product.
Fix 2: a site-wide return policy on your Organization
A return policy that applies to most or all of your products goes on your Organization markup as hasMerchantReturnPolicy. It lives once, on the page that carries your Organization markup, and it is the form Google recommends over per-product markup.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Store",
"url": "https://www.example.com/",
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": "US",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30,
"returnMethod": "https://schema.org/ReturnByMail",
"returnFees": "https://schema.org/FreeReturn"
}
}applicableCountry: the two-letter country codes the policy applies in; an array for several.returnPolicyCategory:MerchantReturnFiniteReturnWindowwithmerchantReturnDays,MerchantReturnUnlimitedWindow, orMerchantReturnNotPermitted.returnMethod:ReturnByMail,ReturnInStoreorReturnAtKiosk.returnFees:FreeReturn,ReturnShippingFeesorReturnFeesCustomerResponsibility.
Fix 3: hasMerchantReturnPolicy on each product's Offer
For products whose terms differ from the store's policy (final-sale items, say), or if you prefer each product page to carry its terms, put the same node on the product's Offer.
"offers": {
"@type": "Offer",
"price": 49.00,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": "US",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30,
"returnMethod": "https://schema.org/ReturnByMail",
"returnFees": "https://schema.org/FreeReturn"
}
}Say what your returns page says. A node that promises free returns in thirty days above a page that charges a restocking fee is a contradiction a shopper, and any system reading on their behalf, can see.
Where this goes on a Shopify store
The product markup most Shopify themes write includes no return terms. The theme file that writes it can be found by searching the theme code for "@type": "Product" (Online Store, Themes, Edit code); the node goes inside the offers object there. The Organization form goes in the theme's layout file, once, so it is on every page. A structured-data app can do either, and Fix 1 needs no code. Pick one method and keep it in step with your returns page.
The two warnings that usually come with it
Missing field priceValidUntil
priceValidUntil is the date after which the offer's price no longer holds. It is recommended, not required, and it exists for prices that genuinely end, such as a sale. If you add it, add a true date and make sure something updates it, because a date in the past tells Google the price has expired. For a standing price, leaving it out is honest and costs you nothing but the warning.
Missing field aggregateRating
aggregateRating is the star rating and count Google can show with a listing. It is recommended, and only add it when it is true: a real rating from real reviews that visitors can read on the page. Rating markup with no visible reviews behind it, or a number that differs from what the page shows, is the kind of mismatch that gets markup ignored, and it is one of the things a Findwise scan reports. A review app that writes the markup from the reviews it displays is the usual way to get this right; without reviews, leave the field out.
Checking the fix
- Run one product URL through Google's Rich Results Test and confirm the Offer shows the return policy node with no missing-field notice.
- In Search Console's Merchant listings report, select the warning and choose Validate fix; Google re-reads a sample of pages over the following days or weeks.
- If you chose Fix 1, the markup warning can stay in the report. Verify the policy assigned to a product in Merchant Center, including any non-default label, before deciding its terms are complete.
If the same product also has a shipping warning, the shipping-details guide shows how to compare the visible delivery terms with settings, product data and markup.
Why this matters beyond the warning
"Can I send it back, and what does that cost" is the question that decides a purchase a shopper is unsure about. A system answering that shopper reads the product's Offer; a returns page it has to find and summarise is a weaker answer than a field it can repeat exactly, and a policy node with no window and no fee is a label, not an answer.
A Findwise scan reads a sample of a store's public pages and checks this from the shopper's side: whether return and shipping terms are stated only in prose, whether a return policy node names its window and its fees, whether the policy nodes a store publishes are attached to each product's Offer, and whether rating markup is backed by visible reviews. Each finding cites the page it was seen on. Findwise estimates from public pages; it does not test AI assistants and cannot say what any assistant shows for your store.
Sources
- Google Search Central: Merchant listing (Product, Offer) structured data
- Google Search Central: Merchant return policy (MerchantReturnPolicy) structured data
- Google Search Central: Organization structured data
- Google Merchant Center Help: Return policy label [return_policy_label]
- Google Search Central blog: More ways to share your shipping and returns policies with Google (November 2025)
Check your own store
Create a free account to see what your public pages tell AI shopping systems about your products. Track weekly changes and work through your next priority fix.
