Google Merchant Center warranty information can now be submitted for ordinary retail products, rather than only the vehicle-ad use case previously documented for Japan. News coverage dated 16 October 2026 describes the change, while Google’s current help pages explain the product-feed requirements.
For online retailers, the question is practical: which products need the information, and how should it be formatted? This is a change to Shopping ads and free-listing data, not a new organic-search ranking factor.
Google Merchant Center warranty: what changed?
Search Engine Land reported on 16 October that Merchant Center’s warranty attribute now supports general products. Google’s documentation confirms the support and treats vehicle ads in Japan separately. The help page does not display a publication date, so 16 October is the date of the report, not a confirmed launch date.
The field describes warranty coverage in a product feed. That can help retailers keep catalogue data consistent with advertising disclosures and the information customers receive. It does not establish that Google will display warranty details for every product or reward merchants with more traffic.
Is the warranty attribute mandatory?
Not for every product. Google’s dedicated warranty page marks the attribute as optional, including where disclosure information may be needed in ads or free listings. Its broader product specification describes it as required for products subject to certain disclosure requirements. In practice, merchants need to assess the product and the markets where they advertise rather than apply a universal rule.
Google highlights Quebec’s Bill 29 as an example of local requirements. Its documentation calls for warranty periods affected by that example to be expressed in years. Retailers should verify their own obligations separately; Google’s feed instructions are not legal advice.
If no relevant warranty exists, do not invent a period just to populate an optional field. Likewise, distinguish included manufacturer or seller cover from a separate paid protection plan.
How to format product warranty data
For standard products, Google requires two sub-attributes when warranty information is submitted:
- duration: the length of coverage as an integer.
- duration_unit: the supported unit month or year.
For a CSV or TSV product feed, the documented column heading is warranty(duration:duration_unit). A hypothetical three-year warranty uses the value 3:year. Six months would be 6:month. Neither example establishes the terms of any real product.
Google also documents a nested XML representation and links to its Merchant API resources. Those formats have their own structure: do not copy a colon-separated spreadsheet value into an API field without consulting the API specification.
One detail may cause confusion. The help page labels the duration unit required for products but also describes a default of months if the unit is missing. Supplying the unit explicitly avoids ambiguity, especially where the relevant local rule specifies years.
The documentation also lists an optional mileage field for eligible vehicle ads. That field is not a standard product-feed requirement.
Why warranty data matters to online retailers
Warranty terms can influence a purchase, particularly for expensive or long-lived goods. Structured product warranty data provides another way to communicate those terms consistently. Search Engine Land identifies regional disclosure requirements as a reason for the change, which aligns with Google’s own example.
Neither source demonstrates that adding this information improves Shopping rankings, conversion rates or click-through rates. More complete data may help shoppers understand an offer, but its commercial effect needs to be measured rather than assumed.
Merchant Center feeds are also separate from ordinary editorial Search results. Nevelit’s guide to Google AI Overviews links covers a different kind of search visibility; it does not establish rules for Shopping product feeds.
How to prepare a warranty product feed
Verify coverage at product level
Start with the actual terms for each affected SKU. Record whether coverage is provided by the manufacturer or seller, and whether an extended plan costs extra. A blanket warranty period applied across unrelated products is likely to create misleading records.
Check country and listing requirements
Identify the markets where each item is advertised. Review applicable disclosure obligations before deciding whether the optional field should be populated. Keep vehicle-ad rules separate from standard products.
Map the fields in your feed tool
Check whether your ecommerce platform or feed plugin supports the warranty sub-attributes. That capability cannot be inferred from Merchant Center’s documentation. For text feeds, follow the compound header syntax; for XML and Merchant API submissions, use their respective formats.
Validate and maintain the data
Compare the submitted period with customer-facing terms, process the feed and inspect Merchant Center’s issue reporting. An uploaded file is not proof that all items were accepted. If warranty conditions change, update the source catalogue and feed together, retaining a record of affected products.
What this means for technical SEO
Google’s warranty documentation explicitly lists no Schema.org property for this feed field. Do not invent corresponding markup or promise an organic-search rich result. Product structured data has separate eligibility rules.
Accurate listings still matter. Google’s product-data specification warns that incorrect or conflicting information can cause disapprovals or display problems. The right outcome is a trustworthy feed that matches real coverage, not a higher SEO plugin score.
Limitations and trade-offs
Some merchants will have no immediate reason to adopt this attribute. Others may need market-specific disclosures, feed-development work and ongoing SKU-level checks. Google has not announced guaranteed advertising benefits from populating the field.
The main operational risk is treating a new field as a reason to fabricate missing data. Clear coverage terms and correct formatting should come before bulk feed updates.
Critical analysis
The expansion is a useful, narrowly scoped improvement. Retailers can provide a recognised warranty period, and Google acknowledges that some markets require it to be disclosed. The difficult part may be verifying the underlying coverage rather than implementing the format.
The distinction between optional feed enrichment and legally required disclosure deserves particular care. So does the boundary between Merchant Center data and SEO markup. Neither a compliant warranty field nor a richer feed guarantees search exposure.
For smaller shops, a focused audit of relevant SKUs and markets is a better starting point than adding assumed warranty periods to the entire catalogue.
Sources
- Google Merchant Center Help – Warranty [warranty], official attribute guidance, checked 19 October 2026.
- Google Merchant Center Help – Product data specification, requirements and context, checked 19 October 2026.
- Search Engine Land – Google Merchant Center adds warranty attribute for product listings, 16 October 2026.
Leave a Reply