To track ai search traffic in google search console, you must use query-based filtering and regular expressions to isolate traffic likely originating from Google AI Overviews. While Google does not currently provide a dedicated toggle for AI-generated traffic, monitoring impressions for informational long-tail queries and comparing them with GA4 referral data from sources like Perplexity and ChatGPT provides a comprehensive view of your performance. This approach allows you to differentiate between traditional blue-link clicks and the newer generative search experiences that are reshaping the search landscape.
The current state of AI search tracking
As of the current reporting standards, Google Search Console (GSC) does not provide a separate 'AI' dimension in its performance reports. Traffic from AI Overviews (formerly Search Generative Experience or SGE) is aggregated into the standard 'Web' search results. This makes it difficult for operators to see exactly how much traffic is being cannibalized by AI summaries or, conversely, how much traffic is being driven by the links within those summaries. To build a reliable picture of your AI search visibility, you must look at two distinct data streams: internal Google search data (via GSC) and external referral data from chatbots (via GA4).
Tracking this data is essential because AI Overviews often occupy the most valuable screen real estate, especially on mobile devices. If your impressions are rising but your click-through rate (CTR) is falling on high-volume informational terms, it is a strong signal that an AI Overview is satisfying the user's intent without them needing to click through to your site. Conversely, for complex queries, being the primary source cited in an AI Overview can lead to a significant boost in high-intent traffic.
Step-by-step: How to track ai search traffic in google search console
The most effective way to isolate potential AI traffic in GSC is by using regular expression (regex) filters to target the types of queries that trigger AI Overviews. These are typically informational, question-based, or long-tail queries.
1. Using regex for ai search console filtering
Navigate to the Performance report in GSC and click on '+ New' -> 'Query' -> 'Custom (regex)'. To find queries that are most likely to trigger AI Overviews, use a regex string that captures common informational prefixes. Use the following regex to filter your query report:
^(who|what|why|how|can|is|are|will|should).*
By isolating these queries, you can monitor their performance over time. If you notice a sudden drop in CTR for these specific terms while impressions remain steady, it is highly probable that Google has started displaying an AI Overview for those keywords. For a more detailed breakdown of this technique, see our guide on Using Google Search Console Regex for Long Tail Analysis.
2. Monitoring CTR shifts in informational queries
Once you have filtered for informational queries, compare the current period with the previous period (e.g., last 28 days vs. previous 28 days).
- Scenario A: Impressions up, Clicks down, CTR down. This suggests an AI Overview is providing the answer directly, leading to 'zero-click' searches.
- Scenario B: Impressions up, Clicks up, CTR stable. This suggests your content is being cited as a 'source card' within the AI Overview, driving traffic even if the user doesn't click the traditional blue links.
3. Comparing desktop vs. mobile data
AI Overviews often appear differently or more frequently on mobile. In GSC, filter by 'Device' and compare mobile vs. desktop performance for your top informational queries. Significant discrepancies in CTR between devices often point to different AI layout configurations.
SGE traffic analysis: Identifying the citation gap
SGE traffic analysis involves identifying which pages are most likely to be used as sources in AI Overviews. Google tends to pull information from pages that have high topical authority and clear, structured answers. To verify if a specific page is gaining AI traffic, look for 'long-click' behavior in GA4 (sessions with high engagement time) coming from queries you identified in GSC.
If you are serious about maintaining visibility in these results, it is worth investing in advanced technical seo services to ensure your site's infrastructure—such as schema markup and site speed—is optimized for Google's crawlers to easily parse and cite your content.
Monitoring Perplexity referral traffic and ChatGPT in GA4
While GSC tracks Google's internal AI search, it cannot track traffic from third-party chatbots like Perplexity, ChatGPT, or Claude. For these, you must use Google Analytics 4 (GA4).
1. Creating a GA4 ai search source channel group
To see all AI traffic in one place, you should create a Custom Channel Group in GA4. This allows you to group traffic from various AI engines into a single category called 'AI Search'.
- Go to Admin -> Data Settings -> Channel Groups.
- Click Create new group.
- Add a new channel called 'AI Search'.
- Set the condition to:
Sourcematches regex.*(perplexity|chatgpt|openai|anthropic|claude|gemini).*.
2. Analyzing referral patterns
Traffic from Perplexity often shows up as perplexity.ai / referral. Traffic from ChatGPT can appear as chatgpt.com, openai.com, or sometimes direct if the link is opened in a way that strips referrer data. By isolating these sources, you can see which of your pages are being recommended by AI agents. We have found that pages optimized for specific, high-intent questions perform best here; for more on this, read about optimizing content for Perplexity and ChatGPT search answers.
Comparison: GSC vs. GA4 for AI tracking
| Feature | Google Search Console (AI Overviews) | GA4 (Chatbot Referrals) |
|---|---|---|
| Tracking Method | Query & CTR Analysis (Regex) | Source/Medium & Referral Data |
| Primary Metric | Impressions & Clicks | Sessions & Conversion Rate |
| Data Source | Google-internal | External AI Platforms |
| Accuracy | Estimated (Blended with organic) | Precise (When referrer is passed) |
| Primary Use Case | Monitoring 'Zero-Click' impact | Measuring AI-driven conversions |
Worked example: Retail brand AI traffic audit
A mid-size e-commerce brand noticed a 15% drop in traffic to their 'How-to' blog section. By following these steps, they performed an audit:
- GSC Filter: They applied the regex
^(how to|what is).*and found that while impressions were up 5%, clicks had dropped 20%. - Visual Check: They manually searched their top 5 queries and confirmed that Google had implemented a 'Product' AI Overview for each.
- GA4 Check: They checked their 'AI Search' channel group and saw that while Google traffic was down, Perplexity referral traffic had increased by 40%, specifically to their 'Best [Product] for [Use Case]' guides.
- Action: They pivoted their content strategy to focus on more complex, opinion-based reviews that AI Overviews are less likely to summarize perfectly, successfully recovering their click volume within 60 days.
Common mistakes in AI search tracking
- Over-reliance on 'Search Appearance' filters: Many users wait for a 'Generative' filter to appear in GSC. While Google has tested this, it is not consistently available to all users. Waiting for it means missing current data trends.
- Ignoring 'Direct' traffic: A portion of AI traffic, particularly from mobile apps (like the ChatGPT app), often loses its referrer data and is categorized as 'Direct'. If you see a spike in Direct traffic to deep content pages without a clear cause, AI referrals are a likely culprit.
- Focusing only on Clicks: In the AI era, impressions matter more than ever. Even if a user doesn't click, seeing your brand name cited in an AI Overview builds 'mental availability' and brand trust, which may lead to a direct search later.
When this is not worth it
Tracking AI search traffic requires a significant amount of manual data manipulation. If your website receives fewer than 1,000 organic visits per month, the sample size is likely too small to draw meaningful conclusions from CTR shifts or regex filtering. In these cases, the 'noise' of standard search volatility will outweigh the 'signal' of AI traffic. Focus instead on basic content quality and technical SEO fundamentals until your traffic volume justifies the time spent on deep data analysis.
Checklist for monthly AI traffic reporting
- Run the informational query regex in GSC and compare CTR to the previous month.
- Check for new 'Source' entries in GA4 under the Referral report.
- Review the 'Engagement Rate' for AI-referred traffic (it is usually higher than standard organic).
- Manually audit your top 10 most-trafficked keywords to see if an AI Overview is present.
- Update your Custom Channel Group in GA4 as new AI startups emerge.
By systematically applying these filters and monitoring the right sources, you can turn the ambiguity of AI search into actionable data that informs your broader marketing strategy.