Google publishes guide to finding Search traffic in analytics
Google has published a Search Central page listing the HTTP Referer values Google Search sends when someone clicks through to a website, and explaining why the visits counted in analytics or server logs rarely match the clicks in Search Console. The page, titled "Identify Google Search traffic in your web analytics or server logs", was added to Google's documentation update log on 12 November 2026.
Google says the page was added "to document how site owners can identify and track traffic from Google Search in their web analytics systems." Nothing on the page describes a change in how Google sends traffic; it writes down behaviour that already existed. It arrives while the November 2026 core update, which began on 10 November, is still rolling out, and that is when owners look hardest at traffic reports and are least sure what each number means.
What referrer does Google Search send?
Google Search uses the origin referrer policy. When a visitor arrives from a search result, the browser tells your site the visit came from https://www.google.com/ (or a local Google domain; the page's examples are google.co.uk and google.co.jp) and nothing else. The path of the results page and the search query are never passed on, so you have to look up the organic query in Search Console's Performance report.
The page breaks the values down by where the click happened. Google Search on the web and the Google app on iOS send https://www.google.com/ or a country domain. The Google app on Android sends either that value or android-app://com.google.android.googlequicksearchbox/https/www.google.com when the app opens the link in a browser tab. A log filter that only matches strings beginning with https://www.google will not catch the Android app value.
Discover and Google Images visits look like Search clicks
Discover traffic uses the same Referer values as the surface where the person saw Discover, so a Discover visit from the Google app or from Google on the web is indistinguishable from a Search click in your logs. Other Google services served from the same origins, Google Images among them, send the same values.
A google.com referrer therefore tells you Google sent the visitor and no more. Search Console's Discover report is where Discover clicks are separated from Search clicks.
The page says nothing about AI Mode or AI Overviews, and gives no separate value for clicks from either. Search Console's standard Performance report counts those clicks together with the rest, so nothing on this page lets you split them out. Search Console also has a separate Generative AI performance report in Search for properties that have it; Google logged a bug that under-counted its impressions from 9 to 11 November, during the first days of the core update.
Most analytics tools count visits without a referrer as Direct
Even with Google's policy set, the visitor's browser or operating system can drop the Referer header entirely, or block JavaScript from reading document.referrer. Google lists the situations where this happens by default:
- private browsing, and the anti-fingerprinting features some browsers build in
- some browsers when a result is opened in a new tab
- a jump from a phone's built-in search widget into a separate browser app
- privacy add-ons or tightened browser settings
A visit that arrives with no referrer cannot be matched to Google, and most analytics tools file it under Direct. Where Search visits are missing or land under Referral or Direct, Google points to your own setup: custom channel groupings, the referral exclusion list and any filters can all reclassify them.
Google adds that JavaScript-based tracking can miss visits altogether because of browser privacy settings, consent management and ad blockers. Consent is the mechanism behind the 32% figure in the GA4 Christmas orders audit, where one retailer's analytics logged 32% of its orders after its consent banner switched itself off.
Why analytics rarely matches Search Console clicks
The section most owners will want is the one on why the numbers never line up. Google says matching the Referer header is not exact and that analytics or log data "often doesn't match 1:1" with the clicks Search Console reports.
The main reason is what each tool measures. Search Console records a click the moment someone selects a link on the results page. An analytics tool records a visit or session only after your page has loaded and run its tracking code. An ad blocker or a declined consent banner stops that code, which produces a click in Search Console with no matching session.
Paid traffic adds a second gap. Search Console reports organic clicks only and never includes Google Ads clicks, while analytics totals may include paid visits depending on how the property is configured. A site that compares all Google traffic in GA4 against Search Console clicks is comparing two different things.
The gap can run the other way as well. Search Console can record clicks that may never show up as visits, as with the early November Search Console click spikes that rose 2x to 6.5x on some sites while impressions stayed flat and looked automated.
Site redirects can drop the Google referrer
Redirects on your own site get their own entry. If a page bounces visitors on with JavaScript or a meta refresh, the browser can report your own URL as the referrer instead of Google's, so the visit looks internal. If any hop in the chain sets a tighter Referrer-Policy, the referrer can vanish altogether.
Redirects that do not preserve the query string drop URL parameters, and Google gives gclid, which it describes as commonly used for ad tagging, as an example. Any advertiser running landing pages through a redirect should confirm the query string survives every hop.
For server logs there is one more rule. Your server log also records a Referer on the images, stylesheets and scripts a page pulls in, and on those requests the value is your own URL rather than Google's. Filter the log down to landing page hits before you count anything.
Run five traffic checks before blaming the core update
A site whose organic numbers look odd this month now has Google's own list of reasons to work through before putting the change down to the core update.
- In GA4, confirm that visits with a google.com referrer and no paid tags sit in Organic Search. If some sit in Referral or Direct, check custom channel groups, the referral exclusion list and any filters.
- Take a sample of landing pages from Search Console and load each one from a Google result. Note any redirect before the final page and check that the final URL still carries the query string.
- Check the Referrer-Policy header your pages and any redirect hops send.
- If you run Google Ads, exclude paid sessions before comparing anything to Search Console.
- Compare Search Console clicks with GA4 organic sessions for the same pages and dates, and expect analytics to come in lower. Record the ratio. A gap that holds its size through the update is normal; a ratio that moves is what to investigate.
For anyone building reports from server logs, Google's table is now the reference list of Referer values to match, including the Android app string. Match it against landing page requests only. The total covers all Google traffic from those origins, including Discover and Images, and still undercounts it, because blank referrers are missed.
If the two reports have never been reconciled on your site, do it once now and write down the normal gap. That number is what makes next month's report readable.
