What Counts as Google Search Traffic?
A visit to one of your pages whose HTTP Referer header shows that the click came from Google Search. The Referer is the header a browser sends to say which page a visitor came from. Google says its own page lets you find these visits “in addition to using Search Console,” and it adds a warning: the header “doesn’t include the search query” (Google doc). Queries still live only in Search Console’s Performance report.
How to Identify Google Search Traffic at a Glance
| Step | Action | Expected result |
|---|---|---|
| 1 | Check your analytics channel rules | Google visits land in Organic Search, not Referral or Direct |
| 2 | Get the Referer field from your logs | One Referer value per request |
| 3 | Keep landing-page requests only | Images, CSS and scripts dropped |
| 4 | Match the Google values | Web, Android app and local domains counted |
| 5 | Compare with Search Console, allowing for the known gaps | A difference you can explain |
Time: about an hour. Tools: analytics admin access or raw access logs, and a shell or spreadsheet. Cost: none. Skill level: intermediate.
Step 1: Check Your Analytics Before Touching Logs
Most tools already classify these visits, so check first that yours does. Google says most analytics systems “automatically recognize these Referer values,” and if Google traffic “shows up as referral or direct traffic,” you should check custom channel rules, referral exclusions and filters (Google doc). In Google Analytics 4, the Organic Search channel is defined by the source matching GA4’s list of search sites, or the medium being exactly “organic” (GA4 Help). If you built custom channel groups for AI assistants, as in our GA4 AI referral guide, check that no rule above Organic Search catches Google first.
Step 2: Pull the Referer Field From Your Logs
In the common “combined” log format, the Referer is the quoted field after the response size. A typical line ends 200 5120 "https://www.google.com/" "Mozilla/5.0 ...". Your CDN or host may name it referer, http_referer or cs(Referer).
Step 3: Keep Landing-Page Requests Only
Drop images, stylesheets, scripts and fonts before counting. Google notes that for those resource requests the Referer “is your own page’s URL,” so they are not Search visits (Google doc). Count only requests for HTML pages.
Step 4: Match the Google Values
Match the web value with any Google domain, plus the Android app value. Google lists three cases: Search on the web sends https://www.google.com/ “or a local Google domain”; the Google app on Android sends the android-app:// value when a result opens in a browser tab, otherwise the web value; the Google app on iOS sends the web value (Google doc). Google does not supply a pattern. This is ours:
^(https://www\.google\.(com|co\.[a-z]{2}|com\.[a-z]{2}|[a-z]{2,3})/|android-app://com\.google\.android\.googlequicksearchbox/https/www\.google\.[a-z.]+)$We tested it on November 13, 2026 against all 187 entries on Google’s domain list, and it matched every one (Google supported domains). It rejected www.googleadservices.com, mail.google.com, news.google.com, www.google-analytics.com and a lookalike, www.google.com.evil.example. For raw logs, this command applies the same test and skips common asset types:
grep -E ' "(https://www\.google\.(com|co\.[a-z]{2}|com\.[a-z]{2}|[a-z]{2,3})/|android-app://com\.google\.android\.googlequicksearchbox/https/www\.google\.[a-z.]+)" "' access.log | grep -vE '"GET [^ ]+\.(png|jpe?g|gif|svg|webp|css|js|ico|woff2?) 'On a nine-line test log we wrote, it kept the five Google landing-page visits and dropped an image request, a Google Ads referrer, a Gmail referrer and a blank Referer. News.google.com is excluded on purpose: Google’s page does not list it as a Search value.
Number of domains on google.com/supported_domains, counted November 13, 2026
Source: Google, google.com/supported_domains, fetched November 13, 2026; our classification.
Counts are ours. One country-style domain, google.cat, has three letters, so a pattern limited to two-letter endings misses it.
The chart shows why a google.com-only rule fails: the global domain is one entry in 187.
Step 5: Compare With Search Console
Expect your count to come in below Search Console’s clicks, and know why. Google gives four reasons the numbers “often” differ: privacy settings, extensions and consent choices; your own redirects, which can replace the Referer; different measurement, since Search Console counts a click when a result is selected and analytics counts only after the page loads its tracking code; and paid traffic, which Search Console excludes (Google doc). Browsers also drop the Referer in private modes, in some new-tab openings and when a native search widget hands off to a browser.
One data note for this week: Google’s data anomalies page says a logging error caused “a decrease in impressions on the Generative AI performance report” for November 9 to 11, 2026, and “affects data logging only” (Search Console Help). That report counts impressions, not clicks, as our explainer on what Search Console shows for AI answers set out. If you are reading the core update through Search Console, as in our November 2026 core update guide, leave those three days out of AI-report comparisons.
How to Verify It Worked
Your log count and your analytics Organic Search count for Google should move together week to week. Neither has to match Search Console exactly. A sudden split between them usually points to a new redirect, a consent change or a channel rule.
Common Problems and Fixes
| Problem | Likely cause | Fix |
|---|---|---|
| Google visits show as Direct | Referer stripped by browser, or a client-side redirect | Use server-side redirects that keep the Referer |
| Google visits show as Referral | Custom channel rule or referral exclusion | Reorder or fix the rule |
| Log count far above analytics | Asset requests counted, or tracking blocked | Filter to HTML pages; expect some blocked tracking |
| Only google.com counted | Pattern too narrow | Match all Google domains and the Android value |
| No query data | Origin policy sends host only | Use Search Console’s Performance report |
What Not to Do
Do not count every request with a Google Referer. Consequence: assets inflate the total. Correction: landing pages only.
Do not treat a blank Referer as Direct by intent. Consequence: you undercount search. Correction: report blank Referers as unknown.
Do not use google\. as a loose match. Consequence: Gmail, ad clicks and lookalike domains slip in. Correction: anchor the pattern as above.
Frequently Asked Questions
What Referer does Google Search send?
On the web, https://www.google.com/ or a local Google domain such as https://www.google.co.uk/. The Google app on Android may send android-app://com.google.android.googlequicksearchbox/https/www.google.com. That is what Google documented on November 12, 2026.
Can I see the search query in the Referer?
No. Google Search uses the origin referrer policy, so the header carries only the scheme and host. Queries are in Search Console’s Performance report.
Does Google Discover have its own Referer?
No. Google says Discover traffic uses the same values as the surface where Discover was viewed, such as the Google app or Google Search on the web.
How many Google domains do I need to match?
By our count on November 13, 2026, Google’s supported_domains list has 187 entries. A pattern for google.com plus two- and three-letter country endings, com.xx and co.xx covers all of them.
Why is my Google traffic lower than Search Console clicks?
Google lists privacy settings and ad blockers, redirects that drop the Referer, different measurement methods and paid traffic. Search Console counts the click; analytics counts only after the page loads.
Was Search Console data wrong in November 2026?
Google reported a logging error that lowered impressions in the Generative AI performance report for November 9 to 11, 2026. It says the issue affects data logging only.
Sources and Methodology
This guide is built from Google’s November 12, 2026 help page on identifying Search traffic, the Search Central updates log, Google’s supported_domains list, GA4’s default channel group definitions and the Search Console data anomalies page, read November 13, 2026, plus Search Engine Roundtable’s November 12 report. The match pattern, domain counts and log test are ours. Step order and the “do not” advice are house recommendations, not Google rules. We tested the pattern on a sample log, not on a live site’s traffic.
- platform documentation Google Search Central, Identify Google Search traffic in your web analytics or server logs (last updated November 12, 2026). Referer values, policy, blanks, discrepancies. Read November 13, 2026.
- platform documentation Google Search Central, Documentation updates. Date the page was added. Read November 13, 2026.
- official Google, supported_domains. The 187 domains we counted and tested. Read November 13, 2026.
- platform documentation Google Analytics Help, [GA4] Default channel group. Organic Search, Referral and Direct definitions. Read November 13, 2026.
- platform documentation Search Console Help, Data anomalies in Search Console. November 9 to 11, 2026 logging error. Read November 13, 2026.
- trade press Search Engine Roundtable, New Google Help Doc Explains How To Identifying Traffic From Google Search (November 12, 2026). Read November 13, 2026.