PingTalks PingTalks
SEO News 7 min read

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.

Laptop on a desk showing an analytics dashboard used to identify Google Search traffic

Key takeawaysThe story in 20 seconds

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.

Marketer checking Google Search traffic in an analytics dashboard
Most organic Google visits arrive looking identical, whatever surface they came from.

What does Google’s new referrer doc actually say?

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.

Can you separate AI Mode traffic from normal Google search in GA4?

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.

3referrer values Google lists for Search traffic
0of them separate AI Mode or AI Overviews clicks
9 to 11 NovSearch Console GenAI report impressions understated

Where each Google surface lands: our table

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 surfaceReferrer sentSeparable by referrer?Usual GA4 channel
Classic web resultsgoogle.com or google.co.inNoOrganic Search
AI Overviews and AI ModeNot documented separatelyNoOrganic Search, per GA4 help
DiscoverSame as the app or web surfaceNoUsually Organic Search; can show as referral or direct
Google app on Androidandroid-app://com.google.android.googlequicksearchbox/…PartlyOrganic 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.

Hand holding an Android phone using a search app
Android app visits can carry their own referrer string, which some setups mislabel.

Why don’t GA4 sessions match Search Console clicks?

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.

Who disagrees, and where we could be wrong

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.

PingTalks verdict

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.

How do you identify Google Search traffic in GA4 in 10 minutes?

Each check takes two minutes. Only the last needs a developer.

  1. Find leaked Android visits. In GA4, open Reports, then Acquisition, then Traffic acquisition. Switch the dimension to Session source / medium and search for googlequicksearchbox. Any rows marked referral are organic visits in the wrong bucket.
  2. Check custom channel groups. Go to Admin, then Data display, then Channel groups. If your team built a custom group, confirm no rule sends Google sources to Referral or Direct.
  3. Check referral exclusions. In Admin, open Data streams, then Configure tag settings, then List unwanted referrals. Google domains should not be there.
  4. Match your logs. We built this pattern from Google’s listed values for log tools: ^https://www\.google\.[a-z.]+/$|^android-app://com\.google\.android\.googlequicksearchbox. Count only landing-page requests, not CSS or image files.
  5. Test one redirect. Click your own result from Google and watch the network tab. If you see a JavaScript or meta-refresh hop, ask your developer for a server-side 301 that keeps the query string.
Developer reviewing server logs on a monitor
A server-side redirect keeps Google's referrer and your gclid intact.
Read rankings after 24 November 2026

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.

What to do now

  • Search GA4 for googlequicksearchbox today and fix any referral rows with a custom channel rule.
  • Annotate 9 to 11 November in your reporting deck as a Search Console logging error.
  • Replace JavaScript redirects on top landing pages with server-side 301s.
  • Add a separate AI Assistant view to your GA4 dashboard for ChatGPT and Gemini, and keep Google AI surfaces in Search Console.
  • Track AI bot crawling for free with Microsoft Clarity’s AI visibility if you need more than Google gives you.

Frequently asked questions

Can I see AI Mode traffic separately in GA4?

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.

What referrer does the Google app on Android send?

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.

Why is GA4 organic traffic lower than Search Console clicks?

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.

Does the Referer header show the search keyword?

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.

Is the Search Console Generative AI report wrong for November?

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.

Sources

Kousik BhattacharyaEditor, PingTalks

Digital Evangelist and Entrepreneur at Clickseek Digital. A results-oriented marketing leader with an 18+ year track record driving transformative growth for diverse global businesses. Expert in performance marketing, demand generation, customer acquisition, strategic partnerships, and market expansion within B2B SaaS, Consumer-Tech, Fintech, Travel/Hospitality, and CRM/ITES Solutions sectors. IIM alumnus with a strong analytical background and a string of accolades, including "Top 50 Most Influential E-Commerce Professional of India" and "Top 100 Digital Marketer of India."

Two stories a day. Zero noise.

What changed in marketing and AI, why it matters and exactly what to do. In your inbox at 11:00 IST.