Platform support

Choose title or structured title for Google product data

Google’s product data specification says the basic product data is the foundation for ads and free listings. In that section, a product name is either title or structured_title. Use title when a person wrote it. Use structured_title when generative AI wrote it. The id attribute is the product’s unique identifier, not the name. This is a Merchant Center data source. It is not a marketplace seller-center listing CSV, and Golanto does not submit it.

Documentation checked 2 November 2026 · English

When does the specification want title, and when structured_title?

The basic product data section labels Title [title] or Structured title [structured_title] Required. It says to use one of those attributes. For titles created using generative AI, use structured_title. Otherwise use title. A title is plain text, max 150 characters. It should match the landing page, describe the product accurately, and can include distinguishing features such as color or size. Do not include promotional text like "free shipping", all capital letters, or gimmicky foreign characters. The specification’s own title example is Mens Pique Polo Shirt.

structured_title has two sub-attributes. digital_source_type is optional. Its values are default, for a title that was not created using generative AI, and trained_algorithmic_media, for a title that was. If no value is specified, default is used. content is required and holds the title text, max 150 characters. The specification’s structured title example is a shoe sentence prefixed with trained_algorithmic_media. This page does not reuse that sentence. The same section gives description the same split: description or structured_description, with the same two digital_source_type values, and content max 5000 characters. Use structured_description when generative AI wrote the description. Otherwise use description.

Person-written name
title: Stoneware mug

Generative AI name
structured_title digital_source_type: trained_algorithmic_media
structured_title content: Stoneware mug

Which attributes in the sections this page read are labeled Required?

The specification defines Required as: submit this attribute, or the product will not be able to serve in ads and free listings. In basic product data, the attributes labeled Required are id, title or structured_title, description or structured_description, link, and image_link. id is max 50 characters. Use a unique value for each product, use the SKU where possible, keep the id the same when updating the data, use valid unicode, and use the same id for the same product across countries or languages. The specification’s id example is A2B4. link uses your verified domain, starts with http or https, and is an encoded URL that complies with RFC 2396 or RFC 1738. Do not link to an interstitial page unless legally required. image_link is the main image URL. Accepted formats named there are JPEG, WebP, PNG, non-animated GIF, BMP, and TIFF. The page says new image size requirements of at least 500 x 500 pixels will be enforced beginning 31 January 2027.

additional_image_link, virtual_model_link, and mobile_link are labeled Optional in that section. virtual_model_link says it is available only in the US. The warranty block is not one Required label for every product. It has a Required sentence for products that need warranty information shown, with Bill 29 in Quebec, Canada as the example, and an Optional line in the same block. The retrieved vehicle sentence was incomplete, so this page does not rebuild it. The block does say to use warranty for a product or vehicle, and that for Vehicle ads it is only available in Japan. duration and duration_unit are labeled Required for Products and Optional for Vehicles. Supported duration units that rendered are month and year, and the block says duration_unit defaults to month. This page does not add warranty to every row.

In the price and availability section, availability and price are labeled Required. availability’s supported values are in_stock, out_of_stock, preorder, and backorder. The example is in_stock. availability_date is labeled required if availability is preorder. A later bullet also says to provide availability_date when you submit preorder or backorder. price’s example is 15.00 USD, and the syntax lines say numeric and ISO 4217. Match the landing page and checkout. Do not submit a price of 0, except for mobile devices sold with a contract and physical goods sold with a subscription. For the US and Canada, do not include tax in price. For all other countries, include VAT or GST. The same section names sale price, unit pricing measure, unit pricing base measure, subscription cost, installment, and loyalty program as further price attributes. This page does not reprint their rules. Category, identifier, shipping, and the rest of the specification are also not reprinted here. The field list on this page is partial.

How do you map a supplier file onto that data source?

Keep an untouched copy of the supplier file. In Merchant Center, use the product data source for the country and language you are submitting. The specification says free-form text such as title and description should use one language in a data source.
In Golanto, choose Google Merchant Center. Record the target country and the date you read the specification. The mapper still opens on Amazon until you change the platform.
Map a person-written product name to title. If generative AI wrote the name, map it to structured_title and set digital_source_type to trained_algorithmic_media. Do not fill both title and structured_title for the same name. The specification says to use one of them.
Map the stable SKU to id. Leave id unchanged when you later edit the name. A title that is longer than 50 characters cannot be copied into id. That case is the separate id-and-title guide.
Leave price, availability, link, and image_link for values you can see on the landing page. Do not invent a warranty column. Golanto compares headers. It does not submit the data source.

Worked example

A supplier name column is not a Google title attribute

Inspect this record

sku,product_name
MUG-350,Stoneware mug

sku and product_name are a synthetic supplier sketch. The specification’s name attributes are title, or structured_title when generative AI wrote the name. Its id example is A2B4 and its title example is Mens Pique Polo Shirt. This mug is not those examples. Map MUG-350 to id and the person-written name to title. Do not submit this sketch to Merchant Center. It leaves out description, link, image_link, availability, and price, which the sections above label Required.

What this check cannot establish

Golanto does not submit a product data source to Google Merchant Center, and it does not decide whether a title was written by a person or by generative AI. This page uses the Product data specification retrieved on 2 November 2026. It quotes the Required labels it read in basic product data and in price and availability, plus the Optional labels beside them. The rest of the specification, including category and identifier tables, is not reprinted, so the field list is partial. The warranty vehicle sentence did not render cleanly. Image enforcement of at least 500 x 500 pixels is the page’s 31 January 2027 date. A mapped file is not an approved product.

Check your file

Start with a copy. Review changes before downloading your import file.

Open the template mapper

Official references

Google Merchant Center: Product data specification (opens in a new tab)

Schema review: google-merchant-product-data-2026-11-02. Examples are synthetic. Store-specific and unpublished requirements are outside these checks.

Common questions

Do I submit both title and structured_title?

The product data specification says to use one of them. Use title when a person wrote the name. Use structured_title when generative AI wrote it, with content for the text and digital_source_type set to trained_algorithmic_media. If digital_source_type is omitted, the specification says default is used.

Is warranty required on every Google product row?

The retrieved specification does not say that. The warranty block has a Required sentence for products that need warranty information shown, with Bill 29 in Quebec, Canada as the example, and an Optional line in the same block. duration and duration_unit are labeled Required for Products and Optional for Vehicles. This page does not add warranty to a row that the specification does not put it on.