Google Documents the Referer Values Its Search Traffic Sends
Google added a page to its Search Central documentation on 12 November 2026, “Identify Google Search traffic in your web analytics or server logs”. Google’s changelog lists it as added documentation, not a change in what Google sends. It states that Google Search uses the origin referrer policy, so the Referer header carries only the scheme and host of the page the click came from: the https:// at the start of the address and the site name after it. Everything after that, including the search term, is dropped. The values Google lists, by where the click happened:
| Where the click happened | Referer value |
|---|---|
| Google Search on the web | https://www.google.com/ or a local Google domain, such as https://www.google.co.uk/ |
| Google app on iOS | https://www.google.com/ or a local Google domain |
| Google app on Android | https://www.google.com/ or a local Google domain, or android-app://com.google.android.googlequicksearchbox/https/www.google.com when the app opens the link in a browser tab |
Can you tell Discover and Google Images traffic apart from Search?
Not from the referrer. The page says Discover traffic “uses the same values as the surface where the user viewed Discover”, and that other Google services served from the same origins, such as Google Images, send the same values too. Google began moving Discover in Chrome from a www.googleapis.com referrer to https://www.google.com/ in February 2021, to match the Google app.
Search Console splits them: Discover has its own performance report, and the Search results report has a search type filter for web and image results. The page does not mention AI Overviews or AI Mode.
What should you check in analytics and server logs?
Google says most analytics systems recognise these values as organic search from Google, and that if Google Search traffic shows up as referral or direct, custom channel rules, referral exclusions or filters may be reclassifying it.
For server logs, count only requests for landing pages, because images, CSS and JavaScript files carry your own page’s URL as their referrer. The page also names site-side causes of lost attribution: client-side redirects, such as JavaScript or meta refresh, that replace the referrer with your own URL, and redirects that send a stricter Referrer-Policy header.
It lists why analytics visits will not match Search Console clicks one to one: privacy settings and extensions that strip the header, and Search Console recording a click when the link is selected while analytics records a visit only once the page loads and runs its tracking code. The other sources of unattributed visits are covered in dark traffic and attribution.
Sources
- Identify Google Search traffic in your web analytics or server logs, Google Search Central
- Latest Google Search documentation updates, Google Search Central
- Search Console Discover report now includes Chrome data, Google Search Central Blog
- Understanding data discrepancies between Google Analytics and Search Console, Google Search Central
More news
-
Google: Moving to a CDN Can Raise Crawling Before the Cache Is Ready
Google says a CDN switch can raise Googlebot's crawl rate while the cache is still empty, loading the origin. The fix: pre-warm, allow verified bots, use 429.
-
Reddit Reviews Turns Product Threads Into AI Review Pages Brands Can't Buy Into
Reddit is testing AI review pages for about 10,000 products, built from user threads. Brands can't pay to appear, so conversations decide what a review says.
-
Discord Is Putting Public Server Chats in Search. Will SEOs Treat It Like Reddit?
Discord's public servers get search-visible pages from 16 November, then member messages: the first-hand talk that drew SEOs to Reddit, within tighter limits.