Part of the AI Search series. For the full picture, start with Technical SEO and AI search readiness: the complete audit checklist.
AI search is easy to talk about and awkward to measure. A page can be quoted in an AI answer and get no click. A click from ChatGPT can arrive with a referrer, with a UTM tag, or with nothing at all. And Google’s AI Overviews look like a new channel but are counted as plain organic search.
This guide shows where each kind of AI visibility is recorded, what each source misses, and how to put them together.
What counts as “AI search traffic”?
Three different things get called that, and no single tool sees all of them:
| What happened | Example | Where it’s recorded |
|---|---|---|
| Your page was shown or cited in an AI answer | A supporting link in an AI Overview | Search Console (Google only) |
| Someone clicked through from an AI product | A visit from ChatGPT or Gemini | Google Analytics, if a referrer or UTM arrives |
| An AI system fetched your page | OAI-SearchBot indexing it; ChatGPT-User reading it for a user | Server logs |
Google AI Overviews and AI Mode
Impressions: Search Console’s Generative AI performance report shows “organic impressions from Search generative AI features”, which Google defines as “how many times links to your site were shown to a user in a generative AI feature.” You can break them down by page, country, device and date, and filter between text and multimodal results. Google says the report had reached all sites by August 31, 2026, but a site needs enough impressions in these features to see it, and sites opted out of generative AI features won’t have it.
Clicks: they’re inside the normal Performance report. Google’s AI features documentation says sites appearing in AI Overviews and AI Mode “are included in the overall search traffic in Search Console”, reported “within the ‘Web’ search type”. They aren’t separated from other organic clicks there.
In Google Analytics: the default channel group defines Organic Search as visits “via non-ad links in organic-search results, including Google’s AI Overviews and AI Mode.” They don’t appear in the AI Assistant channel.
So for Google’s AI features, the useful question is which pages earn generative AI impressions, and whether clicks to those pages hold up over time.
ChatGPT, Gemini, Copilot and other assistants
The AI Assistant channel in GA4
Google Analytics’ default channel group now includes an AI Assistant channel, “the channel by which users arrive at your site from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok.” Its rule assigns the medium ai-assistant and the campaign (ai-assistant) when “the referrer matches a list of AI Assistants.” It explicitly excludes AI Overviews and AI Mode.
Open the Traffic acquisition report with the session default channel group and you’ll see AI Assistant as its own row. Change the dimension to session source to see which assistants send visits.
Assistants the channel doesn’t name
Google’s page lists examples, not a full list. If a visit arrives with a referrer from an AI product that Analytics doesn’t recognise, it falls into the Referral channel instead. Check Session source / medium for referrers such as perplexity.ai or claude.ai, and if you want them grouped, create a custom channel group with your own rule for AI sources. You create one in Admin under Data display, starting from a copy of the default group; it needs Editor access to the property.
ChatGPT’s UTM tag
OpenAI’s publisher FAQ says “ChatGPT automatically includes the UTM parameter utm_source=chatgpt.com in referral URLs.” That makes ChatGPT visits identifiable even when a referrer is missing, as long as the URL keeps its parameters.
The visits you won’t see
Analytics attributes a visit from its referrer or campaign tags. When an assistant’s app opens a link without passing a referrer, or a user copies the link, the visit arrives with neither and is counted as Direct. A rise in Direct traffic to deep content pages, ones people rarely type or bookmark, is often the only trace of this.
Server logs: AI systems reading your pages
Logs record every request, including from AI crawlers that never send a human visitor. The operators document what each user agent is for:
| Kind | Examples | What a request means |
|---|---|---|
| Search crawlers | OAI-SearchBot, Claude-SearchBot, PerplexityBot | Your page is being indexed for that product’s answers |
| Training crawlers | GPTBot, ClaudeBot | Your page is being collected for model training |
| User-triggered fetchers | ChatGPT-User, Claude-User, Perplexity-User | A user’s request led the assistant to fetch your page |
The descriptions come from OpenAI, Anthropic and Perplexity. User-triggered fetches are the closest thing to a direct signal that AI users are reading your content, even when nobody clicks.
Import your access logs into Crawlens and the log analysis groups GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Perplexity-User and other AI user agents as AI crawlers, with a daily chart next to Googlebot and Bingbot. It shows the group as a whole; to compare individual bots, filter the raw log lines by user agent. Logs also tell you whether AI crawlers get errors or redirects instead of your content, which is worth fixing before anything else. See log file analysis for SEO.
How do you put it together?
A simple monthly view, per section of the site or per important page:
| Metric | Source | What it tells you |
|---|---|---|
| Generative AI impressions | Search Console, Generative AI performance report | How often Google’s AI features show your links |
| Organic clicks and impressions | Search Console, Performance report (Web) | Whether overall Google visibility is holding |
| AI Assistant sessions, by source | GA4 default channel group | Visits from recognised AI assistants |
| Other AI referrers | GA4 session source / medium or a custom channel group | Assistants the default list doesn’t name |
Sessions with utm_source=chatgpt.com |
GA4 | ChatGPT visits, even without a referrer |
| AI crawler requests and their status codes | Server logs | Whether AI systems can reach your pages, and how often they do |
| Direct sessions to deep content pages | GA4 | A rough signal of unattributed AI visits |
Then connect it to the site itself. The pages that earn AI impressions or visits are the ones to keep indexable, fast and current. In Crawlens, connecting Search Console and Google Analytics to a crawl puts clicks, impressions and sessions next to each URL’s technical state, so a cited page that starts returning errors or gets noindexed shows up as an issue: Pages with search traffic return errors, Pages with search traffic are not indexable and Landing pages with visits return errors.
For how to become a source in the first place, see how to appear in Google AI Overviews and the AI search readiness checklist.
Checklist
- Search Console Generative AI performance report checked (if available for your site)
- Organic Search in GA4 understood to include AI Overviews and AI Mode
- AI Assistant channel reviewed, by source
- Referral traffic checked for AI sources the channel doesn’t name; custom channel group if needed
-
utm_source=chatgpt.comsessions tracked - Server logs imported; AI crawler requests and status codes reviewed
- Direct traffic to deep content pages watched as a rough proxy
- Pages with AI visibility monitored for errors and indexability in every crawl
Frequently asked questions
How do I see ChatGPT traffic in Google Analytics?
GA4's default channel group has an AI Assistant channel for visits from sources such as ChatGPT, Gemini, Deepseek, Copilot and Grok. ChatGPT also adds utm_source=chatgpt.com to its referral links, so you can filter on that source too.
Is AI Overviews traffic shown separately in Google Analytics?
No. Google Analytics counts visits from AI Overviews and AI Mode in the Organic Search channel, and excludes them from the AI Assistant channel. Search Console's Generative AI performance report shows their impressions.
Why does some AI traffic show up as Direct?
Analytics needs a referrer or campaign parameters to attribute a visit. Visits from apps, copied links or browsers that strip the referrer arrive with neither, so they're counted as Direct.
Can I see how often AI tools read my pages?
Yes, in your server logs. AI companies identify their crawlers and user-triggered fetchers by user agent, such as GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot and PerplexityBot. Requests from user-triggered agents happen when someone's question leads the assistant to your page.
Does Search Console show clicks from AI Overviews?
Clicks from AI Overviews and AI Mode are included in the regular Performance report under the Web search type, mixed with other results. The Generative AI performance report is described in terms of impressions.