TLDR;
Google announced AI Performance Insights and richer product attributes in Merchant Center. Participating retailers can learn more about their presence in AI shopping and describe which needs a product suits. Check pilot coverage and recommendation accuracy, then compare visibility with actual sales results.
What happened
Google announced AI Performance Insights and conversational product attributes in Merchant Center. The reporting helps participating merchants assess presence in AI-powered shopping, while richer attributes describe product suitability; access and data coverage depend on the pilot and supported markets.
Why it matters
Conversational shopping depends on distinctions that traditional catalogue fields may not capture well. More detailed attributes can help establish whether a product meets a customer's needs, while reporting can reveal supported exposure. Neither capability removes the need to verify data coverage or connect observed visibility with commercial outcomes.
Richer product attributes can address a common gap between catalogue organisation and customer intent. A catalogue may contain a category, title and price, while the customer asks whether the item fits a particular situation. Suitability often depends on details such as materials, dimensions or compatibility, and those details need reliable ownership. AI Performance Insights can help identify supported exposure, but the report does not remove the need to check the product's actual representation. The enterprise opportunity is to use the two capabilities together: improve the information that supports matching, then investigate whether important products receive appropriate coverage. Pilot access and data definitions matter because an absent figure may reflect reporting scope rather than a lack of customer interest. The programme should reward accurate matching, not merely more complete fields or larger visibility totals.
How your brand can benefit / be affected
Check pilot access and the definitions behind each reported measure. Establish a baseline for important product groups and distinguish AI presence from traffic, orders and revenue.
Add supported attributes for compatibility, materials, dimensions and intended use, with an owner for accuracy and updates. Test representative customer scenarios and prioritise mismatches. Avoid filling fields with promotional assertions that cannot be substantiated by the product documentation.
Choose product groups where missing suitability information causes confusion or returns. Identify the supported attributes that describe real decision factors and source them from approved product information. Do not ask a team to invent attractive claims to fill every available field. Where a fact is unknown, resolve it with the product owner or leave the uncertainty explicit. Check consistency between Merchant Center, owned pages and any other supported product data route. A dimension or material stated differently in two places can undermine a recommendation even if both records look complete. Assign an update process for new variants and revised specifications.
Read the report definitions and establish a baseline within the pilot's actual coverage. Review whether the observed presence relates to useful product questions, then compare suitable engagement and completed orders separately. Test difficult cases where a visually similar product should not match the customer's requirement. Use the findings to correct attributes or destination content and monitor the relevant group after the change. Avoid interpreting an AI visibility increase as a revenue increase without downstream evidence. The commercial benefit is better-qualified discovery and fewer mismatched expectations. It requires catalogue discipline and measurement context, not simply access to a new reporting screen or a larger number of descriptive fields.
News date: 20 May 2026. Editorial review: 16 September 2026. Analysis includes subsequent developments where stated.