Tracking Generative AI Traffic: New Search Console Performance Reports Explained
Google introduces dedicated reporting for Search Generative Experience, allowing local businesses to separate AI-driven visibility from traditional SERP metrics.

Google has formally introduced dedicated reporting for AI-driven search experiences within its primary webmaster toolset. Last updated June 3, 2026, the Google Search Central Blog announced the launch of new Search Console Generative AI reports, designed to help site owners understand how their content surfaces within generative summaries and conversational interfaces.
For local operators, this represents a significant shift in how traffic must be audited. Previously, clicks from AI-generated overviews were often blended with standard web results, making it difficult to determine if a site was winning space in the new AI snapshots or simply maintaining its legacy blue-link positions. We believe this granularity is essential for businesses that rely on geographically specific traffic, where the "AI answer" often serves as the final gatekeeper before a user decides to visit a storefront.
How does the reporting structure change for local intent?
The new reporting mechanism separates data by surface, providing specific tabs for Search and Discover within the generative context. In the past, a dental practice in Leeds might see a surge in traffic and attribute it to improved organic rankings. With these reports, that same practice can now see if their recent blog post on "emergency tooth extraction" was specifically cited by Google’s AI as a primary resource for a user’s conversational query.
This distinction is particularly important for local businesses because AI overviews frequently aggregate information from multiple sources to answer localized needs. Unlike the traditional Local Pack, which prioritizes business profile data, the generative experience often pulls from deep-site content. The new Search Console Generative AI reports provide the first clear evidence of which specific pages are fueling these AI-driven responses.
Analyzing visibility with Search Console Generative AI reports
For a 12-location HVAC operator, the data provided in these reports allows for a more nuanced content strategy. By filtering by the "Generative AI" appearance type, the operator can identify if their service area pages are appearing when users ask complex, multi-layered questions like "how to maintain a heat pump in a coastal climate."
Before this update, quantifying the value of these long-tail, informational queries was a matter of guesswork. Now, Google explicitly identifies the impressions and clicks generated by these interactions. We have observed that this helps distinguish between users who are simply browsing and those who have been funneled through an AI-led research phase before reaching a site's contact page.
Are local queries attributed differently in AI reports?
A central concern for local SEOs is whether Google attributes local intent queries differently when they pass through a generative filter. While traditional search results prioritize proximity and relevance, generative summaries often lean on authority and content depth. The Search Console Generative AI reports allow us to contrast these two paradigms.
For example, a boutique hotel in the Lake District might find that while they rank in position two for "luxury hotels Cumbria," they are the primary citation in a generative overview for "quietest hotels with lake views for a weekend trip." The reports show that the generative interface creates a new competitive layer where a site can dominate a conversation even if it lacks a top-three blue-link ranking for the head term.
What this means for local businesses
To prepare for this shift in reporting, we recommend local operators and their agencies take the following steps:
- Segment your traffic sources: Regularly compare your "Search Appearance: Generative AI" data against your standard web search impressions to identify if your traditional visibility is being cannibalized by AI summaries.
- Audit citation frequency: Use the new reports to identify which specific pages are most frequently referenced by AI; these are your "authority pillars" and should be updated more often.
- Map long-tail queries to AI clicks: Connect query-level data in the generative report to your local landing pages to see if AI is better at matching complex local needs than traditional search.
- Refine content for conversational depth: If impressions in the generative report are high but clicks are low, consider improving the structured data or readability of your local service pages to make them more attractive as AI citations.
Sources
Frequently asked questions
- Where can I find the new generative AI data in Search Console?
- The data is located within the Performance report section. Users can filter by 'Search Appearance' and select 'Generative AI' to isolate traffic and impressions specifically originating from AI-driven summaries and conversational results.
- How does this differ from traditional search reporting?
- Traditional reporting tracks interactions with blue links and standard search features. The new reporting specifically isolates traffic from the Search Generative Experience (SGE), helping marketers distinguish between users engaging with AI-generated answers and those using traditional search paths.
- Does this report include Local Pack results?
- Currently, these reports focus on the web-based citations and links within the generative summaries. While local queries trigger these summaries, the standard Local Pack metrics generally remain in their existing categories unless they are part of a generative response interface.


