Implementation
Fill Google Merchant Center Attributes AI Mode Can Actually Use
Fill conversational Merchant Center fields with highlights, details, variants, and Q&A without duplicating your product description.

Google's conversational attributes do not replace a clean product feed. They add the facts a shopper asks after the title has done its job: Does this have a headphone jack? Which width is this shoe? Where is the assembly PDF?
This is the worksheet for that overlay. The Google AI Mode shopping audit is the five-stage operating system. Do not start here if Merchant Center and your storefront still disagree on price, stock, or URL. A beautiful Q&A file on a disapproved SKU is a spreadsheet, not a listing.
Google's conversational attributes help page is the source for every field below. The attributes are optional. Google says they will not change the approval status of products you already submit. Google recommends a supplemental data source, or the Merchant API, instead of overloading a fragile primary file. That recommendation is operational, not fussy. A primary feed that already struggles with variants will break worse when you add repeated group attributes.
If a fact already lives in description, product_highlight, or product_detail, do not paste it again into question_and_answer. Google tells you not to duplicate. Duplication feels complete in a sheet. It teaches the model nothing it could not already read.
Start from the core specification
The product data specification still decides whether the item can appear at all. Conversational fields sit on top. If you skip this section and jump to Q&A, you will write answers for a product Google cannot show.
Minimum before you add AI Mode attributes:
- Stable
id - Accurate
title,description,link,image_link availabilityandpricethat match the live offerbrandplusgtinormpnwhere requireditem_group_idwhen the shopper can buy more than one variant
Shopify stores that use Google & YouTube already sync a primary feed. Put conversational fields in a supplemental source keyed on the same id. WooCommerce and other platforms submit the same attributes through a Merchant Center file or the Merchant API. The field names do not change. The transport does. Open Merchant Center after upload either way. The plugin UI is not the record Google stored.
When those core fields match the live offer, you can fill the overlay. Fill it in a fixed order so you do not write Q&A for a fact that belongs in a spec pair.
The attribute set, in the order you should fill it
Each attribute answers a leftover question. That is the only reason to add it. If the leftover question is already answered in the description, skip the field.
| Attribute | Job | Fill it when |
|---|---|---|
product_highlight | Short, product-only selling facts | The description buries the two or three facts a shopper compares |
product_detail | Named specification pairs | You have structured specs (material, capacity, ports) |
item_group_title | Family name for a variant set | Colours or sizes should stay one product in conversation |
variant_option | Human-readable variant axes | Internal codes currently hide size, width, memory, or colour |
question_and_answer | Buying questions the other fields do not answer | You have real FAQs, not keyword lists |
document_link | PDF the shopper or model can read | Manuals, size charts, or assembly files exist and are public |
related_product | Required parts and accessories | The product is incomplete without another SKU |
popularity_rank | Your own relative performance | You can compute it from inventory, not guess |
Google's own example on the conversational-attributes page is a Pixel phone variant: one id, one item_group_id, a family title, variant options for display / memory / colour, Q&A about the headphone jack and Bluetooth, highlights, details, related accessories, a manual PDF, and a popularity rank of 95.5. Copy the structure. Do not copy the phone. The structure is what matters: family, readable variants, leftover questions, real documents, real accessories.
A store that sells bags, apparel, or furniture can use the same structure. The next section is that structure filled for one backpack so you can see what actually moved.
Write a before-and-after row for one real product
Use a product you actually sell. Apparel, bags, furniture, and device accessories show the gaps fastest. Do not start with the hero SKU you already babysit. Start with the family that creates “which colour / does it fit / is X included” tickets.
Before (what many feeds still send)
| Field | Value |
|---|---|
id | SKU-4419 |
title | The Weekender |
description | Premium quality for modern travel. |
color | NV1 |
availability | in_stock |
item_group_id | *(empty)* |
A shopper who asks for a 26-litre clamshell backpack that fits a 16-inch laptop will not find this record unless luck intervenes. The feed never said those facts. Title is a nickname. Colour is an internal code. There is no family. There is no spec. Q&A cannot rescue this row because there is nothing true to hang a question on. Repair identity first, then add overlay fields.
After (same SKU, conversational-ready)
| Field | Value |
|---|---|
id | SKU-4419-BLK |
item_group_id | weekender-26 |
title | Carry-on travel backpack 26L, clamshell, 16-inch laptop sleeve, black |
item_group_title | Carry-on travel backpack 26L |
variant_option | color:black |
description | Opening sentence that names the category and use, then measurements, material, laptop size, carry-on claim, and what is not included. |
product_highlight | 26-litre clamshell main compartment / Dedicated padded laptop sleeve / Listed carry-on exterior dimensions on the size chart |
product_detail | Capacity:Volume:26 L / Material:Shell:recycled nylon / Compatibility:Laptop:16 in |
question_and_answer | Does it have a separate shoe compartment? → No. Shoes go in the main compartment or a packing cube. / Will a 16-inch MacBook Pro fit? → Yes, in the padded laptop sleeve. Measure your machine if you use a thick case. |
document_link | Public size-and-airline PDF if you publish one |
related_product | Packing-cube accessory by id or gtin if you sell it |
availability | Variant-level truth |
price | Current offer, not last month's campaign |
Notice what moved, and in what order. Identity and family first, so colours stay one product. Readable variant next, so “black” matches. Description and details next, so volume and laptop size are structured. Q&A last, for the questions the spec does not phrase as a question: shoe compartment, thick laptop case. Highlights stay product-only. They do not name another brand's machine as a comparison.
If you cannot produce this after-row for one live SKU, do not build a 50-SKU file. You do not yet have a repeatable pattern.
Apparel example
A wool sweater feed that only says Navy Knit will lose “machine washable merino crewneck, women's medium, not itchy.” Put fiber, care, and fit in product_detail. Put “Is it machine washable?” and “Does it pill in the first month?” in Q&A only if those answers are true and not already in the details. Size belongs on variant_option, not in a paragraph the model has to guess from. If medium and large are separate products with no item_group_id, the conversation cannot say “it also comes in large.”
Furniture example
A dining table that ships in two cartons needs related_product for the required hardware kit if that kit is a separate SKU. The Q&A should answer assembly time and whether chairs are included. Dimensions go in product_detail. A lifestyle title that omits seat count wastes the conversation. document_link belongs here when you already host an assembly PDF. Do not upload a lookbook and call it a manual. Google says it will extract from the document. A lookbook will extract marketing, not torque specs.
Those examples only work if the file survives upload. Most “the attributes disappeared” tickets are transport errors, not copy errors.
Common submission errors
Read this table after you write the after-row, not before. It is the list of ways a good row dies in transit or gets ignored.
| Error | What Google told you | What to do |
|---|---|---|
| Same sentence in description and Q&A | Do not duplicate | Keep the spec in details. Use Q&A for a decision the spec does not phrase as a question |
| “Best-selling luxury essential” as a highlight | No promotional text | Replace with a measurable fact |
| Q&A that includes “ships free until Friday” | No time-related offer data in Q&A | Move to shipping and sale attributes |
| Keyword list as questions | Avoid listing search terms | Write the question a customer asked in chat |
| Popularity rank of 99 because it “feels true” | Rank is relative to your inventory | Calculate or omit |
| PDF behind a login | Document link must be usable | Host a public file or skip the attribute |
| Related product pointing at a discontinued SKU | Identifier must resolve | Remove the relationship |
Re-open the Merchant Center product after the supplemental upload. If the attribute is not on the item, the transport failed. Fix the join on id before you write more copy. A Shopify Google & YouTube id is not always the SKU you type in admin. Export the id the channel actually sent.
Q&A is a repeated group attribute. Colons, commas, and quotes inside a question or answer will split the row if you treat a CSV like a document. Google recommends TSV or separate question_and_answer columns, and tells you to escape special characters. If Merchant Center shows one mangled FAQ instead of five, the file broke before Google ever judged the copy. That is a format bug, not an AI Mode ranking problem.
Once the attributes appear on the item, stay inside the official limits. The limits are how Google keeps the overlay usable. They are not optional style notes.
Respect the official limits
From Google's specification:
product_highlight: optional. Google's product highlight spec allows 1–150 characters per highlight, requires at least 2 and at most 100, and recommends 4–6. Product only. No promotional shouting, no keyword lists, no comparisons, no compatible-product essays, no repeat of details you already submitted elsewhere.product_detail: name/value pairs with their own character limits. Use real spec names, not marketing adjectives.question_and_answer: group attribute. Max 30 pairs. Max 10,000 characters total. Each question and each answer max 1,000 characters. Both sub-attributes required.- Do not put price, sale dates, shipping promises, or your company name inside Q&A. Those belong on offer attributes.
- Do not submit Q&A if
document_linkalready contains the same FAQ. Google says it will extract from the document instead. document_link: public PDF URLs, comma-separated if more than one.related_product: relationship type, identifier type, and identifier. Google's examples includerequired_part:id:AZ7B,accessory:gtin:811571013579, andoften_bought_with:id:AZ7C.popularity_rank: a percentage of your own inventory performance. Higher means stronger relative to *your* other products. Do not invent a marketplace rank.
Grammar and spelling matter. Google says customers rely on the answers. A wrong “yes, it is waterproof” is worse than an empty field. Empty is a gap. Wrong is a return.
The limits do not change by platform. Shopify and Woo only change how the file gets there.
Shopify path vs WooCommerce path
Shopify. Install and connect Google & YouTube. Let the channel own the primary sync. Export the product id values it uses. Build a supplemental sheet or Merchant API upload for highlights, details, Q&A, documents, and related products. Re-upload when the catalog changes, not once a year. A winter size run with last August's Q&A is how you get a confident wrong fit answer.
Metafields can hold the source facts. They do not reach Merchant Center unless you map them. If material and laptop size live in metafields, decide which field is canonical and write that into the supplemental source. Two metafields and a theme block for the same litre count is how Stage 2 of the audit fails.
WooCommerce and other platforms. Use the same attribute names. Your plugin or feed app is only a transport. Open the Merchant Center product, not the plugin UI, to verify what Google stored. Custom order meta that never leaves WordPress cannot help AI Mode. If the plugin says “synced” and Merchant Center does not show question_and_answer, believe Merchant Center.
When the path is chosen, run a 50-SKU test. The test is how you prove the pattern, not how you boil the catalog.
A practical fill order for a 50-SKU test
- Export 50 SKUs that already approve in Merchant Center. If they are not approved, you are still in the audit, not this worksheet.
- Repair titles, identifiers, and variant groups. Stop if more than a handful still mismatch the site. Overlay work on a lying core feed teaches the model the lie.
- Write four to six highlights per SKU (Google's recommended range). Read them aloud. If they sound like ads or name another product, cut them.
- Add details only for measurable specs.
- Write three to eight Q&A pairs from real tickets or PDP questions: fit, compatibility, inclusions, care, what the product is *not*.
- Attach PDFs that already exist. Do not upload a marketing brochure and call it a manual.
- Add related products only when a shopper would be stuck without the second item.
- Skip
popularity_rankuntil you can calculate it from your own units or revenue share. - Submit the supplemental source. Wait for Merchant Center to show the new attributes on a sample of products.
- Re-run the six-prompt matrix from the Google AI Mode audit. Change one class of field per cycle so you can tell what moved.
What these fields cannot do
They cannot override a disapproved item. They cannot invent stock. They cannot make a prohibited product eligible. They cannot guarantee that AI Mode will quote your Q&A or show your SKU.
They can remove a class of failure you can prove: the conversation asked a constraint, and your feed never contained the answer.
If you need the wider catalog and measurement loop, return to the audit. If you need the Shopify-wide channel map, use the Agentic Storefronts hub. This page has one destination: a Merchant Center row that can survive a follow-up question.