TLDR;
Google confirmed that dedicated AI visibility reports in Search Console had reached websites worldwide. Enterprise brands can now build a broader baseline across their sites. Keep AI impressions separate from visits, conversions and revenue so exposure is not mistaken for commercial success.
What happened
Google confirmed that its dedicated generative AI performance insights in Search Console had rolled out to all websites worldwide. The update broadened access beyond the June subset, giving more brands a consistent first-party view of their pages’ impressions within supported AI search and Discover features.
Why it matters
The wider rollout removes an important access limitation from the June launch. Enterprise groups can use a more consistent first-party source across their website portfolio, while still respecting property coverage and metric definitions. A reported impression describes exposure in supported features, not what the user understood or whether the brand won a customer.
Worldwide reporting access makes it easier for an enterprise group to establish a portfolio baseline without relying on the June launch's limited availability. It does not make every property directly comparable. Sites can serve different markets and customer needs, and the supported feature contexts and metric definitions still determine what an impression represents. The enterprise opportunity is to organise first-party evidence consistently, then investigate important changes at the page or topic level. The danger is aggregating figures into a large reach claim without checking overlap or relevance. A property may gain exposure for low-value informational material while losing useful demand elsewhere. The report becomes commercially valuable when it helps teams understand where to investigate, with visits and business outcomes kept alongside it as separate evidence.
How your brand can benefit / be affected
Review all relevant properties and establish comparable market and page-group reporting. Document the supported Search and Discover contexts, start dates and definitions before aggregating figures.
Use the reports to identify material changes and prioritise answer-quality or source investigations. Keep qualified visits, conversions and revenue alongside the visibility data as separate outcomes. Check for overlapping reporting before presenting a portfolio-wide reach number.
Inventory the relevant Search Console properties and decide which page groups serve each business objective. Record report start dates, supported contexts and any coverage differences before building comparisons. Check ownership boundaries so the same material or reporting context is not counted twice in portfolio totals. Establish a baseline for priority markets and topics, then retain enough detail to investigate movements. Do not make every site's target a simple increase in AI impressions. A service page and a corporate newsroom may have very different reasons to be visible, and their results should be interpreted against those purposes.
Use material changes to trigger a source and journey review. Check whether the affected pages are current, accessible and useful for the associated customer questions, then review relevant referrals or qualified outcomes where evidence exists. Annotate content changes and shifts in reporting so a new data view is not credited as an acquisition improvement. Explain to stakeholders that exposure can grow without a matching increase in visits or revenue. The wider rollout supplies a stronger common measurement foundation; the enterprise still needs commercial interpretation and accountable action. A useful dashboard should lead to a focused investigation or decision, rather than simply add another growing total to the management report.
News date: 31 August 2026. Editorial review: 16 September 2026. Analysis includes subsequent developments where stated.