ItemlumeAssets & tasks / DECISION CHECK
Which Google feed fields should hold an AI-written product title or description?
If you use an AI-generated title or description in Google product data, follow the current structured_title and structured_description guidance. A human checking the facts is essential, but checking does not automatically turn generated text into human-authored text.
Separate authoring from factual review
Record which text came from a model and which product facts support it. For a fictional desk lamp, dimensions can come from a supplier sheet while the wording comes from an AI draft. Approve the dimensions, finish and included components before mapping the approved copy to the feed. Remove invented certifications and performance numbers even when the phrasing is fluent.
Google documents a digital_source_type sub-attribute and content for the structured fields. Consult the linked title and description specifications for the exact syntax supported by your feed method. A spreadsheet export, XML source and API connector may expose different mapping interfaces; do not paste a JSON object into an ordinary title cell without checking its schema.
Prepare a mapping handoff
| Editorial input | Feed mapping question | Evidence to retain |
|---|---|---|
| Generated title | Does the connector support structured_title? | Approved text and origin |
| Generated description | Does it support structured_description? | Approved text and fact references |
| Product identifier | Which stable item receives this copy? | SKU and market |
| Connector validation | Did the structured content parse correctly? | Processed product preview |
The worksheet is an editorial handoff, not an implemented Google integration. Keep the old source value so a malformed mapping can be corrected without rewriting the product record.
Validate one product first
Choose one representative SKU and market. Submit it through your normal authorized feed workflow, then inspect the processed title and description. Check that customers see the intended content rather than field names, serialized braces or an empty title. Also inspect variant distinctions: “large” and “small” should not become indistinguishable simply because a model shortened the copy.
Itemlume can help draft creative copy, but it does not infer your connector’s field compatibility or submit Merchant Center data. A planning draft still needs factual approval and correct downstream mapping.
Keep a dated origin record
Store the final wording, creation method, fact-sheet version, reviewer and connector mapping together. Recheck the current specification when switching feed providers. Do not describe a title as “Google approved” merely because the generator completed or a spreadsheet accepted the cell. Feed parsing, policy review and campaign performance are separate observations.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Do these fields verify product claims?
No. You still need evidence for the claims and variant facts.
Does human proofreading remove AI origin?
Do not assume that proofreading alone changes how generated content should be declared.
Will every connector support the fields?
Verify the actual source method and processed product; support varies.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open Assets & tasks Check pricing and credits