Identify Google Search Traffic: What Google’s New Doc Admits
Google's new referrer page explains how to identify Google Search traffic in GA4 and logs. It also confirms AI Mode, Discover and Images clicks look the same.

Google's new referrer page explains how to identify Google Search traffic in GA4 and logs. It also confirms AI Mode, Discover and Images clicks look the same.

01Google Search Central published a page on 12 November 2026 explaining how to identify Google Search traffic using HTTP Referer headers.
02Google Search sends only the scheme and host as the referrer, so search queries never appear in GA4 or server logs.
03Discover and Google Images clicks send the same referrer values as Google Search, and the page gives no separate value for AI Overviews or AI Mode.
04Google Analytics counts AI Overviews and AI Mode clicks as Organic Search and excludes them from the AI Assistant channel.
Your GA4 report can’t tell an AI Mode click from a classic blue-link click, and Google has now put that in writing. On 12 November 2026, Google Search Central published a new page explaining how to identify Google Search traffic in analytics and server logs, and the most useful part is what it can’t separate.
The timing matters. The November 2026 core update started rolling out on 10 November and can take up to two weeks. If your Google numbers swing this fortnight, you need to know which report to believe before you rewrite a single page.

Google says its Search pages send an HTTP Referer header that carries only the scheme and host, such as https://www.google.com/ or a local domain like https://www.google.co.in/, never the path or the query. That is the “origin” referrer policy, so no search term ever reaches your logs or GA4.
The page lists three referrer values. Google Search on the web sends the Google domain. The Google app on iOS sends the same. The Google app on Android sends either the web value or a longer string, android-app://com.google.android.googlequicksearchbox/https/www.google.com, when it opens your page in a browser tab.
Then the admission. Discover clicks carry the same values as the surface where someone saw the feed, and Google Images sends the same values too. Luis Rijo of PPC Land pointed out in his breakdown of the page that it says nothing about AI Overviews or AI Mode at all.
No. Google Analytics’ own help page defines the Organic Search channel as including clicks from AI Overviews and AI Mode, and it excludes both from the newer AI Assistant channel that catches ChatGPT, Gemini, Copilot and others. With identical referrers and one channel, there is no clean split inside GA4.
The only place Google breaks out AI surfaces is the Search Console Generative AI performance report, which we walked through on 2 November. Even that wobbled this week: Google logged an error that understated its impressions for 9 to 11 November. Google says only the data logging was hit, not rankings.
We compared Google’s referrer page with the GA4 channel rules to map where each surface ends up. This is our reading of both documents, not a Google table.
| Google surface | Referrer sent | Separable by referrer? | Usual GA4 channel |
|---|---|---|---|
| Classic web results | google.com or google.co.in | No | Organic Search |
| AI Overviews and AI Mode | Not documented separately | No | Organic Search, per GA4 help |
| Discover | Same as the app or web surface | No | Usually Organic Search; can show as referral or direct |
| Google app on Android | android-app://com.google.android.googlequicksearchbox/… | Partly | Organic Search, unless a custom rule moves it |
Indian sites should audit that Android row first, because most Indian mobile visits come from Android phones. If your setup treats the long string as a referral, real organic traffic from Jaipur to Coimbatore is sitting in the wrong channel.

They measure different moments. Search Console counts a click the instant someone taps your result, while GA4 records a visit only after the page loads and the tag fires. Ad blockers, consent banners, private browsing and redirects all sit in the gap, and Google’s page lists each of them.
Two causes are worth chasing because you control them. JavaScript or meta-refresh redirects swap Google’s referrer for your own URL, so the visit looks internal. And a redirect that drops the query string strips the gclid, which quietly breaks Google Ads attribution too.
Our maths, as an illustration only: say Search Console shows 10,000 clicks for a week and GA4 shows 7,800 organic sessions. That 22% gap is your baseline, not a verdict, and it moves with your consent banner and audience. If it jumps to 40% the week you migrate a template, check your redirects before you blame the core update.
Watch out: do not compare 9 to 11 November impressions in the Generative AI report against any other week. Google has flagged those three days as a logging error.
Possibly, and it would make this doc read differently. On 13 November, consultant Glenn Gabe shared screenshots of a test with no AI Mode tab in the results page and no “Ask anything” box under AI Overviews, as Search Engine Roundtable reported. Google has not commented on it.
If AI answers stop being a separate destination, everything becomes plain Google Search, which is how the referrer page already treats it.
Google has told you, in its own docs, that one report will never show where AI answers send your visitors.
Barry Schwartz, editor of Search Engine Roundtable, wondered why Google published the page at all, given how little Google Search traffic he says he sees lately. A fair reading: this is housekeeping, and serious SEO teams knew these values already.
We think the value is the paper trail. When a client or CFO asks why GA4 can’t show AI Mode revenue, you can now link Google’s own words. Our verdict is weakest for large publishers running server-side tagging with custom parsers. They may already split traffic in ways a GA4 default setup never will.
Stop promising clients an “AI Mode traffic” number from GA4. It doesn’t exist. Use Search Console’s Generative AI report for AI surface trends, GA4 Organic Search for revenue, and spend 10 minutes this week checking that Android app visits aren’t leaking into Referral. Skip any tool that claims to isolate AI Overview clicks from referrers alone.
Each check takes two minutes. Only the last needs a developer.

The November core update has a rollout window of up to two weeks from 10 November. Compare full weeks after it ends, as our core update tracker explains.
No. Google Analytics counts AI Overviews and AI Mode clicks under Organic Search, and they share the same referrer as normal results. Use the Search Console Generative AI performance report for AI surface trends.
It sends either the normal Google domain or android-app://com.google.android.googlequicksearchbox/https/www.google.com when it opens a page in a browser tab. Some analytics setups mislabel the second value as a referral.
Search Console counts a click when the result is tapped, while GA4 needs the page to load and the tag to fire. Consent banners, ad blockers, private browsing and client-side redirects all widen the gap.
No. Google Search uses the origin referrer policy, so only the scheme and host such as https://www.google.co.in/ are passed. Query data is only available in the Search Console Performance report.
Google confirmed a logging error that lowered impressions in that report for 9 to 11 November 2026. Google says it affected data logging only, not actual search performance, so exclude those days from comparisons.
What changed in marketing and AI, why it matters and exactly what to do. In your inbox at 11:00 IST.