Return policy schema is an important check in the E-Commerce SEO (WooCommerce) category. This is a medium-priority issue — not urgent, but fixing it will improve your overall SEO health and, more to the point, the way your products present in Google Shopping and free listings. Return terms are one of the trust signals Google now surfaces directly in product results.
What This Check Is Really About
Schema.org added MerchantReturnPolicy so a product’s return terms can be expressed as structured data, and Google reads it. This check verifies that your Product markup carries a hasMerchantReturnPolicy property describing how returns work: the return window, who pays for return shipping, and the applicable country. When it is present and valid, Google can show return information alongside price and availability in Shopping and free product listings.
The key fields inside MerchantReturnPolicy are returnPolicyCategory (for example MerchantReturnFiniteReturnWindow), merchantReturnDays (the number of days), returnMethod, returnFees, and applicableCountry. You either express these on the product, or you set them once in Google Merchant Center — but the on-site structured data is what keeps organic product listings consistent with your Shopping feed.
Why It Matters for SEO
- Return terms appear in Google Shopping and free product listings as a visible trust signal
- A generous, clearly-stated return policy lifts click-through and reduces purchase hesitation
- Consistent structured data keeps organic listings aligned with your Merchant Center feed and avoids mismatch warnings
- It is a low-cost differentiator most competitors have not bothered to mark up
How to Check It
- Run a product URL through Google’s Rich Results Test and look at the
Productitem for ahasMerchantReturnPolicynode — its absence is the failure. - Check Google Search Console under the Shopping/Merchant listings reports for “Missing return policy” style warnings.
- If you run Google Merchant Center, confirm whether return policy is set there, at account level, or expected per-product.
- Run the SEO Roadmap audit to see every product flagged, not just a sample.
How to Fix This in WordPress
Difficulty Level: MEDIUM – This fix requires some technical knowledge or familiarity with WordPress settings and plugins.
Estimated Time: 20 min
Step 1: Decide where the policy lives
For most stores the return policy is a single site-wide rule, not a per-product one. That means you want to state it once and have it apply everywhere, rather than editing hundreds of products. Confirm your actual terms first — window in days, who pays return shipping, which countries — because the markup must match your real published policy or it is worse than useless.
Step 2: Emit the structured data
WooCommerce does not output MerchantReturnPolicy on its own. Rank Math and Yoast SEO (with WooCommerce SEO) can extend the Product schema, and several product-schema plugins add return-policy fields specifically. Configure the return window, fees, and country once at the global level so every product inherits it. If you maintain custom JSON-LD, add the hasMerchantReturnPolicy node to your product template rather than to individual products.
Step 3: Align Merchant Center
If you sell through Google Shopping, set the matching return policy in Google Merchant Center too. The two should agree. A site that marks up a 30-day window while Merchant Center says 14 will earn a mismatch warning and undermine both.
Verify the fix
- Clear your caching and any schema plugin cache.
- Re-run the Rich Results Test on a couple of products and confirm the return policy node validates.
- Re-run the SEO Roadmap audit, then check Merchant Center and Search Console over the following days.
Recommended Tools & Plugins
These tools can help you fix and prevent this issue:
- Yoast SEO – Comprehensive SEO plugin with built-in checks
- Rank Math – Feature-rich SEO plugin with detailed analysis
- Google Search Console – Free tool to monitor your site’s search presence
- SEO Roadmap – Complete SEO audit and action plan tool
Common Mistakes to Avoid
- Marking up a return policy that does not match the one on your actual returns page
- Setting return terms in the schema but a different window in Google Merchant Center
- Editing products one by one instead of applying a single global policy
- Copying a competitor’s return window into your markup without checking your own terms
- Adding the schema and never validating a single product afterwards
Need More Help?
If the return policy still will not validate, check whether two plugins are both writing Product schema and colliding, which is the usual cause on WooCommerce stores that have accumulated SEO plugins over the years. Consolidate to one source of product structured data, then run a full SEO Roadmap audit to confirm the fix held across the catalogue.
This guide is part of the SEO Roadmap knowledge base – your complete resource for WordPress SEO optimization.
Last modified: August 2, 2026
United States / English
Slovensko / Slovenčina
Canada / Français
Türkiye / Türkçe