Google details search referrer values for analytics and logs
Google has published a new Search Central page listing the referrer values site owners may see from Google Search, Discover, and Google Images.
Google has added a new Search Central page explaining how site owners can identify traffic from Google Search in analytics tools and server logs. The update, reported by Search Engine Journal, lists the HTTP Referer values Google may send and explains why those numbers may not match Search Console.
The new page also says the same referrer values can appear for Discover and Google Images. That means a google.com referrer can show that Google sent the visit, but not which Google surface it came from.
What changed
Google Search now has documentation that spells out the origin-level referrer values a website may receive. Because Google Search uses an origin referrer policy, the referrer includes only the scheme and host, not the page path, query parameters, or the user’s actual search query. For query data, Google points site owners to Search Console’s Performance report.
The page also explains that Google Search on the web may send https://www.google.com/ or a local Google domain, and that the Google app can send similar values, including an Android app referrer in some cases. It adds that Discover and other Google services, including Google Images, can use those same origins. Google also explains several reasons analytics and Search Console counts can differ, including missing referrers, redirects, ad blockers, consent choices, privacy settings, and channel rules inside analytics software.
What it means for your website
If your reports show traffic from google.com, that does not automatically mean standard web search alone. The new documentation says Discover and Google Images can look the same in referrer data, so business owners should not rely on analytics referrers to separate those sources. If you want to split Discover from Search, Google says to use the Discover report in Search Console.
This also helps explain why traffic totals often do not line up between tools. Search Console records a click when a user selects a result, while analytics tools usually count a visit only after the page loads and the tracking script runs. Redirects, dropped query strings, stricter referrer policies, and custom analytics settings can all change what you see, especially on landing pages tied to ads or mobile traffic.
What to do now
- Review how your analytics platform classifies Google traffic, especially if some visits from Google appear as Referral or Direct instead of organic search.
- Use Google Search Console’s Discover report if you need to separate Discover clicks from standard search clicks.
- Check redirects on important landing pages and make sure they pass the full query string, so parameters such as gclid are not removed.
- When reviewing server logs or analytics, count requests to landing pages only, not requests for images, CSS, or JavaScript files.
- Monitor Google’s documentation updates log for revisions to this page, especially because the current documentation does not cover AI Mode or AI Overviews.
More from SEO News
All SEO News-
· Search Engine Journal
Google warns CDN moves can raise crawl load and hurt visibility
-
· Search Engine Journal
Optimizely Fixes Signup Flaw After Malware Hit Customer Sites
-
· Search Engine Journal
Google Ask Maps adds appointment finding and business calls
-
· Google Search Central Blog
Google adds new Search Analytics API filters and reporting