Industry Snippet

Google Documents the Referer Values Its Search Traffic Sends

Markdown
View as Markdown Open this page as plain text
This page as Markdown, ready to paste into ChatGPT, Claude or a doc.
RSS
On the left, a drawing of a browser tab for Schema Bean, an invented coffee shop, open on schemabean.co.uk/guides/flat-white/, with a Request Headers panel beneath the address bar listing accept, accept-language, referer and sec-fetch-site. The referer row, reading https://www.google.com/, is highlighted in yellow. On the right, a yellow Google Search label above the headline A Google referrer carries only the domain, and the line No path, no query, no search term. Discover and Google Images send the same values.
A drawing of the request a browser sends after a click from Google Search, not a screenshot: the referer carries Google's address and nothing after the slash.

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 happenedReferer value
Google Search on the webhttps://www.google.com/ or a local Google domain, such as https://www.google.co.uk/
Google app on iOShttps://www.google.com/ or a local Google domain
Google app on Androidhttps://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

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.

The How Google Search sets the Referer header section of Google's documentation. A paragraph says the Referer header contains only the scheme and host of the referring page, without the URL path or query parameters. The next paragraph introduces the table of Referer values, and its highlighted sentence says traffic from Discover uses the same values as the surface where the user viewed Discover, such as the Google app or Google Search on the web.
The opening of Google's page added on 12 November 2026. The sentence on Discover traffic is highlighted.

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.

The Match the Referer header in your analytics or logs section of Google's documentation. Its first paragraph says most web analytics systems automatically recognise these Referer values as organic search traffic from Google, and the highlighted sentence says that if Google Search traffic is missing or shows up as referral or direct traffic, check whether custom channel rules, referral exclusions or filters in your analytics configuration are reclassifying it.
The analytics section of the same page. The sentence on custom channel rules, referral exclusions and filters is highlighted.

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

More news