usdigitalmarketingindex.com SEO
How should merchant return policies be represented in structured data?
Updated November 15, 2026
State the store’s standard policy once, as a MerchantReturnPolicy nested under the Organization markup, and add a product-level policy only where a product’s terms differ. That is the arrangement Google’s documentation describes: “A standard return policy for your business that applies to most or all products you sell can be specified using the MerchantReturnPolicy structured data type nested under the Organization structured data type using the hasMerchantReturnPolicy property” (Google’s merchant return policy documentation). The markup must say what the published policy says. It records the policy. It does not replace it, and it creates no return rights that the store’s terms and the applicable consumer law do not already provide.
Policy scope and applicability
Start from the written policy, and establish its scope before writing any markup.
| Question | Why it matters for the markup |
|---|---|
| Which countries does the policy cover? | The applicableCountry property takes country codes, and policies can differ by country |
| Is there a return window, no returns, or no time limit? | These are the three values of returnPolicyCategory |
| How many days? | Required when the window is finite |
| Do all products share the policy? | If not, the exceptions need product-level markup |
| Does the policy change seasonally? | The documentation provides seasonal override properties for organization-level policies |
| Where is the policy published? | The markup should sit on, and can link to, that page |
On placement, the documentation says: “We recommend placing return information on a single page on your site that describes the return policy of your business. You don’t need to include it on every page of your site”.
Required policy properties
The documentation offers two ways to satisfy the requirement, as checked on November 11, 2026.
| Option | Required properties | Use when |
|---|---|---|
| A | applicableCountry and returnPolicyCategory | The policy's terms can be stated as structured values |
| B | merchantReturnLink | The store points to a web page that describes the policy |
For option A, returnPolicyCategory takes one of these values:
https://schema.org/MerchantReturnFiniteReturnWindow: a set number of days to return a product;https://schema.org/MerchantReturnNotPermitted: returns are not permitted;https://schema.org/MerchantReturnUnlimitedWindow: no time limit.
One dependency is stated twice in the documentation: if the category is the finite window, “the merchantReturnDays property is required”. It defines that property as the number of days from the delivery date.
Further properties are recommended and describe the terms in more detail, among them returnFees, returnMethod, returnShippingFeesAmount, refundType, and itemCondition. Add them where the policy states those terms, using the values listed in the documentation.
An example for a store with a 30-day policy in one country. The company and addresses are placeholders.
{
"@context": "https://schema.org",
"@type": "OnlineStore",
"name": "Example Outfitters",
"url": "https://www.example.com/",
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": "US",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30
}
}
OnlineStore is a subtype of Organization. A store that prefers to point to its policy page uses the second option:
{
"@context": "https://schema.org",
"@type": "OnlineStore",
"name": "Example Outfitters",
"url": "https://www.example.com/",
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"merchantReturnLink": "https://www.example.com/returns/"
}
}
Product and organization levels
The two levels have different jobs.
| Level | Where the markup sits | What it states |
|---|---|---|
| Organization | Under the Organization type, on a single page | The standard policy for most or all products |
| Product | Under the Offer of a specific product | A policy that differs from the standard for that product |
The documentation’s wording for the second: “If you need to override your standard return policy for a specific product, specify one or more instances of MerchantReturnPolicy under the Offer type”. It also warns that offer-level policies “support a more limited set of properties”, and refers to the merchant listing documentation for which ones.
A hypothetical store:
| Product group | Published terms | Markup |
|---|---|---|
| Clothing | Standard 30 days | Organization-level policy; nothing on the products |
| Clearance items | Final sale, no returns | Offer-level policy on each clearance product, category MerchantReturnNotPermitted |
| Mattresses | 100-night trial | Offer-level policy on those products, finite window, 100 days |
Do not repeat the standard policy on every product. The override exists for differences.
Consistency checks
The published policy is the reference. Everything else is compared with it.
| Compare | With | Must agree on |
|---|---|---|
| Organization-level markup | The returns page | Window, countries, category |
| Offer-level markup | The product page's stated terms | The exception and its length |
| Markup | Checkout and order confirmation wording | The same terms the customer is shown when buying |
| Markup | Any return settings supplied to Google through Merchant Center | The same policy |
| Markup | The policy for each country served | The right policy for each country code |
Checks to run:
- Test the page carrying the Organization markup in the Rich Results Test and confirm the return policy is read without errors.
- Test a product with an override and a product without one.
- Read merchantReturnDays against the written policy. Confirm both count from the same event; the property is defined from the delivery date.
- Confirm the merchantReturnLink address loads the policy page.
- Recheck whenever the policy changes, including seasonal extensions and their end dates.
- Review the merchant listings report in Search Console for issues.
Mistakes these checks catch:
- a window in markup longer than the one in the policy;
- a policy marked for a country where the store applies different terms;
- final-sale products inheriting the standard policy;
- a holiday extension left in markup after it ended;
- markup updated while the returns page was not, or the reverse.
On what the markup achieves, the documentation says Google Search “can use this information to display return policies alongside your products and in knowledge panels”. Can is the operative word. Accurate markup makes the information available to Google and does not oblige Google to show it.
Return terms are one product attribute that can vary within a catalog. Price is another, and how to mark it up when it changes by size or color is covered in the guide to how Product structured data should represent a price that changes with selected variants.
The rule: one standard policy at organization level, overrides only on the products that differ, and every value taken from the policy customers can read.
Add your comment to this answer