Discussion
  • eCommerce SEO
  • Search Console
  • Structured Data

Shipping and returns can be set in Search Console, Merchant Center and markup. Which do you treat as the source of truth when they disagree?

Published 1 reply

Discussion starter: an ecommerce SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    The source of truth is your actual policy, the terms a customer gets when they buy. Search Console settings, Merchant Center settings and structured data are three ways of telling Google about that policy, and none of them should be allowed to become the master copy. When they disagree, the fix is not to work out which one Google will prefer; it is to generate or update all of them from one internal record so they cannot disagree. If you cannot keep three channels in sync, use fewer channels: a correct policy in one place beats a correct policy in two places and an outdated one in the third.

    What each channel is for

    Channel Suits Typical drift
    Merchant Center shipping and returns settings Merchants running product feeds and Shopping listings Set up at launch by the paid team and not revisited when policies change
    Search Console shipping and returns settings, added in November 2025 Sites without a Merchant Center account that want policies shown in organic results Configured once by the SEO team; nobody else knows they exist
    Structured data on the site Business-wide policies in Organization markup, with product-level markup for products whose terms differ, as Google’s merchant listing documentation recommends Hard-coded in templates by developers and missed when the policy page changes

    Google documents how some of these relate, for example product-level details for exceptions alongside a business-wide policy. Those rules are worth reading, but designing around precedence is fragile. It tells you which wrong value will be shown, not how to avoid showing a wrong value.

    Why disagreement matters

    • Shoppers see the wrong terms. A listing that promises free returns within 60 days when your policy is 30 creates disputes and support costs.
    • Merchant Center issues. Mismatches between what you declare and what the landing page shows can lead to warnings or disapprovals for affected products.
    • Consumer protection. Advertising a better returns or delivery policy than you honour can be misleading under consumer law in many markets, regardless of which channel displayed it.
    • AI answers. Assistants answering “does [store] offer free returns?” may use any of these sources or your policy page. Consistency is the only way to be sure the answer is right.

    Setting up a single source

    1. Keep the policy in one structured record inside your ecommerce platform or a configuration file: return window, return cost, refund method, conditions, shipping costs and times by region, thresholds for free delivery, exceptions by product type.
    2. Generate the policy page from it, or at least keep the policy page’s key facts in the same record.
    3. Generate Organization and product-level markup from it. Products with different terms, such as oversized items or final-sale goods, take their values from the same record’s exceptions.
    4. Update Merchant Center and Search Console settings from it, through the Content API or a documented manual process with a named owner.
    5. Choose which channels you use. If you run Merchant Center, the Search Console settings may be redundant for you; if you do not, Search Console settings plus markup cover organic results.

    Watch for this:

    Seasonal policy changes, such as extended holiday returns or temporary free shipping, are when channels drift most. Build the start and end of each promotion into the same process: every channel updated on the day the policy changes, and reverted on the day it ends. A holiday returns extension still showing in March is a common, avoidable mismatch.

    An audit to run quarterly and after every policy change

    • Write down the current policy from the terms and conditions, not from memory.
    • Compare it with the Merchant Center shipping and returns settings for each country you sell in.
    • Compare it with the Search Console settings, if configured.
    • Validate the Organization and product-level markup on a sample of pages, including products with exceptions.
    • Check how your listings display shipping and returns in search results and in Shopping for a few products.
    • Ask two or three assistants about your returns and delivery policy and note whether the answers are correct.

    Hypothetical example:

    An outdoor retailer shortens its return window from 60 to 30 days. The policy page and Merchant Center are updated, but the returns policy in Organization markup is hard-coded in the theme and still says 60 days, and the Search Console setting, configured by a former SEO contractor, also says 60. Organic listings show 60-day returns for months, and customer service starts receiving complaints. The team moves the policy into a single configuration used by the theme, removes the Search Console setting because Merchant Center already covers its listings, and adds the policy to the release checklist so the next change reaches every channel together.

    Who should own it

    Most drift happens because each channel has a different owner who does not know the others exist: the paid team owns Merchant Center, SEO owns Search Console, developers own the markup, and customer service owns the policy page. Give one person or team responsibility for the policy record and for confirming that every channel matches it after each change. In practice that is often the ecommerce operations team, with SEO and paid search as consumers of the record rather than editors of their own copies. Write the channels into the policy change checklist that legal or operations already uses, so a change to the terms automatically triggers the updates rather than relying on someone remembering.

    Differences by country and product

    Most mismatches in larger stores come from exceptions rather than the headline policy: different return windows by country, non-returnable categories, oversized delivery charges, marketplace items with the seller’s own terms. The single record needs to model those exceptions explicitly. If it only holds the headline policy, markup will overstate your terms for every exception, and you will not notice until a customer does.

    The policy in your terms and conditions is the truth, one internal record carries it, and every channel is generated from that record or updated by one named owner on the same day. Then the question of which channel wins stops mattering.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.