Short answer
Google has added a new Search Central page explaining how to identify search traffic in web analytics tools and server logs. It lists the Referer values Google Search sends, explains why the header is sometimes blank and why analytics data rarely matches Search Console clicks one to one. The search query is not included in this header.
Highlights
- Google Search sends only the domain in the Referer header; the page path, parameters and search query are not included.
- Discover and Google Images use the same values, so the Referer alone does not show which Google surface a visit came from.
- Redirects, cookie consent, ad blockers and private browsing can make Google traffic in analytics look lower than in Search Console.

3 min readAuthor: UNIT Journal EditorEditor-in-chief: Uğur Deniz İlhan
Google has added a new page to Search Central so that site owners can identify search traffic in their own analytics tools and server logs. The page covers the HTTP Referer header sent with a click and explains why the data does not match Search Console.
Which Referer values does Google Search send?
On the web, Google Search sends google.com or a country-specific Google domain. The Google app on iOS uses the same values, while the Android app can send its own android-app address when it opens the link in a browser tab.
Google uses the "origin" referrer policy. As a result, the header contains only the scheme and the domain; the page path, parameters and search query are not sent. For queries, Google points to the Performance report in Search Console.
There is an important limit, as Search Engine Journal points out: Discover and Google Images send the same values. A visit showing google.com tells you it came from Google, but not whether it came from Search or Discover. The page also does not deal separately with traffic from AI Mode or AI Overviews.
Why does analytics show less than Search Console?
Because the two tools count different things. Search Console records a click the moment a result is selected, whereas an analytics tool only sees the visit after the page loads and the tracking code runs. Private browsing, opening links in a new tab in some browsers, privacy extensions, ad blockers and cookie consent choices widen this gap.
The site itself can also distort the data. Redirects made with JavaScript or meta refresh can replace the Referer with your own address, and redirects that do not preserve the query string drop the gclid value used for ad tagging. In analytics, custom channel rules, referral exclusions or filters can also reclassify Google traffic as "direct" or "referral".
What should teams do?
- When matching server logs or custom analytics, include local Google domains and the Android app address in your rule, not just google.com.
- Count only landing page requests; image, CSS and JavaScript requests also carry a Referer, but its value is your own page's URL.
- Check your campaign and redirect setup: redirects on ad landing pages should keep query parameters, otherwise the gclid is lost.
- Separate Discover traffic using the Discover report in Search Console, not the Referer, and build your organic reports around that split.
- Track the gap between Search Console and analytics every month with the same method; a sudden widening may signal a tagging or redirect error.
Classifying the source of search traffic correctly is the first step in measuring the impact of SEO. An analytics and conversion optimisation setup that reads analytics alongside Search Console and CRM data catches these leaks in channel reports early.
Frequently asked
- Does the Referer header show the search query?
- No. Google Search sends only the domain; to see which queries bring visitors to your site, use the Performance report in Search Console.
Sources
- Google Search Central ·
- Search Engine Journal ·
Follow UNIT Journal
What's new in search, AI and technology, in your feed every day.


