Site icon Impact Digital

How to Identify Google Search Traffic in GA4 and Logs

Diagram of a visitor clicking a Google result and the Referer header reaching a website analytics report

If you run a small site, blog or online shop, you probably check where visitors come from every week. On 12 November 2026 Google added a Search Central page that explains how to identify traffic from Google Search using the HTTP Referer header. This guide is for site owners, bloggers and small agencies who want to understand what that header shows, what it leaves out, and why your analytics numbers will never match Search Console exactly.

What Google announced

The Search Central updates log lists the 12 November 2026 entry as “Added documentation on identifying traffic from Google Search”, described as a new page about identifying traffic from Google Search using HTTP Referer headers. The page itself is titled “Identify Google Search traffic in your web analytics or server logs”. It does not announce a new feature or ranking change. It documents values your analytics tool or server already sees, so you can recognise Google visits when you build reports or parse logs.

What a Referer header is

When someone clicks a link, the browser can tell the destination site which page the visitor came from. That is the Referer header (spelled that way in the header name). In JavaScript the same information appears as document.referrer. Analytics tools read it to label a visit as organic search, referral or direct.

The referrer values Google sends

According to Google’s page, these are the values to expect:

Where the visitor clickedReferer value
Google Search on the webhttps://www.google.com/, or a local domain such as https://www.google.co.uk/ or https://www.google.co.jp/
Google app on Androidandroid-app://com.google.android.googlequicksearchbox/https/www.google.com when the app opens the link in a browser tab, or https://www.google.com/ (or a local domain)
Google app on iOShttps://www.google.com/ (or a local domain)
DiscoverThe same values as the surface where the user saw it: the Google app or Google Search on the web
Other Google services on the same origins, such as Google ImagesThe same values, so that traffic matches these patterns too

Two practical points follow. First, the Android app value starts with android-app://, not https://, so a log filter that only looks for “google.com” with a web scheme could miss it. Second, Google Images traffic shares the same patterns, so you cannot separate it from web search using the referrer alone.

The Search Central page does not mention AI Overviews or AI Mode, so this article makes no claim about what referrer those features send. Some industry sites may discuss it; treat that as reported only until Google documents it.

What the header does not contain

Google uses the origin referrer policy. Per MDN, that policy sends only the origin (scheme, host and port) whether the request is same-origin or cross-origin, so a page at https://example.com/page.html sends https://example.com/. Google’s page states that the header holds only the scheme and host of the referring page. In plain terms:

For queries, Google points you to the Performance report in Search Console. If you want a walkthrough, see our guide on finding quick SEO wins in the Search Console Performance report.

When the Referer is missing

Even with the origin policy, a browser or operating system may drop the header or block document.referrer. Google lists 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, and privacy extensions or strict browser settings. JavaScript tracking can also miss visits because of consent tools and ad blockers. Those visits usually fall into “direct” in your reports even though they began on Google.

Why analytics and Search Console disagree

Google says identifying Search traffic this way “isn’t exact”. The documented reasons are:

How this appears in GA4

Google Analytics Help defines the default channel group rules. Organic Search applies when the source matches a list of search sites or the medium exactly matches “organic”. Referral applies when the medium is “referral”, “app” or “link”. Direct requires the source “(direct)” with a medium of “(not set)” or “(none)”. “Unassigned” appears when no other channel rule matches. The same help page describes Organic Search as covering non-ad links in organic search results, including Google’s AI Overviews and AI Mode. That is Analytics’ channel definition, not a statement about referrer headers, and Search Central does not address it.

To view it, open Reports, then Acquisition, then Traffic acquisition. Analytics Help notes that if the report is missing it may have been hidden from your default view, and Editors and Administrators can add it back to the left navigation. Traffic acquisition describes each user’s most recent session, while User acquisition shows only where new users came from. Compare the right report with the right question: Traffic acquisition for “how did sessions arrive this month”, User acquisition for “how did new people find us”.

Because Google Search arrives as https://www.google.com/ and similar values, GA4 normally recognises it without extra work. If your data looks wrong, Google’s page suggests checking for custom channel rules, referral exclusions or filters that might reclassify the traffic as referral or direct.

Practical checks to run

  1. Look at the channel report. In GA4 go to Reports > Acquisition > Traffic acquisition and confirm Organic Search is present and plausible compared with last month.
  2. Check for Google as a referral. If google.com shows as a referral source, look for custom channel groups or rules that could be misclassifying it.
  3. Review unwanted referrals. In Admin, under Data collection and modification, open Data streams, choose Web, select the stream, click Configure tag settings, then Show all and List unwanted referrals. Analytics Help says you can list up to 50 domains per stream and need Editor access or higher. Make sure google.com is not on that list, because listed domains do not appear as traffic sources.
  4. Audit redirects. If your site uses JavaScript or meta refresh redirects on landing pages, test whether they change the visitor’s referrer. Prefer server-side redirects that keep the query string where it matters.
  5. Count landing pages only in logs. Browsers also send a Referer for images, CSS and JavaScript, with your own page’s URL as the value, so count only requests for landing pages.
  6. Compare trends, not totals. Put Search Console clicks and GA4 organic sessions side by side over several weeks. A steady ratio is normal; a sudden break is worth investigating.

If you tag your own campaigns, keep those separate from organic search. Our UTM parameters in GA4 tagging guide covers how to label links so they do not muddy organic numbers, and the GA4 key events setup guide shows how to measure what organic visitors do once they arrive.

Common mistakes

Key takeaways

FAQ

Can I see which keywords sent a visitor from the Referer header?

No. Google states the header does not include the search query. Use the Performance report in Search Console for queries.

Why does Search Console show more clicks than GA4 shows organic sessions?

Search Console counts the click on a result, while analytics counts a visit only after the page loads and tracking runs. Blockers, consent choices and redirects add further gaps, so some difference is expected.

Does the origin policy mean Google sends my full URL somewhere?

No. The origin policy applies to the page the visitor came from, here Google, and sends only its scheme and host. Your own site’s referrer behaviour is controlled separately by your site’s Referrer-Policy.

What referrer do AI Overviews or AI Mode send?

Google’s new page does not say. Analytics Help describes the Organic Search channel as including those features, but that is a reporting definition. Any specific referrer claims from industry sites are reported only and unconfirmed.

Sources

Exit mobile version