When someone clicks a Google Search result, Google sends only its scheme and host, such as https://www.google.com/, as the referrer. It never sends the search query. The Android Google app can send an android-app:// value instead. Some visits arrive with no referrer at all and get counted as direct traffic. To see queries, use Search Console, not analytics.
Google documented it in November
Google added a page to Search Central in November 2026, Identify Google Search traffic in your web analytics or server logs, listed on its documentation updates page. Most of it confirms what analysts suspected, but having it in writing settles a lot of arguments about “missing” Google traffic. If the term is new to you, start with our referrer glossary entry.
The values Google sends
Google Search uses the origin referrer policy. The Referer header contains only the scheme and host, with no path and no query parameters.
| Where the click happened | Referer value |
|---|---|
| Google Search on the web | https://www.google.com/ or a local domain such as https://www.google.co.uk/ |
| Google app on Android | android-app://com.google.android.googlequicksearchbox/https/www.google.com when the app opens the link in a browser tab, otherwise https://www.google.com/ |
| Google app on iOS | https://www.google.com/ or a local domain |
| Discover | The same value as the surface where Discover was viewed |
| Google Images and other services on the same origins | The same values as Search |
One consequence: from the referrer alone, you can’t tell a classic blue-link click from Images, Discover or a link inside an AI answer on the same domain. That split lives in Search Console, not in your analytics.

Why the query is never included
Google says plainly that the Referer header doesn’t include the search query, and points to the Performance report in Search Console for query data. Any tool claiming to recover Google keywords from your analytics is estimating, not reading them. Our Search Console guide covers where queries live.

Why some Google visits look like direct traffic
Even with the origin policy, the browser or operating system may drop the referrer. Google lists common cases:
- Private browsing and anti-fingerprinting protections
- Opening results in a new tab, in some browsers
- Moving from a native mobile search widget to an external browser
- Privacy extensions or strict browser settings
Analytics scripts can also miss visits because of consent choices and ad blockers. Your own site can strip the referrer too: Google notes that JavaScript or meta-refresh redirects can replace it with your own URL, and a redirect that sends a stricter Referrer-Policy header can remove it. Our explainer on noopener and noreferrer covers the link-level side of the same header.
Check your channel rules
Google says most analytics tools recognize these values as organic search automatically. If Google traffic shows up as referral or direct, check whether custom channel rules, referral exclusions or filters are reclassifying it. In GA4, three things are worth checking:
- Custom channel groups. Make sure the organic search rule still matches Google sources, including the Android app value, before any referral rule catches it.
- Unwanted referrals. Excluding Google domains there, sometimes done to fix payment-gateway issues, can hide real search visits.
- Redirect chains. Test your most-linked old URLs. A client-side redirect can turn a Google visit into self-referral or direct traffic.
For server logs, match only requests for landing pages. Images, CSS and scripts carry your own page as the referrer.

Why analytics won’t match Search Console
Expect a gap, even with perfect setup. Search Console counts a click when someone selects a result. Analytics counts a session only after the page loads and the tracking code runs. Privacy tools, consent banners and redirects widen the gap. Search Console reports only organic clicks, while analytics totals may include ads. Track the trend in each tool rather than trying to make them agree.
Don’t tag your own way out
It can be tempting to add UTM parameters to fix attribution. They’re right for links you place, such as email, social posts, Business Profile links and ads. Never add them to internal links, and you can’t add them to Google’s organic results. For AI assistants that do pass a referrer, such as chatgpt.com or perplexity.ai, set up a separate channel so those visits don’t get mixed into generic referrals. Our AI visibility measurement guide covers the rest.
Clean measurement is unglamorous and slow to set up, but every later decision depends on it. That’s the long run in practice.
