If you are deciding whether to add Merchant Center conversational attributes or repair your core product feed first, stabilize core product data before enrichment. Conversational attributes are optional fields that help AI systems understand product nuances on surfaces such as AI Mode; Google says they complement—not replace—your primary product data specification, and including them will not change the approval status of existing products. This article gives you a Feed Readiness Ladder, a Conversational Attribute Priority Scorecard, and a practical sequence for ecommerce brands deciding where to spend the next sprint.
Key takeaways
-
Core feed accuracy, completeness, and freshness typically determine whether products can appear reliably in Shopping ads, free listings, and AI shopping experiences.
-
Conversational attributes—question and answer, document link, related product, item group title, variant option, and popularity rank—are optional enrichment layered on top of that foundation.
-
Do not duplicate facts already present in description, product highlight, or product detail into conversational attributes.
-
When available, AI performance insights can show which terms, attributes, and shopping stages matter before you rebuild every FAQ field.
-
Treat conversational attributes as a later rung: useful after disapprovals, price/availability mismatches, and missing required attributes are under control.
What conversational attributes are—and what they are not
Google Merchant Center documents conversational attributes as optional fields that help AI systems and conversational agents understand product-specific nuances. They are designed to complement the primary product data specification and can support discovery across AI-driven surfaces such as AI Mode in Search, while also supporting traditional search experiences.
The currently documented conversational attributes are:
-
question_and_answer — product FAQs buyers actually ask
-
document_link — accessible PDFs such as manuals or assembly guides
-
related_product — accessories, substitutes, or required parts by identifier
-
item_group_title and variant_option — clearer variant grouping alongside item_group_id
-
popularity_rank — relative popularity as a percentage of your inventory
Google recommends submitting these through a supplemental data source when possible, though you can also add them to a primary source or send them through the Merchant API. That separation matters operationally: enrichment should not destabilize the feed that controls price, availability, identifiers, and policy compliance.
What they are not: a substitute for accurate titles, GTINs, images, shipping, returns, or landing-page consistency. Google’s product data specification states that accurate product data is foundational for ads, free listings, and AI-powered formats. Incorrect or missing information can cause disapprovals, limited eligibility, or incorrect displays. Conversational attributes will not rescue a feed that fails those basics.
Why this decision matters now
Shoppers increasingly ask longer product questions in AI surfaces. Google’s September 16, 2026 retail update framed readiness around accurate feeds, conversational attributes, and AI performance insights. In that post, Google stated that merchants adopting core Merchant Center feed best practices see, on average, a 5% increase in conversions the following month, and that in testing with lululemon, submitted conversational attributes were incorporated 50% of the time in relevant AI Mode product recommendations. Treat those as directional platform figures—not a guarantee—and keep the sequencing: core feed hygiene first, conversational enrichment second.
AI performance insights are now documented for English-language queries for Merchant Center accounts in Australia, Canada, India, New Zealand, and the United States. The report focuses on organic AI traffic such as free listings—not paid ads—and covers share of voice, shopping stages (discovery, evaluation, ready to buy), top terms, popular attributes, and search intents. That report is a better prioritization input than guessing which FAQs to invent.
Bottom-line decision rule
-
If products are disapproved, missing required attributes, or mismatched on price and availability versus the website, fix the core feed first.
-
If the core feed is stable but variants are messy, clarify item groups, titles, and structured variant attributes before writing FAQs.
-
If core data and variants are sound, add conversational attributes for high-intent SKUs where buyers ask nuanced questions the primary fields do not answer.
-
Use AI performance insights—when available—to choose which terms and missing attributes to populate, instead of enriching the entire catalog at once.
The Feed Readiness Ladder
Use this ladder to place your catalog before you staff a conversational-attribute project. Move up one level at a time. Skipping levels usually creates busywork without fixing discoverability or trust.
L0 — Unstable or non-compliant feed
Products fail policy checks, show recurring disapprovals, or cannot stay in sync with the website. Price and availability mismatches are especially costly because Google checks that Shopping ads and listings match the site. Automatic item updates can reduce some crawling mismatches, but Google notes they are not a replacement for up-to-date Merchant Center product data. At L0, conversational attributes are premature.
L1 — Required attributes and destinations working
Required attributes applicable to your products are present. Free listings and any Shopping destinations you rely on are not blocked by systemic data-quality issues. Images, identifiers, titles, and landing pages are consistent enough for verification. This is the minimum for reliable product visibility work.
L2 — Recommended attributes and freshness cadence
You submit recommended attributes that matter in your category, refresh feeds when the site changes, and keep shipping and returns accurate. Google’s high-quality data guidance emphasizes submitting applicable required attributes, including as many recommended attributes as practical, and updating Merchant Center when the website updates. L2 is where most catalogs should live before enrichment campaigns.
L3 — Conversational enrichment for priority SKUs
You add question_and_answer, document_link, related_product, and clearer variant grouping where buyers ask nuanced questions. Prefer a supplemental data source so enrichment does not risk the primary feed. Start with hero products, high-margin lines, or SKUs that already appear in AI performance insights for evaluation-stage queries.
L4 — Insight-led catalog iteration
You review AI performance insights routinely, map top terms and missing structured attributes into titles, descriptions, and attributes, and expand conversational fields where share of voice is weak on high-frequency intents. Google’s best practices for the report explicitly recommend high-quality data first, then implementing report recommendations and reviewing regularly. L4 is continuous optimization—not a one-time FAQ dump.
Conversational Attribute Priority Scorecard
Score each item 0 (no), 1 (partial), or 2 (yes). Total out of 14. Use the total to choose the next sprint.
|
Scorecard item |
0 |
1 |
2 |
|
Disapprovals and Needs Attention issues are under control |
Systemic blockers |
Recurring but managed |
Stable for priority SKUs |
|
Price and availability match the website on a reliable cadence |
Frequent mismatches |
Mostly synced |
Fetch/API timing aligned |
|
Required and category-critical recommended attributes are complete |
Many gaps |
Partial coverage |
Strong completeness |
|
Variant grouping is clear (item_group_id and distinguishing options) |
Broken or missing |
Inconsistent |
Consistent across heroes |
|
Buyer FAQs exist outside marketing copy (support, PDFs, PDP Q&A) |
No real FAQ source |
Scattered answers |
Curated source of truth |
|
You can submit enrichment via supplemental source or Merchant API |
No path |
Manual only |
Repeatable pipeline |
|
AI performance insights reviewed for a priority category (if available) |
Unavailable/unread |
Opened once |
Used for backlog |
Interpretation: 0–5 = stay at L0–L1 and repair core feed quality. 6–9 = finish L2 recommended attributes and variant clarity. 10–12 = begin L3 conversational enrichment on a short SKU list. 13–14 = operate at L4 with insight-led iteration.
Worked example: mid-size apparel brand
Hypothetical example: a 4,000-SKU apparel brand wants “AI Mode readiness” before peak season. Marketing proposes writing 20 FAQs per product. Merchant Center shows recurring size and color warnings on variants, occasional price mismatches after flash sales, and no supplemental feed process. AI performance insights (available in their country) show strong discovery-stage frequency for “breathable,” “machine wash,” and fit terms, with weak share of voice on evaluation-stage spec queries.
Scorecard reality check: disapprovals partially managed (1), price/availability cadence weak during promos (0), recommended attributes incomplete on materials and care (1), variants inconsistent (1), FAQ source exists in support tickets but unused (1), enrichment pipeline absent (0), insights reviewed once (1). Total: 5.
Two-week sprint based on the ladder:
-
Align promo price updates with Merchant Center fetches or Merchant API updates so flash-sale mismatches stop.
-
Normalize item_group_id, color, and size for the top 50 revenue styles; add item_group_title and variant_option only after groups are clean.
-
Populate missing material and care attributes called out in AI performance insights before writing new FAQ copy.
-
Only then create a supplemental feed with five high-value question_and_answer pairs for those 50 styles—drawn from real support tickets, not invented marketing language—and attach one care-guide PDF via document_link where it exists.
The brand does not need 80,000 FAQ fields in week one. It needs a stable core feed, clearer variants, insight-led attributes, and a small enrichment set it can maintain.
How to implement conversational attributes without breaking the feed
-
Pick a short SKU list. Start with products that already convert or already appear in AI insights for evaluation intents.
-
Audit duplication. If the answer already lives in description, product_highlight, or product_detail, do not paste it again into question_and_answer.
-
Use a supplemental data source when possible. Google recommends this path so enrichment stays separate from primary product submission.
-
Prefer real buyer questions. Pull from support tickets, returns reasons, size charts, and PDP Q&A—not speculative SEO keyword lists.
-
Add documents buyers actually need. Manuals and assembly PDFs via document_link are more useful than decorative brand PDFs.
-
Link related products carefully. Use related_product for true accessories or required parts with correct identifiers—not every cross-sell in the catalog.
-
Measure after, not before. Recheck AI performance insights and free-listing diagnostics after enrichment. Do not claim success from upload volume alone.
Shopify merchants selling into Google AI Mode and Gemini still depend on Merchant Center for product discovery. Shopify’s help documentation states that products must be available in Google Merchant Center—typically via the Google & YouTube sales channel with product and shipping sync enabled, or another Merchant Center connection—and that store policies must be complete. Conversational attributes remain a Merchant Center data decision on top of that channel setup; they do not replace feed accuracy or policy completeness.
Common failure patterns
-
FAQ theater on a broken feed. Writing hundreds of question_and_answer pairs while price mismatches and missing GTINs remain unresolved.
-
Duplicating primary fields. Copying description text into conversational attributes against Google’s explicit guidance not to duplicate description, product_highlight, or product_detail content.
-
Enriching the whole catalog on day one. Without a supplemental pipeline and ownership, enrichment goes stale faster than it helps.
-
Ignoring AI performance insights when available. Guessing FAQs while the report already surfaces popular attributes and intents for your category.
Limitations and exceptions
Conversational attributes are optional. They do not guarantee inclusion in AI Mode recommendations, Shopping ads, or free listings. Google’s lululemon testing result and the average conversion lift tied to core feed best practices should be read as directional platform evidence, not a forecast for your brand.
AI performance insights availability is limited to specified countries and English-language queries, and the report is category-scoped rather than one all-category view. If the report is unavailable in your market, still follow the ladder: core quality first, then carefully scoped enrichment.
If your bigger constraint is site trust, checkout friction, or paid acquisition structure, feed enrichment alone will not fix growth. Coordinate Merchant Center work with broader generative engine optimization services and, when the storefront itself is the bottleneck, with website and ecommerce development so product truth on the site and in the feed stay aligned.
Recommended next steps
-
Score your catalog with the Conversational Attribute Priority Scorecard today.
-
Identify your current Feed Readiness Ladder level and fund only the next level’s work.
-
If you are below L2, pause conversational-attribute projects until disapprovals, freshness, and critical attributes are stable.
-
If you are at L2 or higher, build a supplemental enrichment file for a short hero SKU list and measure with AI performance insights where available.
If you want help turning Merchant Center diagnostics and AI performance insights into a prioritized feed backlog, book a growth strategy session. Bring your Needs Attention export, a sample of top SKUs, and—if available—your AI performance category view; we will map whether you should stay on core feed repair or move into conversational enrichment.
