Surfaces our work more for you across Google Search and AI answers.
You have two tabs open. Google Analytics says Google sent you one number of visitors last month. Search Console says Google sent you a different number of clicks, and the two aren't close. One of them has to be wrong, so which one do you believe when the marketing invoice is due?
Neither is wrong. They count different things at different moments, and this week Google wrote that down in one place.
Quick read: On November 12, 2026, Google added a page to its Search Central documentation, "Identify Google Search traffic in your web analytics or server logs." It explains that a click from Google Search arrives with an HTTP Referer header containing only the scheme and host, such as
https://www.google.com/or a country domain, with no path and no search query; the Google app on Android can send anandroid-app://value instead. The page lists why the header is sometimes blank (private browsing, anti-fingerprinting, new tabs, privacy extensions) and why analytics totals differ from Search Console: Search Console counts a click when a result is selected, while analytics counts a visit only after the page loads and its tracking code runs; Search Console excludes Google Ads clicks; redirects and stricter referrer policies can strip the header (Google Search Central; documentation changelog). Separately, Google's data anomalies page records a logging error that lowered impressions in the Search Console Generative AI performance report from November 9 to 11, 2026, affecting the report only (Google Search Console Help).
What Google wrote down on November 12
The new page covers one mechanism: the Referer header. (One r. The misspelling is in the original web standard and everyone has been stuck with it since.) When someone clicks a result on Google, their browser sends your server a short note saying where they came from. Google sets that note to the bare domain and nothing else. No path, no query, no hint of what the person typed.
So if you were hoping this page would tell you the search terms behind each visit, it won't, and Google says so on the first screen. The query lives in Search Console's Performance report and nowhere else.
What the page does give you is the list of values to look for. A click from Google Search on the web shows up as https://www.google.com/ or a local domain like google.co.uk. The Google app on iPhone looks the same. The Google app on Android can show up as an android-app:// address when the link opens in a browser tab. Discover traffic arrives looking like whatever surface it was seen on, so it blends into the same bucket, and so does Google Images.
Most analytics tools already sort these values into "organic Google" for you. Google's note is that if your Google traffic is showing up as referral or direct instead, check your own configuration first: custom channel rules, referral exclusions, filters. The signal was there. Something on your end re-sorted it.
Why the two numbers will never match
This is the part nobody tells an owner, so when the numbers disagree it feels like someone made a mistake. Google's page, together with its older guide to using Search Console and Analytics together, lists the reasons. The ones that matter for a small site:
- Different moments. Search Console logs a click the instant someone selects your result. Analytics logs a visit only after your page loads and the script runs. Click and bounce before that, and you're a click in one report and nothing in the other.
- Blockers and consent. Ad blockers, privacy extensions, and a declined cookie banner all stop the analytics script. Search Console counts on Google's side of the click, so it doesn't care.
- Paid clicks. Search Console reports organic only. Your analytics total for Google may include Google Ads traffic.
- Time zone. Search Console runs on Pacific time and you can't change it. Analytics runs on whatever you set. Clicks near midnight land on different dates.
- Redirects. If a click lands on an old address that bounces to a new one, a client-side redirect can replace the Referer with your own page, and the visit loses its Google label.
- Which URL gets credit. Search Console reports on the canonical URL Google chose. Analytics reports on whatever address ran the script. Same page, two names, two rows.
Google's own framing is that small differences are normal and some causes can't be fully debugged. The goal is a reasonable explanation for the gap, not a match to the visit.
Where Google's own AI clicks land
Here's the question I'd expect you to ask next, because it's the one I asked. If someone clicks through from an AI Overview or from AI Mode, where does it show up?
The new page doesn't mention either feature. Google's separate documentation on AI features says those clicks are included in overall search traffic in Search Console, under the "Web" search type, with no separate row. On the analytics side, Semrush's November 12 write-up on measuring AI traffic quality states it plainly: clicks from Google AI Overviews and AI Mode stay in Organic Search, and visits without referrer information can appear as Direct.
So Google's AI surfaces don't get their own line in either report. The referrer is still google.com and the click is still "Web." Google Analytics 4 (GA4) did add an "AI Assistant" channel this year, but that's for chatbots like ChatGPT, Gemini and Claude, which send a referrer of their own, and it only works when a referrer is sent at all. That's the same weakness behind the October week when ChatGPT visits slid into Direct.
The one first-party view of Google's AI surfaces is Search Console's Generative AI performance report. We've written up what that report shows on our own two properties, and the longer story of why those surfaces matter is in our overview of how search and AI answers now fit together.
The same week, the report itself was wrong
Which brings up the second thing that happened this week, and it applies to every number on this page.
Google's data anomalies page now carries an entry for November 9 to 11, 2026: a logging error caused a decrease in impressions on the Generative AI performance report in Search. Google says it affects data logging only. Your pages appeared in AI Overviews and AI Mode as often as they would have; the report undercounted it for three days.
Two details make this easy to misread. The November 2026 core update began on November 10, in the middle of the bug window, so a dip in the AI report lines up with a ranking event that had nothing to do with it. And a similar logging error hit the same report from August 13 to 17, which Google backfilled on August 21. Whether this month's gap gets the same treatment, Google hasn't said.
The report shows an annotation on the affected dates. If you keep a monthly report of your own, copy it over. Future you will not remember which dip was a bug.
A ten-minute check for your own site
You don't need a tool. You need the two tabs you already had open and a willingness to accept a gap.
- In Search Console's Performance report, set the range to last month and note total clicks for the Web search type.
- In GA4, pull sessions for the same month where the source is google and the medium is organic.
- Expect analytics to be lower. A modest gap is blockers, consent, and bounce-before-load. Move on.
- If the gap is large in either direction, check the GA4 time zone, then whether paid traffic is mixed in, then whether the site redirects from an old address.
- If Google traffic sits under Referral or Direct, open the channel rules and referral exclusions before touching the site. The fix is almost always a rule, not a page.
- Open the Generative AI report, confirm the November 9 to 11 annotation, and note it in your records.
Then stop. One monthly look at the pair is enough. I ran a grooming salon for years, and the back-of-house hour was always the one that got skipped, so I'd rather you do this once a month and understand it than daily and dread it.
Reconciliations that make it worse
- Picking whichever number is bigger. Search Console tells you how Google treated your site. Analytics tells you what people did after they arrived. Blending them into one "Google visitors" figure throws away both answers.
- Tightening the referrer policy to "fix privacy." A stricter
Referrer-Policyheader changes what your pages send onward, and Google notes it can remove the header entirely. It won't change what Google sends you, and it can break attribution for every site you link to. - Rewriting pages because the Generative AI report dipped this week. Three undercounted days during a logging error, overlapping a core update, say nothing about the pages.
- Paying for a dashboard that hides the gap. Plenty of tools blend both sources into one smooth line. Smooth is not the same as true. You want to see the seam.
- Chasing the search query through the referrer. It isn't there and hasn't been for years.
The numbers are a clue, and the work is figuring out what produced them. If you'd rather someone read both reports every month, mark the bugs, and tell you in plain English what moved and why, that's what a monthly website care plan is for.
FAQ
What is the Referer header?
A short note the browser sends to your server with each request, naming the page the visitor came from. For clicks from Google Search it contains only the scheme and host, such as https://www.google.com/, with no path and no search query. The one-r spelling is a typo in the original web standard that stuck.
Why does Google Analytics show fewer Google visits than Search Console?
Search Console counts a click when someone selects your result. Analytics counts a visit only after your page loads and the tracking script runs, so ad blockers, declined cookie consent, and people who leave before load all lower the analytics count. Search Console also excludes Google Ads clicks, and the two tools can run on different time zones.
Can I see which search terms brought each visitor from the referrer?
No. Google's referrer carries no query, and the new page says so directly. Search terms are available only in aggregate, in the Search Console Performance report.
Do clicks from AI Overviews and AI Mode show up separately?
Not in either tool. Google reports them under the "Web" search type in Search Console, and they land in Organic Search in GA4 with a google.com referrer. The Search Console Generative AI performance report is the one place that breaks out Google's AI surfaces.
What was the Search Console bug on November 9 to 11, 2026?
Google's data anomalies page says a logging error lowered impressions in the Generative AI performance report for those three days and affected data logging only, so appearances in AI features weren't changed. A similar August error was later backfilled; Google hasn't said whether this one will be.
My Google traffic shows up as Direct in GA4. Is the site broken?
Usually not. Some visits arrive with a blank referrer because of private browsing, privacy extensions, or a result opened in a new tab, and GA4 files those as Direct. If a large share lands there, check channel rules and referral exclusions first, then look for a client-side redirect that overwrites the referrer.
Want a back office for your site?
The build is free on any Care plan with a 12-month minimum. Care starts at $199/mo, and you can switch tiers anytime.
Apply for a build slot →RELATED READS