Google documents warranty information for Merchant Center product feeds

What changed

Google Merchant Center documentation describes a warranty attribute that merchants can use to provide warranty information for a product. The page explains how to submit the data but does not establish a launch date.

For product data, the warranty attribute is optional. When a merchant supplies warranty information for products, the documentation says the duration and duration-unit sub-attributes are required. Duration is an integer, while the unit identifies whether that duration is expressed in months or years. Supported unit values are month and year, and the documentation says month is the default if the unit is not specified.

The core operational point is data accuracy. A merchant should map the stated warranty coverage into a duration and the correct corresponding unit. A warranty lasting three years should be represented as a value of three with a year unit; a six-month warranty should use six with a month unit. Teams should avoid converting values loosely or using a duration that does not reflect the actual commercial warranty offered for that SKU.

The documentation gives source-format guidance as well. In text data sources such as TSV or CSV, the warranty attribute is supplied with duration and duration-unit sub-attributes in the attribute name, with values presented in the documented order and separated by a colon. Google also provides an XML structure for the same data and directs Merchant API users to the relevant API resource. Feed owners should apply the syntax that matches their own data source rather than copying an example from a different feed format.

Vehicle advertising has separate considerations in the documentation. For vehicles, duration and duration unit are optional, and mileage is an additional optional field for warranty coverage in kilometers. That mileage field is described as applicable to Vehicle ads, not general product feeds. Retailers should therefore keep vehicle-specific attributes and ordinary product warranty data distinct in their feed design and governance.

This documentation can be useful where a merchant needs to display warranty information accurately in ads or free listings. It is not legal advice, and the documentation reviewed does not establish which merchants must provide the field in any jurisdiction. Compliance teams should determine their own obligations separately from the feed implementation.

The Google source page is undated on the page. Secondary coverage is dated 16 October 2026, but that date should not be presented as a confirmed documentation publication or revision date.

Why it matters for advertisers

Warranty data can improve the completeness and accuracy of product information, but implementation depends on clean SKU-level source data. The documentation also makes clear that vehicle-specific warranty fields should not be applied to ordinary retail products.