Google added new Search Central documentation on 12 November explaining how to identify Google Search traffic in analytics platforms and server logs. It sets out the HTTP Referer values sent after search-result clicks and why Search Console click counts may not match sessions recorded by Google Analytics or a publisher's own measurement system.
The Google documentation says Search uses the `origin` referrer policy: the destination generally receives the referring host, not the user's search query or the full search-result URL. Web clicks usually show a Google domain, while some Android app flows send an `android-app://` value. Google Images and Discover can share these referrer values, so the header alone cannot reliably distinguish those surfaces.
Google lists several reasons for discrepancies: privacy controls and blockers, redirects that alter or remove parameters, different counting methodologies and the distinction between paid and organic traffic. Search Console records an organic click when a user selects a result; web analytics usually starts recording only after the destination page loads and tracking executes. A direct subtraction of the two reports can therefore be misleading.
As PPC Land notes, this is an attribution and documentation update, not a new ranking signal or a separate, confirmed AI Mode traffic channel. Publishers and SEO teams should audit channel definitions, referral exclusions, redirect chains and consent settings before treating mismatched reports as evidence of organic traffic loss.

Комментарии