If you have ever opened your analytics, looked at a chunk of traffic labeled Direct, and thought that cannot be right, you are probably correct. Some of that traffic came from Google Search. It just arrived without the label that would prove it.
Google has now published something that helps you sort this out. A new page on Search Central lists the exact HTTP Referer values Google Search sends when someone clicks through to your site. For anyone who reports on traffic, it settles arguments that have been running for years. Here is what it says, what it does not say, and what you should change in your own setup because of it.
What Google Actually Published
Google added a page to Search Central that documents how site owners can identify and track traffic from Google Search inside their analytics tools. The page lists the referrer values that Search sends, and it explains why some visits show up with no referrer at all.
The key detail is the referrer policy. Google Search uses the origin referrer policy, which means only the scheme and host of the referring page are sent. You get https://www.google.com/ or a local Google domain such as https://www.google.co.uk/. You do not get the search query, the path, or any parameters. For the actual queries behind your clicks, Google still points you to the Performance report in Search Console.
The same values apply beyond web search. The Google app on iOS sends the same google.com values. The Google app on Android sends those values too, or an android-app value when it opens the link in a browser tab. Discover traffic carries the values of whichever surface it was viewed on, and Google Images sends the same values as well. So a google.com referrer tells you Google sent the visitor, but it cannot tell you whether they came from Search, Discover, or Images.
What a Referrer Value Can and Cannot Tell You
A referrer value is a clue, not a full story. It can confirm that a visit came from Google. It cannot tell you which Google surface sent it, and it cannot tell you what the person searched for.
That distinction matters more than it sounds. Many teams try to split Search and Discover traffic using referrer data, and the page is clear that this will not work. The values overlap by design. If you want to separate Discover clicks from Search clicks, use the Discover report in Search Console, not your analytics referrer column.
The same logic applies to reporting. When traffic carrying Google referrer values shows up in your analytics, it is generally classified as organic traffic from Google Search. But if you find some of it filed under Referral or Direct, your own setup probably reclassified it. Custom channel groupings, referral exclusion lists, and filters can all move Google traffic into the wrong bucket without anyone noticing. Google’s published list gives you the reference values to check your own rules against.
Why Some Google Visits Arrive With No Referrer
The page also explains the visits that arrive with nothing at all. Browsers and operating systems can strip the referrer header for privacy reasons. That happens when someone searches in private mode, opens a link in a new tab depending on the browser, or jumps from a mobile search widget into an external browser.
Your own site can cause the same problem. Client-side redirects can replace the referrer with your own domain, so the visit looks like it came from inside your site. A redirect that drops the query string can also strip parameters such as gclid, the tag Google Ads uses to identify paid clicks. A redirect with a stricter Referrer-Policy header can remove the referrer altogether.
This is the part most teams miss. The missing referrer is often not a Google problem or a browser problem. It is a redirect problem, and redirects are something you control.
Why Search Console and GA4 Will Never Match
Search Console records a click every time someone selects a link in the results. Analytics records a visit only after the page has loaded and the tracking script has run. Ad blockers, consent choices, and privacy settings can stop the script, so the visit never appears in analytics even though the click is real.
The two tools also measure different things. Search Console tracks organic clicks only. Analytics totals may or may not include Google Ads traffic, depending on how your site is set up. And when you count Google Search referrals, Google says to count only requests to your landing pages. Requests for images, CSS, and JavaScript files carry your landing page URL as their referrer, so including them inflates your count.
None of this means one tool is wrong. They count different events at different points in the journey, and treating them as the same number is the mistake.
What to Do This Week
This is a small document, but it gives you a practical checklist. Work through it before your next reporting cycle.
First, pull the list of referrer values from Google’s page and compare it with the values your analytics actually sees. If you find google.com referrers filed under Referral or Direct, fix your channel grouping or referral exclusions so they land under organic search.
Second, check your redirect setup. If your paid landing pages redirect, confirm the redirects pass the query string through. Losing a gclid breaks your paid attribution, and it is one of the gaps Google names directly in the page.
Third, audit your client-side redirects and your Referrer-Policy header. A redirect that swaps in your own domain as the referrer, or a policy stricter than the default, quietly turns traceable Google traffic into mystery traffic.
Fourth, stop trying to split Search and Discover in analytics. Use the Discover report in Search Console for that split, and use the standard Performance report for queries. Referrer data was never built for that job.
Fifth, keep an eye on the documentation update log. The page was last updated on November 12, and it does not cover AI Mode or AI Overviews. Search Console’s standard Performance report counts clicks in both categories but has no search appearance type that separates them. The page also does not mention the google.com/goto redirect links that have been appearing in results since late August.

FAQ
What referrer values does Google Search send?
Google Search sends https://www.google.com/ or a local Google domain such as https://www.google.co.uk/. The Google app on Android may also send an android-app value when it opens a link in a browser tab. Only the origin is sent, never the query or path.
Can I tell Search traffic apart from Discover traffic using referrer data?
No. Discover, Google Images, and Search send the same values, so a google.com referrer cannot identify the surface. Use the Discover report in Search Console to separate Discover clicks from Search clicks.
Why does some Google traffic show up as Direct in my analytics?
Browsers and operating systems can remove the referrer header in private mode, in new tabs, or when moving from a search widget to a browser. Your own redirects and Referrer-Policy settings can also strip it. When no referrer arrives, analytics often files the visit as Direct.
Why do Search Console clicks and GA4 sessions never match?
Search Console counts a click when someone selects a link. GA4 counts a session only after the page loads and the tracking script runs, which ad blockers and consent choices can prevent. Search Console also tracks organic clicks only, while analytics may include paid traffic.
Does Google’s page cover AI Mode or AI Overviews?
Not yet. The page was last updated on November 12 and does not mention AI Mode, AI Overviews, or the google.com/goto redirect links in results. Watch Google’s documentation update log for revisions.