Every few months a client sends the same screenshot: Search Console says 900 clicks, Google Analytics says 610 organic sessions. Which one is lying? On November 12, Google finally put the answer in one official page, and it explains more than the gap.
The page is called Identify Google Search traffic in your web analytics or server logs. It’s short: four sections and one table. This guide covers what it says, then turns it into checks you can run on your own setup today, including what it means for tracking AI Mode and AI assistants.
- Google Search sends only the domain as the referrer (for example https://www.google.com/), never the search terms or the result type.
- The Google app on Android can send an android-app:// referrer that some analytics setups misfile.
- Browsers often drop the referrer entirely, so part of your “direct” traffic is really Google.
- Search Console and analytics will never match. Google lists four reasons, and three of them you can partly fix.
- You can’t tell AI Mode or AI Overviews clicks apart from regular results by referrer.
What Google published
When someone clicks a Google result, their browser can send a Referer header telling your site where they came from. Google uses the “origin” referrer policy, which means you get only the scheme and domain. No path, no query string, no search terms.
| Where the click came from | Referer value your site receives |
|---|---|
| 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 link opens in a browser tab, otherwise the web values |
| Google app on iOS | https://www.google.com/ or a local Google domain |
Two practical points. Local domains matter: a site with international traffic will see google.de, google.co.il, google.com.au and dozens more, so filters need to match all of them. And the Android value is the one most likely to be misfiled. If your setup doesn’t treat it as organic search, those visits show up under referral or “unassigned”.
When the referrer disappears
Google sets the policy, but the browser decides what to send. Google lists the usual cases where the header goes missing or can’t be read by JavaScript:
- Private browsing and anti-fingerprinting modes
- Some browsers when a result opens in a new tab
- Moving from a native mobile search widget to an external browser
- Privacy extensions and strict browser settings
Visits without a referrer are usually filed as direct. So if your direct traffic seems oddly high for a site nobody types into a browser, some of it is Google organic you can’t attribute. It’s not a fixable bug. It’s the cost of browsers protecting privacy.
Why analytics never matches Search Console
Google gives four reasons. Here they are, with what you can do about each:
| Reason | What happens | Can you fix it? |
|---|---|---|
| Privacy settings and tools | Ad blockers, consent choices and browser settings stop your tracking script or strip the referrer | Partly. Consent mode and server-side tracking recover some data, within the law |
| Redirects on your site | Client-side redirects replace the referrer with your own URL. Server redirects that drop query strings remove tags like gclid | Yes. Use server-side 301s and keep query strings |
| Different measurement points | Search Console counts the click. Analytics counts the visit only once the page loads and tracking runs | Partly. Faster pages and earlier-loading tags lose fewer visits |
| Paid vs organic | Search Console only reports organic. Analytics totals may include paid, depending on setup | Yes. Compare organic to organic only |
So neither number is lying. Search Console is closer to “how many people clicked us on Google.” Analytics is closer to “how many people actually saw the page.” The gap between them is a measure of how much you lose along the way, and it’s worth watching over time.
Because the referrer contains only the domain, a click from an AI Overview, AI Mode or a regular blue link all look identical: https://www.google.com/. You can’t separate AI-feature clicks from classic clicks in analytics or logs. Search Console’s Generative AI performance report is the only place Google splits them, and only for impressions. We walk through that report in our guide to seeing AI Mode traffic in Search Console.
Check 1: Is GA4 filing Google traffic correctly?
- In GA4, go to Reports, then Acquisition, then Traffic acquisition.
- Change the primary dimension to Session source / medium.
- Search the table for “google”. You want google / organic. Look for anything else: google / referral, a source containing googlequicksearchbox, or Google traffic under (not set).
- If you find misfiled rows, open Admin, then Data display, then Channel groups, and adjust the Organic Search rule so those sources count as organic. Create a custom channel group rather than editing the default, so you keep the original for comparison.
Check 2: Are your redirects eating the referrer?
Every redirect between the Google result and your final page is a chance to lose the referrer or tracking tags. Check your most important landing pages from the command line:
curl -sIL "http://yoursite.com/services/?utm_test=1" | grep -iE "^(HTTP|location)"
You want at most one 301 to the final HTTPS URL, with the query string still attached. Watch for chains like http to https to www to trailing slash, and for any redirect that’s done with JavaScript or a meta refresh instead of a server 301. Those are the ones that can replace the referrer with your own URL.
Check 3: Count Google referrals in your server logs
Logs don’t depend on JavaScript or consent, so they’re the most complete view you have. On an nginx or Apache log in the default combined format:
# Requests with a Google referrer (any country domain, plus the Android app)
grep -cE '"https://www\.google\.[a-z.]+/"|googlequicksearchbox' access.log
# Same, per day
grep -E '"https://www\.google\.[a-z.]+/"|googlequicksearchbox' access.log \
| awk '{print substr($4,2,11)}' | sort | uniq -c
# Top landing pages from Google
grep -E '"https://www\.google\.[a-z.]+/"|googlequicksearchbox' access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20
These count requests, so filter to page URLs if your log also includes images and scripts. On managed WordPress hosts, you’ll usually find raw access logs in the hosting panel.
What different patterns usually mean
| What you see | Likely cause | What to check |
|---|---|---|
| GA4 far below Search Console, logs close to Search Console | Tracking loss: consent banner, ad blockers, slow tag loading | Consent mode setup and when your GA4 tag fires |
| Logs and GA4 both far below Search Console | Referrer stripped before your page loads | Redirect chains and JavaScript redirects |
| Direct traffic rising while organic falls | Referrers being dropped, not lost visitors | Browser mix, new-tab behavior, recent redirect changes |
| Google traffic under referral | Android app referrer or a missing channel rule | Session source / medium in GA4, then channel groups |
| Sudden gap after a site change | New CDN, firewall or redirect rule | Anything deployed around the date the gap started |
Doing the same for AI assistants
The same detective work applies to AI traffic, and it’s slightly easier. ChatGPT adds utm_source=chatgpt.com to its links, so those visits are easy to spot. Other assistants usually send their own domain as the referrer, and the bots that fetch your pages appear in logs under their own user agents, which we cover in how to check which AI crawlers visit your site.
But the same limits apply. Many people who see you in an AI answer search your name later and arrive as Google organic or direct. No referrer will ever show that journey. That’s why a first-party source like ChatGPT Business Hub, which counts mentions and clicks from OpenAI’s side, is a useful companion to your logs. We explain it in our Business Hub guide.
The bigger lesson
Google’s page quietly admits something useful: no single tool sees all of your traffic. Search Console sees clicks, analytics sees loaded pages, logs see raw requests, and none of them sees the person who heard about you in an AI answer and came back a week later.
Use all three, know what each one misses, and watch the gaps between them. A stable gap is normal. A gap that suddenly grows is almost always something you changed.
FAQ
How do I identify Google Search traffic in my analytics?
Look at the HTTP Referer. Clicks from Google Search on the web and iOS send https://www.google.com/ or a local Google domain. Clicks from the Google app on Android can send android-app://com.google.android.googlequicksearchbox/https/www.google.com.
Why does Google Analytics show fewer visits than Search Console?
Google lists four reasons: privacy tools that block tracking, redirects that remove the referrer, different measurement points (a click vs a loaded page), and paid traffic that may be mixed into analytics totals.
Why does some Google traffic show up as direct?
Browsers sometimes drop the referrer, for example in private browsing, when results open in a new tab in some browsers, or with privacy extensions. Visits without a referrer are usually counted as direct.
Can I see which search query someone used to reach my site?
No. Google uses the origin referrer policy, so your site receives only the domain, not the search terms. Query data is available in Search Console.
Can I tell AI Mode clicks apart from regular Google clicks in analytics?
No. They arrive with the same google.com referrer. Search Console’s Generative AI performance report is the only place Google separates AI-feature impressions.
Why is Google traffic showing as referral in GA4?
Usually because of the Android app referrer or a channel rule that doesn’t treat that source as organic. Check Session source / medium, then adjust your channel groups.
Can redirects make me lose Google traffic data?
Yes. Client-side redirects can replace the referrer with your own URL, and server redirects that drop query strings remove tracking tags. Use a single server-side 301 that keeps the query string.
How do I count Google referrals in my server logs?
Search your access log for Google referrer values, for example with grep matching Google domains and googlequicksearchbox, then filter to page requests. Compare the daily count with Search Console clicks for the same day.
Disclosure: information and opinion based on Google’s Search Central documentation published November 12, 2026, plus how we read referrers and logs on client sites and our own. See our full disclaimer.