Google Explains How to Spot Search Traffic in Analytics and Logs

On November 12, 2026, Google added a new Search Central page explaining how to identify Google Search traffic in your web analytics or server logs using the HTTP Referer header, and why those numbers often won't match Search Console.

What changed

Google's Search Central documentation updates log lists the change on November 12 as "Added documentation on identifying traffic from Google Search." The new page, Identify Google Search traffic in your web analytics or server logs, covers a few practical points that are useful to have from Google directly:

• Only the domain is passed. Google Search uses the origin referrer policy, so the Referer header contains just the scheme and host, such as https://www.google.com/, not the full URL.
• No search terms. The Referer doesn't include the query someone searched. For query data, Google points you to the Performance report in Search Console.
• The values to look for. Search on the web sends https://www.google.com/ or a local Google domain such as google.co.uk. The Google app on Android can send android-app://com.google.android.googlequicksearchbox/https/www.google.com when a link opens in a browser tab. The Google app on iOS sends https://www.google.com/ or a local Google domain.
• Other Google surfaces look the same. Discover uses the same values as the surface where someone viewed it, and other Google services on the same origins, such as Google Images, send the same values too.

The page also explains why some visits arrive with no Referer at all, including private browsing, anti-fingerprinting features, links opened in a new tab in some browsers, moving from a native mobile widget to an external browser, and privacy extensions or strict settings.

Who it affects

Anyone who reports on organic traffic. That includes business owners checking Google Analytics, in-house marketers explaining why analytics and Search Console disagree, and agencies building client reports. It's also useful if you or your developer look at raw server logs.

What to do now

• Check your channel setup. Google says most analytics tools classify these Referer values as organic Google traffic automatically. If Search visits are showing up as referral or direct, it suggests checking your custom channel rules, referral exclusions and filters.
• Count landing pages only in logs. Browsers also send a Referer when loading images, CSS and JavaScript, but those values are your own page URL. Google says to count only requests for landing pages when matching Google's Referer values.
• Review your redirects. Google notes that client-side redirects can replace the Referer with your own page's URL, redirects that drop query strings lose parameters such as gclid, and a stricter Referrer-Policy on a redirect can remove the Referer. If you've changed URLs or added redirect rules, it's worth testing a few.
• Set expectations on reports. Use Google's explanation of why the numbers differ when a client or manager asks why analytics shows fewer visits than Search Console shows clicks.

If you'd like help getting this right, my SEO reporting and analysis and technical SEO work both cover it. I've also shared some Google Analytics 4 reporting tips.