AI Descriptions in Merchant Center: Feed Origin and Attribute Precedence
Choose the attribute by text origin, preserve trained_algorithmic_media, and prevent description from taking precedence over structured_description.
Sending both fields does not protect the AI description
When description and structured_description are submitted together, Google uses only description. This can defeat the purpose of a migration: adding the structured description alongside the conventional field does not give priority to the text with declared origin. For descriptions created with generative AI, the specification requires structured_description instead of description, with the text in content and digital_source_type set to trained_algorithmic_media. Source s1
The general AI-generated content guidance allows alternative attributes instead of, or alongside, conventional title and description attributes. The description-specific specification requires replacement and explains precedence. When implementing description exports, the general guidance does not make submitting both an equivalent alternative. Source s0 Source s1
Suggested action: Before expanding the export, inspect a sample of the final file. As a review practice, check that items with generative descriptions contain only structured_description as their description attribute, without a legacy description accompanying the submission. Do not stop at checking whether the new field appears in the configuration. Source s1
Four situations for choosing the mapping
Descriptions not created with generative AI can use description or structured_description. In the latter, default identifies non-generative origin and is also applied when digital_source_type has no value. That omission does not identify generative text: trained_algorithmic_media is required for it, and content must contain the description. Source s1
Suggested action: Use the following matrix as an editorial decision aid, not as an integration test result. Choose the path based on the origin of the description being exported; if both attributes are present, also review which text will actually be used. Source s1
Editorial decision aid
| Text origin | Submitted attributes | Export decision |
|---|---|---|
| Human, without generative AI | description only | Permitted path; export the non-generative description. |
| Human, without generative AI | structured_description only | Populate content; use explicit default or its behavior when omitted. |
| Generative AI | structured_description only | Populate content and declare trained_algorithmic_media. |
| Human or generative | description and structured_description | description takes precedence. To export the generative description, remove description and retain the structured field with its origin declaration. |
Keep origin attached to the text version
Suggested action: As an internal catalog practice, record origin alongside the description version, product, variant, and editorial approval. Keep that record attached through review and export so attribute selection does not depend on the publisher’s memory. This control is a process recommendation, not an additional field required by Google. Source s1
Suggested action: Do not automatically reclassify generative text as human-written just because it was reviewed. For partially generated, AI-translated, or heavily edited descriptions, refer the classification for confirmation before export; do not adopt an editing percentage as an exception without support in official documentation. Source s1
The product page is not the feed payload
Google requires consistency between description information, other submitted data, and the landing page. Its documentation maps description to the Schema.org property Product.description, but says structured_description is not currently supported by Schema.org. Website markup is therefore not presented as an equivalent to the structured feed attribute. Source s1
The feed description must focus on the product. The specification excludes company history and policies, comparisons with other products, links within the text, and promotional messages such as prices, shipping, and sale dates. Sale price and shipping, for example, belong in their dedicated attributes. Source s1
Suggested action: During editorial review, separate visible copy, Product.description markup, and the exported attribute. Preserve facts about the item and its variant, but do not automatically carry purchase prompts and promotional messages from the page into the feed. Treat information consistency as the review objective, not as a requirement for literally identical text or the same format across all three layers. Source s1
TSV and XML need different checks
In TSV, digital_source_type and content values are separated by a colon. If content contains a colon, that entire sub-attribute must be enclosed in double quotes; internal double quotes must be doubled. Google says incorrect formatting can make the value appear to contain too many sub-attributes and cause disapproval. Source s1
In the official XML example, digital_source_type and content are elements inside g:structured_description. The documentation calls for formatting that matches the data source type; the TSV representation should not be treated as a universal submission format. Source s1
Suggested action: To validate the exporter, include text with colons and double quotes in the sample and inspect its serialization. Check the final output as well as the configured mapping. If submission uses Merchant API, consult its specific documentation before defining the fields; do not turn the file structure into an assumption about the API. Source s1
Check the limit and the exact token
description and the content sub-attribute of structured_description accept 1 to 5,000 characters. Google says descriptions exceeding the limit are truncated with a warning. Its best practices recommend placing important details within the first 160 to 500 characters and including information that distinguishes variants, such as color, size, and material. Source s1
In the Brazilian Portuguese version of the official help page consulted on October 1, 2026, in UTC−3, one example contains train_algorithmic_media. The requirements on that same page and the English specification give trained_algorithmic_media. The Portuguese page also warns of possible AI translation errors. The origin value established in the requirements is trained_algorithmic_media. Source s1 Source s2
Checklist before releasing the export
Suggested action: Use this list as an editorial release aid for catalog and integration teams. Link the exported sample to the approved version and review identified issues in Merchant Center after submission. If you find a discrepancy, correct the mapping before expanding the export. Source s1
Suggested action: For paid-media teams, keep the scope of the check clear: this procedure reviews description attributes, not guaranteed overall approval or campaign results. Do not use precedence between description and structured_description as a priority rule among feeds, APIs, or crawled website data. Source s1
Suggested checks before export
- Confirm the approved version’s origin for each product and variant.
- Choose description or structured_description according to origin.
- For generative text, check content and trained_algorithmic_media.
- Remove competing description fields for items with generative descriptions.
- Check variant facts against the landing page.
- Remove links and promotional messages from the feed description.
- Verify character limits and serialization for the selected format.
- Retain a final sample and review diagnostics after submission.
Sources and scope
- AI-generated content - Google Merchant Center Help — consulted 2026-10-01 (UTC−03).
- Description [description] and structured description [structured_description] - Google Merchant Center Help — consulted 2026-10-01 (UTC−03).
- Descrição [description] e descrição estruturada [structured_description] - Ajuda do Google Merchant Center — consulted 2026-10-01 (UTC−03).
Your next step
Check the official description requirements.
Compare a sample of the final file with the requirements and format rules, checking the origin declaration and the absence of a competing description field.
This is editorial guidance, not a guarantee of platform approval or sales results.