You have updated your shop’s returns page, but Google still shows the old return window or suggests that returns are free when customers must pay postage. Before editing the page again, check which source is supplying that information.
Google can receive return details through Merchant Center, Search Console, product data and website structured data. The useful question is where the incorrect promise starts. A change to one source may leave another untouched.
Start with one affected product and its destination country. Trace the policy attached to it, correct the responsible source, then check that the correction survives the next product update.
1. Record exactly what Google is showing
Take a screenshot of the result, including the product and the returns wording. Record the search, date, device and customer country. Keep the destination product URL too. This gives your team a repeatable example instead of a general report that “Google is wrong”.
Separate a returns annotation beside a product listing from a normal search result quoting an old sentence on your website. This guide focuses on product and merchant return information. If the wording is simply an extract from an outdated page, investigate that page first.
Make a small comparison for the affected item:
- What does Google promise?
- What does the product page say?
- What does the main returns page say?
- Which policy does your team actually apply to this product and country?
Check each mismatch separately. A correct return window does not prove that the postage charge or return method is also correct.
2. Make the customer-facing policy consistent
Google’s Merchant Center return-policy guidance requires accessible, consistent information across your website and Merchant Center. Customers must be able to read the policy without signing in or providing personal information.
Open your returns page as a visitor. Compare it with product-page summaries, footer links and promotional banners. Check the window, eligible condition, return method and costs. Remove conflicting promises rather than adding another explanation elsewhere.
For a UK shop selling abroad, compare the policy for each relevant destination. Do not assume that the policy for domestic customers describes an overseas order.
Give the person making the digital changes an approved policy to work from. Their task is to represent the business’s terms accurately across the shop and Google, rather than deciding commercial terms while fixing a listing.
3. Check the saved policy in Merchant Center or Search Console
If you use Merchant Center, open Delivery and returns under Products and shop, then Return policies. Check the saved country, policy URL, return window and costs. Google also supports window extensions for holidays: inspect any extension’s date range and deadline.
Google’s Merchant Center guidance distinguishes Verified, Pending and Rejected policies. Saving a change and having an approved policy are separate checks.
If the policy was managed in Search Console
Look under Settings > Shopping > Shipping and returns. Google’s current Search Console instructions confirm that an online merchant does not need a Merchant Center account to configure these settings. You need owner or full-user access; an existing Merchant Center account must be associated with the property.
A policy created or edited in Merchant Center must be managed there and will not be available for editing in Search Console. An empty Search Console view therefore does not establish that Google has no saved policy.
Choose a clear owner for policy updates. Record whether that person works in Merchant Center, Search Console or the shop’s integration. This avoids two people correcting different copies and assuming the job is finished.
4. Inspect the affected product’s exceptions and overrides
If some products are wrong while others look correct, inspect product data before changing the shop-wide default.
Google’s return policy label documentation explains how return_policy_label assigns a non-default policy to a product or group. Where no label is supplied, the configured default applies through that mechanism.
Check whether the affected item carries an old exception label. Compare it with a similar item that shows the right terms. Ask whoever manages the feed to trace where that label is assigned and whether the next import will restore it.
Check the newer product-level returns attribute too
Labels are not the only route. Google’s current returns attribute specification says that returns can supply product-level details and override an account-level Merchant Center policy. It includes country, condition, window, return method and fees.
This means an accurate account default may coexist with an incorrect product override. Inspect both before deciding which needs repair. Google recommends using these overrides sparingly when an account policy can cover much of the catalogue.
After changing a mapping, check a normal product, an intentional exception and a product that previously carried the wrong terms. The aim is to repair the mismatch without accidentally removing genuine differences between products.
5. Review website markup after the account and product checks
Structured data is the machine-readable information your website supplies alongside the content customers see. It may be generated by your ecommerce platform, theme, SEO plugin or custom development.
Google’s merchant return policy documentation supports a business-wide MerchantReturnPolicy under Organization and a product-specific policy under Offer. Within website markup, the product-specific policy can override the general one.
The same guidance says that Merchant Center or Search Console settings take priority over website return-policy markup. Correcting the markup alone may therefore leave a conflicting saved setting in control. Product-feed overrides need their own check, as described above.
Ask your developer to identify which component produces each policy. Repair that component’s settings or output instead of adding another competing block of markup. Keep this work in the shop’s existing structured-data implementation.
6. If a correction reverts, trace the integration
Compare the saved policy immediately after your change and after the next scheduled synchronisation. If it changes back, investigate the source feeding that update. Repeated manual edits will leave the underlying cause in place.
For custom integrations, there is a current technical check: Google’s Content API sunset guidance records the 18 August 2026 sunset and intermittent failures from 1 September for requests without an active extension. Its current timetable distinguishes this from full decommissioning. Do not assume every legacy request has already stopped working.
Ask the developer to inspect actual policy-update responses and the migration to Merchant API. For an integration supplied by your ecommerce platform, raise the evidence with its provider, which manages that migration.
7. Verify the repair in three places
First, check the customer journey: the product page, returns page and any relevant checkout message should describe the same applicable terms.
Second, check the submitted information. Confirm the correct policy status, destination country, product label and any direct product override. Repeat this after a scheduled feed update.
Third, check the website implementation if markup changed. Google’s structured data guidelines recommend the Rich Results Test and URL Inspection for technical checks. They also require current, visible content and make clear that valid markup does not guarantee a rich result.
Keep approval, website crawling and public display as separate observations. Search Console’s guidance says return-policy verification can take about 10–13 days. That is not a promised deadline for every Google result to change.
Recheck the original product and country, then sample the unaffected products. Record what changed and what still differs. If the submitted information is correct but the public result remains wrong, use that evidence when requesting support.
Keep the policy accurate through the next promotion
Add Google’s policy settings and product mappings to the same change process as your website returns page. For a seasonal extension, assign someone to check the start, the end and the return to standard terms.
If prices or stock are also inconsistent, our guide to Merchant Center price and availability mismatches covers those separate checks.
Need help finding which setting or integration is supplying the wrong returns policy? Talk to BuzzBoost about checking your shop, product data and Google settings together.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
