Google AI Mode referrer: can you isolate AI Mode clicks?
What Referer Google Search sends on web, Android and iOS, why it goes missing, and why no Google AI Mode referrer value separates AI clicks from organic ones.
By Crawlito · 9 min read
In short
- Google Search uses the origin referrer policy, so the Referer header carries only the scheme and host, such as https://www.google.com/, with no path or query parameters.
- Google's page on identifying Search traffic lists Referer values for the web, Android and iOS but no value that marks a click from AI Overviews or AI Mode, and GA4 counts both features under Organic Search.
- On Android the Google app can send android-app://com.google.android.googlequicksearchbox/https/www.google.com when it opens a result in a browser tab, so log rules that only match google.com miss those visits.
- Search Console counts a click on an external link in an AI Overview or in AI Mode as a click, inside the Web search type, while the Generative AI performance report shows impressions only.
- When you count Google visits in server logs, count requests for landing pages only, because images, CSS and JavaScript carry your own page's URL as the Referer.
On this page
- What Referer values Google Search sends
- Is there a Referer value for AI Mode or AI Overviews?
- Why the Referer goes missing
- How to count Google Search visits in server logs
- Why your numbers will not match Search Console
- What to use instead of a referrer for AI features
- Frequently asked questions
- Make sure Google visitors land on readable pages
No. At the time of writing you cannot isolate Google AI Mode or AI Overviews clicks by their referrer. Google Search sends its Referer under the origin referrer policy, so your server or analytics tool sees only https://www.google.com/ or a local Google domain, the same value a click from an ordinary blue link sends. Google's page on identifying Google Search traffic lists the values for web, Android and iOS and does not mention AI features at all. What you can do is count Google Search visits correctly, understand why they never match Search Console, and use the Generative AI performance report for the AI side, which reports impressions rather than clicks.
Google added that page to its documentation on 12 November 2026, according to the Search Central updates log. This post works through it with AI Mode in mind. For GA4 channel setup, see the GA4 AI traffic guide. For crawler counts, see measuring AI crawler traffic.
What Referer values Google Search sends
Google's page gives one table of values. Condensed:
| Where the click happened | Referer you receive |
|---|---|
| Google Search on the web | https://www.google.com/ or a local Google domain, such as a .co.uk or .co.jp domain |
| Google app on Android | android-app://com.google.android.googlequicksearchbox/https/www.google.com when the app opens the link in a browser tab, or https://www.google.com/ (or a local domain) |
| Google app on iOS | https://www.google.com/ or a local Google domain |
| Discover | The same values as the surface where the person saw it, such as the Google app or Google Search on the web |
| Other Google services on the same origins, such as Google Images | The same values |
Two details in that table matter for measurement.
Only the origin is sent. Google says it uses the origin referrer policy, so the header contains the scheme and host and nothing else: no path, no query parameters. A request from a Google results page looks like this whatever kind of results page it was:
GET /pricing HTTP/2
Host: example.com
Referer: https://www.google.com/Whatever distinguishes a results page that shows an AI Overview, or an AI Mode conversation, never reaches you in the header. The search query is not included either. Google points you to the Search Console Performance report for queries.
The Android value is not a URL on google.com. A log filter or analytics rule that matches only google. hostnames in https:// referrers will miss visits that carry the android-app:// value. Most analytics tools already classify these values as organic Google traffic, Google says, but a hand-written log query has to include both forms. If Google traffic shows up as referral or direct in your analytics tool, Google suggests checking custom channel rules, referral exclusions and filters.
Is there a Referer value for AI Mode or AI Overviews?
Not one that Google documents. The identifying-traffic page treats Google Search as one source: it lists values by surface (web, Android app, iOS app, Discover) and none of them is specific to an AI feature. Google's AI features documentation says sites that appear in AI Overviews and AI Mode are included in overall search traffic and reported in the Performance report under the Web search type. It does not describe a separate referrer, tracking parameter or analytics dimension for those clicks.
So in practice:
- In analytics, a click from an AI Overview link or from AI Mode lands in the same organic Google bucket as any other Google result. GA4's default channel group definitions say this outright: the Organic Search channel includes Google's AI Overviews and AI Mode, and the AI Assistant channel (sources such as ChatGPT, Gemini, Deepseek, Copilot or Grok) excludes them.
- In server logs, the request looks identical to a classic organic click: same Referer, no query string added by Google.
- Any tool or report that claims to split AI Mode clicks out of referrer data is inferring it from something other than the documented header. Ask what that something is before you trust the number.
If you have seen landing URLs with extra fragments or parameters and assumed they come from AI features, treat that as an observation to test, not a documented signal. URL fragments (the part after #) are never sent to the server at all.
The difference between the two features themselves is covered in AI Mode vs AI Overviews.
Why the Referer goes missing
Some Google Search visits arrive with no Referer at all and end up in Direct. Google lists these documented causes:
- Private browsing and anti-fingerprinting protections in the browser.
- Opening search results in a new tab, in some browsers.
- Moving from a native mobile search widget to an external browser.
- Privacy extensions or strict browser settings.
Separately, JavaScript tracking can miss visits that did carry a Referer, because of privacy settings, consent management or ad blockers. Your server logs still see those requests; your analytics tag does not.
There is also a cause you control. Google notes that client-side redirects can replace the Referer with your own page's URL, that redirects which drop the query string lose parameters such as gclid, and that a stricter Referrer-Policy on a redirect can remove the Referer entirely. If your landing URLs redirect, for example from http to https or to add a trailing slash, check the response headers on the redirect:
curl -sI https://example.com/pricing | grep -iE '^(HTTP|location|referrer-policy)'A Referrer-Policy: no-referrer on that hop is worth fixing before you trust any Google traffic trend. For client-side redirects (JavaScript or meta refresh), the next request carries your own URL as the Referer, so the Google origin is lost before the final page loads.
How to count Google Search visits in server logs
Server logs give you the most complete view of visits with a Google Referer, because they do not depend on a tag running. Google's page makes one point that is easy to get wrong: when a page loads, the browser also sends a Referer for its images, CSS and JavaScript, and that value is your own page's URL. To count Search visits, Google says, only look at requests for the landing pages themselves.
This query for the nginx or Apache "combined" log format counts landing-page requests with a Google Search Referer, by path. It matches both the https:// and android-app:// forms, keeps only GET requests that returned 200, and drops static assets:
awk -F'"' '
$4 ~ /^https:\/\/www\.google\.([a-z]{2,3}|co\.[a-z]{2}|com\.[a-z]{2})\/?$/ ||
$4 ~ /^android-app:\/\/com\.google\.android\.googlequicksearchbox\// {
split($2, req, " "); split($3, st, " ")
if (req[1] == "GET" && st[1] == "200" &&
req[2] !~ /\.(css|js|mjs|map|png|jpe?g|gif|svg|webp|avif|ico|woff2?|ttf|json|xml|txt)(\?|$)/)
print req[2]
}' access.log | sort | uniq -c | sort -rn | head -25How to read and adjust it:
- In the combined format, splitting on
"puts the request line in field 2, the status code at the start of field 3, the Referer in field 4 and the user agent in field 6. - The hostname pattern is an approximation of Google's local domains, such as
google.de,google.co.ukandgoogle.com.au. Google does not publish a regex. Runawk -F'"' '{print $4}' access.log | grep -i google | sort | uniq -conce to see what you actually receive and widen the pattern if needed. - If your site serves HTML from extensionless API paths, exclude those as well, or you will count XHR and fetch requests from your own pages.
- Bots can send a fake Google Referer. Exclude requests whose user agent is a known crawler before you report the total.
The result is a count of human-looking landing requests from Google Search, all surfaces combined. It still cannot tell you which of them came from AI Mode.
Why your numbers will not match Search Console
Even a clean log count will differ from Search Console clicks, and Google lists the reasons on the same page:
| Reason | Effect |
|---|---|
| Privacy and client settings | Scripts blocked, query parameters stripped, Referer suppressed |
| Redirects | Referer replaced (client-side redirects) or removed (stricter Referrer-Policy), gclid lost with the query string |
| Different measurement | Search Console counts a click when the person selects the link; analytics counts a visit only after the page loads and runs the tag |
| Paid and organic | Search Console reports organic clicks only and excludes Google Ads; analytics may include paid traffic, depending on configuration |
Two more points come from Google's Performance report help. Clicking a link to an external page in an AI Overview counts as a click, and so does clicking an external link in AI Mode. And in general, Google says a click is any click that sends the user to a page outside Google Search, Discover or News. So Search Console clicks already include AI feature clicks, folded into the Web search type, and Google does not document a Performance report filter that separates them.
The practical consequence: a gap between Search Console clicks and your log or analytics count is normal, and the size of the gap says nothing about AI Mode. For diagnosing a real drop, use the step-by-step process in organic traffic dropped: is it AI Overviews?.
What to use instead of a referrer for AI features
Since the referrer cannot do it, use the one Google report that is specific to AI features. Search Console's Generative AI performance report covers AI Overviews and AI Mode. Per its help page:
- It shows impressions only: how many times links to your site were shown in a generative AI feature. The page does not mention clicks or click-through rate.
- You can break impressions down by page, country, date and device, and filter by Web: text-based or Web: multimodal search.
- It is based on the Web search type in the Performance report, excludes Search Labs experiments, and may not appear if your site has too few generative AI impressions.
- Google says it became available for all websites worldwide as of 31 August 2026.
A careful way to combine the two sources, without pretending they measure the same thing:
- Export the top pages by generative AI impressions for a month.
- Run the log query above for the same month and the same pages.
- Put both columns side by side and label them honestly: "impressions in Google AI features" and "landing visits from Google Search, all features".
That table shows where you appear in AI features and how much Google traffic those pages receive overall. It does not show how many of those visits came from AI features, and you should not divide one column by the other. Our guide to the Generative AI performance report covers the report in more depth, and AI citations vs referral traffic explains why visibility and clicks belong in separate rows.
Frequently asked questions
What referrer does Google AI Mode send?
Google does not document a separate one. Google Search uses the origin referrer policy, so a click from AI Mode arrives with https://www.google.com/ or a local Google domain, the same as other Google Search results.
Can GA4 separate AI Overviews clicks from organic search?
No. GA4's channel definitions put AI Overviews and AI Mode clicks in the Organic Search channel and exclude them from the AI Assistant channel, and the Referer gives you nothing to split them out with.
Why do some Google visits show an android-app referrer?
Google says the Google app on Android can send android-app://com.google.android.googlequicksearchbox/https/www.google.com when it opens a result in a browser tab. Count it as Google Search traffic in log queries and channel rules.
Does Search Console count clicks from AI Mode?
Yes. Google's Performance report help says clicking a link to an external page in AI Mode or in an AI Overview counts as a click, reported under the Web search type. Google does not document a filter that isolates those clicks.
Why do my log counts include image and CSS requests from Google?
They usually do not come from Google. The browser sends your own page's URL as the Referer for a page's assets, and Google advises counting only requests for the landing pages themselves.
Make sure Google visitors land on readable pages
Measurement tells you where Google sends people. Whether Google can show your page in AI features at all depends on it being crawlable and indexable. As a next step, run the free check on one of your top landing pages: it checks a single page and needs no account. It does not read your logs or Search Console data.
Filed under Strategy and audits. Topics: google, analytics, measurement, ai-overviews, server-logs