Google explains how Search traffic reaches your analytics, and leaves out AI Mode

Google has quietly published its first official explanation of exactly which browser referrer values Search sends to a site's analytics tools, closing a gap that has made "why don't my organic numbers match" one of the most common unanswered questions in SEO reporting.

The page landed in Google's Search Central documentation on Nov. 12, 2026, logged in the platform's own changelog as "Added documentation on identifying traffic from Google Search," with the stated goal of helping site owners identify and track Google Search traffic inside their own analytics setups. It isn't a blog post or a product announcement. It's a reference page, the kind Google tends to publish once enough people have asked the same support question often enough.

What the page actually says

The core of it is a list of HTTP Referer values. A click from Google Search on the web arrives carrying https://www.google.com/ or the equivalent local domain, such as google.co.uk. The Google app on iOS sends the same thing. On Android it's the same value too, unless the link opens in a separate browser tab, in which case the browser instead sees an android-app:// referrer. Discover carries whatever value belongs to the surface where someone saw it, so a Discover click inside the Google app and a Discover click on google.com can register differently. Google also confirms that other services sharing its origins, Google Images among them, send the identical referrer as Search, which is exactly why a referrer alone can never tell you which Google surface actually sent the visitor.

Underneath all of it sits one rule: Google uses what the page calls the origin referrer policy, so a Referer header only ever carries the scheme and the host.

"The referrer contains only the scheme and host, without the path or query parameters," Google's own Search Central documentation states.

No path, no query string, and never the search query itself. Search Console's Performance report remains the only place to see which queries actually drove the clicks.

Why two dashboards have never agreed

None of the individual facts here are new behavior. What's new is Google stating them in one place, including the specific reasons a real Search visit can show up in analytics as something else, or not at all. A referrer can arrive blank because of private browsing, anti-fingerprinting protections, how a given browser handles new tabs, or someone moving from a phone's native search widget into an external browser. A site's own redirect chain can erase the evidence before analytics ever sees it: a client-side JavaScript or meta-refresh redirect replaces the referrer with the site's own URL, a redirect that drops the query string takes tracking parameters such as gclid down with it, and a stricter Referrer-Policy header on that redirect can wipe the referrer out entirely. Google also warns that browsers attach a Referer to asset requests, images, stylesheets, scripts, so any count that isn't filtered down to landing-page hits will overstate traffic that's really just a page loading its own assets.

The page also spells out, more plainly than Google usually does, why Search Console and analytics will never produce identical numbers even when both are configured correctly. Search Console logs a click the moment someone selects a result; analytics logs a visit only once the destination page finishes loading and its tracking script runs, a gap that ad blockers, consent banners and privacy settings widen further. Search Console counts organic clicks only; whether a site's analytics includes Google Ads traffic in the same total depends entirely on how that account is set up.

• Check whether referral-exclusion lists or custom channel rules are quietly reclassifying Google Search visits as Direct or Referral
• Confirm redirects in the click path preserve query strings and don't attach a stricter Referrer-Policy header
• Strip out asset requests (images, CSS, JS) before counting referrer hits as visits
• Use Search Console's own Discover report to separate Discover clicks from Search clicks, since their referrers are identical

The traffic nobody can source

What the new page doesn't mention, at all, is AI Mode or AI Overviews. Search Engine Journal, which flagged the update on Nov. 13, points out that this leaves the actual sore spot untouched: Search Console's Performance report already folds classic results, AI Overviews and AI Mode clicks into one total, with no appearance-type filter that separates one from another. A marketer can now trace, with real precision, why a classic organic visit might arrive in their own analytics labeled as Direct. They still can't isolate, through any tool Google provides, how much of their traffic came from an AI surface instead of a traditional results page.

That's the gap software marketers actually feel day to day, as AI-driven discovery keeps taking a larger, less legible share of how buyers find a product before they ever type its name into a search box. Google just made the old plumbing easier to audit. It left the new plumbing exactly as opaque as it was before Nov. 12.