Google Merchant Center Warranty Data: A Practical Feed Guide

If warranty terms currently live only on your product pages, support documents, or internal spreadsheets, you now have a more structured option. Google Merchant Center supports a warranty [warranty] attribute for general products appearing in Shopping ads and free listings.

The field itself is simple. The difficult work is deciding which products need it, expressing the duration without changing its meaning, and keeping the feed aligned with the warranty customers actually receive. This guide gives you a practical way to make those decisions without treating warranty data as either a universal requirement or an advertising shortcut.

Start with applicability, not feed formatting

The warranty attribute is generally optional, but that does not make warranty disclosure optional in every situation. Local regulations can require warranty information for particular products or advertisements. Your first task is therefore to classify products by market and legal obligation, not to populate the field across the entire catalog by default.

Google points to Quebec’s Bill 29 as an example of a regulation under which certain warranty details must appear in advertising. That does not mean every product sold in Quebec automatically receives the same feed treatment. Product type, warranty terms, advertising context, and the law’s scope still need review.

Do not use the availability of a Merchant Center field as a legal interpretation. Have the person responsible for Quebec compliance determine which offers are covered. Then translate that determination into a documented feed rule. If applicability is unclear and the omission could create legal exposure, pause the affected offer for review rather than guessing.

Encode the duration and unit as one complete value

For a standard product, warranty data has two supporting fields. Warranty duration [duration] contains a whole number. Duration unit [duration_unit] identifies whether that number represents months or years. Both supporting fields are required when you submit warranty information.

• Duration: Enter the whole-number length of the warranty.
• Duration unit: Use the supported month or year unit.
• Complete pair: Do not emit one supporting field without the other.
• Quebec rule: Use years when submitting a warranty period covered by Bill 29.

A three-year warranty is represented by pairing a duration of 3 with a duration unit of year, expressed in the documented example as 3:year. That value should come from the actual warranty terms. It should not be inferred from a product’s expected lifespan, the seller’s return window, or a marketing phrase about product quality.

Months and years are both supported for general products, so preserve the contractual period instead of rounding it into a more convenient unit. If your source data specifies a period in months, do not enlarge it by rounding to years. If the terms say something that cannot be represented faithfully as a whole-number duration in one of the supported units, route the product for review rather than inventing a number.

Do not copy mileage into the general-product duration field. Mileage-based warranty information belongs to the separate formatting available for eligible vehicle ads in Japan. The expansion to general products did not turn mileage into a supported general-product duration unit.

Build warranty data into the feed as a governed workflow

A manual feed edit may solve one product today, but it creates a maintenance problem as soon as a manufacturer changes its terms or the same item is sold in another market. Treat warranty coverage as governed catalog data with an owner, an authoritative record, and explicit transformation rules.

1. Name the source of truth. Decide whether the controlling warranty term comes from your product information system, manufacturer agreement, compliance database, or another maintained record. A promotional landing page should not silently become the legal source.
2. Classify offers by target market. Record where each offer is advertised and whether a local disclosure rule applies. Do not assume that one global warranty rule covers every country or province.
3. Map the actual coverage period. Connect each product or warranty class to its contractual duration. If variants, refurbished items, bundles, or seller-specific offers receive different coverage, keep those records separate.
4. Normalize without changing meaning. Transform the approved period into a whole number plus month or year. Apply the year requirement to warranty periods within the relevant scope of Quebec’s Bill 29.
5. Require a complete pair. Add a feed validation rule that rejects or quarantines records containing duration without duration_unit, or duration_unit without duration. For a legally required disclosure, omitting the incomplete pair from the feed is not a complete resolution; send the offer to its compliance owner.
6. Inspect representative outputs. Check products with different warranty periods, product conditions, and target markets. Compare the source record, exported feed value, and processed Merchant Center data.
7. Record changes. Keep the effective warranty term, applicable market, data owner, and last approved change together. That history makes it possible to explain why a value appeared in an advertisement if the terms are later questioned.

This approach also prevents a common automation error: filling every empty field with a default warranty. Missing information is not evidence that a standard warranty applies. A blank record should trigger classification or review, not fabricated coverage.

Keep the feed, product page, and warranty terms aligned

The structured value is only one representation of the promise you make to the buyer. The duration in Merchant Center should agree with the product page and the controlling warranty terms for that exact offer. A technically valid feed value can still be misleading if the customer receives different coverage.

Keep warranties separate from returns. A warranty describes covered protection over a stated term. A return policy governs whether and how a purchase can be sent back under the seller’s rules. A return window should not be placed in the warranty fields merely because it already exists as a clean duration in your catalog.

Your review should compare the same facts across every customer-facing and machine-readable location:

• The product or offer receiving the warranty.
• The market in which that offer is advertised.
• The whole-number duration.
• The month or year unit.
• The warranty language on the product page.
• The controlling manufacturer or seller terms.
• Any separate treatment for variants, bundles, conditions, or vehicle ads.

Repeat that review whenever a warranty program changes, a product is moved between catalog records, a new market is added, or a feed transformation is rewritten. Those are the moments when a previously correct value is most likely to drift.

Measure this work by accuracy, completeness, and market coverage. Google has not announced a guaranteed improvement in ad visibility or performance from submitting warranty data. The attribute gives you a standardized way to communicate coverage; it should not be presented internally as a promised ranking or conversion lever.

Warranty attribute FAQ

Is warranty data required for every Merchant Center product?

No. The warranty attribute is generally optional. It may be required when the advertised product is subject to a local warranty-disclosure rule, so applicability must be decided by product and market rather than with one catalog-wide assumption.

What must I submit for a standard product?

Submit both warranty duration [duration] and duration unit [duration_unit]. The duration is a whole number, and the supported units are months and years. A three-year warranty uses a duration of 3 and the year unit, shown as 3:year in the documented example.

Can I use lifetime or mileage as the duration unit?

The supported general-product units identified for this attribute are months and years. Do not convert a lifetime warranty into a guessed number. Mileage-based formatting remains available separately for eligible vehicle ads in Japan and should not be inserted into a general-product duration field.

Will adding a warranty improve Shopping ad performance?

No performance or visibility improvement has been guaranteed. Warranty data can help communicate product coverage and support applicable disclosure obligations, but it should not be implemented as a ranking tactic with an assumed return.

Start with a narrow audit: identify the markets where warranty disclosure may matter, map the affected offers to authoritative terms, and test complete duration-unit pairs before expanding the rule. Once that logic is stable, make warranty validation part of every catalog and market launch.

References

• Search Engine Land – Google Merchant Center adds warranty attribute for product listings