← Help Center

Add return policy signals Google can actually use

If Google cannot read a return policy from settings or markup, your offer trust signals stay weaker.

Symptom

The storefront does not expose return policy markup even though the account may already have return settings elsewhere.

Exact cause

Google flagged this state because your product pages do not include MerchantReturnPolicy structured data markup. Adding this markup helps Google understand your return terms directly from your pages, which can improve your listing's trust signals and click-through rate.

This page teaches precedence instead of just shouting “add schema.” Markup matters, but it is not always the first or strongest fix location.

Which system wins

For storewide return policies, Google’s precedence flows from Merchant API or Merchant Center/Search Console settings down to product-level markup and then organization-level markup. Markup helps, but account-level settings can outrank it.

Correct edit point

Use Merchant Center or Search Console if you want account-level control. Add theme markup when page-level detail and crawl-visible trust matter.

Manual fix steps

  1. Add a MerchantReturnPolicy JSON-LD block to your product pages.
  2. Include: returnPolicyCategory (e.g., MerchantReturnFiniteReturnWindow), merchantReturnDays, returnMethod, and returnFees.
  3. This can be added via a theme app extension or directly in your theme's product template.

StoreSteady assist

StoreSteady will generate a JSON-LD code snippet with your return policy details. Copy it into your Shopify theme's product template before the closing </head> tag.

Example patch

{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "name": "{{ shop.name }}",
  "hasMerchantReturnPolicy": {
    "@type": "MerchantReturnPolicy",
    "applicableCountry": "US",
    "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
    "merchantReturnDays": 30,
    "returnMethod": "https://schema.org/ReturnByMail",
    "returnFees": "https://schema.org/FreeReturn"
  }
}

Use markup only when markup is actually the correct edit point. Storewide return settings in Merchant Center or Search Console can outrank markup.

Validation steps

  1. View the rendered HTML and confirm the structured data values match the visible product page.
  2. Run Rich Results Test or Merchant listing validation on a live product URL.
  3. Check Merchant Center diagnostics again after Google has had time to recrawl the page.

Expected resolution time

Google re-crawls structured data within 24–72 hours.

Free Scanner

Scan your store for this exact issue

Check whether your storefront is showing the same public signal problem described in this article before you connect the app. Start with no markup return policy.

Source article: Add return policy signals Google can actually use

Related Issues

Improve Store Quality return experience
Unclear, weak, or inconsistent return policies can hurt store-quality signals.
Fix missing return policy in Merchant Center
If Merchant Center does not have a return policy configured, Shopping eligibility and return trust signals stay weaker.
Add product condition markup Google can understand
Missing or inconsistent product condition data weakens Google’s understanding of your offer.
Connect Search Console to Merchant Center for real diagnostics
Without the association, you miss Shopping tab notifications and growth opportunities.