TLDR;
Google introduced dedicated AI impression reports for an initial group of Search Console sites and announced controls over inclusion in AI features. Brands can see more of their exposure and make clearer content-use decisions. The reports still do not show the full journey to a sale.
What happened
Google introduced Search Console views for impressions within generative AI features in Search and Discover, initially for a subset of sites. It also announced new website-owner controls over inclusion in AI features; the reports focus on visibility and should not be mistaken for revenue or a complete attribution model.
Why it matters
Impressions within supported generative AI features can reveal exposure that blended search reporting obscured. They still cannot explain the full customer journey or assign revenue by themselves. The controls also raise a different question: whether inclusion in each experience supports the enterprise's acquisition, publishing or content-rights objectives.
Dedicated reporting can make AI exposure easier to discuss because it separates a supported feature's impressions from a broader search total. That is a measurement improvement, but it is not a complete account of customer influence. Impressions do not show whether the answer was favourable, accurate or commercially relevant. Inclusion controls address another question altogether: whether the enterprise wants its content available in a particular experience. Combining those decisions into one dashboard can create pressure to maximise exposure without considering rights, audience or business purpose. The sensible response is to define the metric and the desired participation policy separately. Initial access was limited to a subset of sites, so portfolio comparisons also need to account for availability before interpreting differences as performance gaps.
How your brand can benefit / be affected
Check whether your properties have access and read the precise report definitions. Keep Search and Discover contexts distinguishable, establish a baseline and avoid counting overlapping measures as independent reach.
Review inclusion controls with the owners of search performance, content and commercial strategy. Document the intended result before changing settings and monitor the effects afterwards. Treat the June subset as an initial rollout, with later worldwide availability recorded separately.
Record which properties have access, the feature contexts covered and the earliest usable reporting period. Group pages by commercial purpose and keep Search and Discover definitions clear. Check whether any totals overlap before adding them together or comparing with existing reports. Build a baseline that allows future changes to be investigated without implying that a new screen creates a new audience. Review sampled answer accuracy separately where practical, since an impression count does not describe the quality of the representation. Explain those boundaries in enterprise reporting so stakeholders understand what the additional visibility does and does not reveal.
Assess inclusion settings with the owners of content, acquisition and commercial policy. Write down the intended benefit or concern for the affected material before changing access. A publisher's licensing decision and a retailer's product discovery decision may have different priorities even within one corporate group. Test the supported setting on a bounded scope and monitor both the intended effect and valuable discovery. Retain the configuration and change date for later investigation. Keep the June announcement as the initial rollout in the archive, with subsequent wider access identified separately. This supports deliberate participation and useful measurement without treating visibility growth as the only acceptable enterprise outcome.
News date: 3 June 2026. Editorial review: 16 September 2026. Analysis includes subsequent developments where stated.