Search Console vs GA4: Why the Numbers Differ
What Search Console and GA4 each actually measure, why their numbers never match, and which one to trust for clicks, sessions, queries and revenue.
Search Console and GA4 measure different things: Search Console counts clicks on Google's results the instant they happen, while GA4 counts sessions from visitors whose browser accepted tracking and ran the measurement script. Their numbers will never match exactly, and treating either one as simply "wrong" misreads what each was built to do.
Knowing which one to trust for which question is one piece of the larger SEO reporting process this cluster covers in full.
On this page
What does each tool actually measure?
Search Console measures Google's side of the interaction: how often a page appeared in results, how often it was clicked, and at what average position, all recorded server-side by Google itself before a visitor ever reaches your site [2]. GA4 measures your side: what happened once a browser landed on the page, tracked through a script that has to load and run successfully to count anything at all.
| Question | Search Console | GA4 |
|---|---|---|
| What does it count? | Clicks on a Google result | Sessions after tracking loads |
| Carries the search query? | Yes | No |
| Needs visitor consent to count? | No | Yes, in most configurations |
| History available | Up to 16 months | Aggregated reports: unbounded |
| Shows revenue or leads? | No | Only if goals are configured |
| Source of truth for | Rankings, queries, impressions | On-site behaviour, channels, goals |
Neither column is the "real" number and the other an approximation of it. They are answers to two different questions that happen to get reported side by side because both matter to the same decision.
Think of it as two different vantage points on the same event. Search Console sits on Google's side of the results page and watches what happens before anyone leaves it — an impression, a click, the query behind it. GA4 sits on your side of the visit and watches what happens after someone arrives — a page view, a scroll, a form submission. A single visitor produces one row of data in each system, and the two rows were never going to describe the same thing, because they were recorded by two different observers standing in two different places.
Why do the numbers never actually match?
Because the moment each tool counts is different, and everything that can happen between those two moments widens the gap. Search Console logs the click server-side, before a browser has even started loading your page. GA4 only counts the visit once the page has loaded, a consent banner has been accepted rather than dismissed, an ad blocker has not silently dropped the tracking request, and the measurement script has finished running [1].
Bot traffic adds one more layer. Search Console applies its own filtering to what counts as a genuine click before you ever see the number, and GA4 applies a different filtering process on its side — the two do not use identical definitions of what a "real" visit is, so some of the gap is simply two different bot-filtering methods disagreeing at the margins.
Do consent banners and privacy tools change the gap?
Yes, more than almost anything else in this comparison. Search Console's click count happens entirely on Google's servers, before a consent banner on your own site has even had the chance to render — nothing a visitor does with your cookie prompt affects whether that click gets logged. GA4's session count depends entirely on that same visitor accepting tracking, because the measurement script that creates a GA4 session typically will not run, or will run in a reduced mode, until consent is granted.
That means a site with a strict cookie banner, a low consent-acceptance rate, or a market with unusually cautious visitors will show a wider Search-Console-to-GA4 gap than an otherwise identical site with a looser consent setup — not because its SEO is different, but because a smaller share of its real visitors ever get counted on the GA4 side. If you manage sites across different markets or under different consent regimes, expect the size of the gap itself to vary by market, and do not read that variation as a difference in search performance.
Which one do you trust for which question?
Search Console for anything about visibility before the click: impressions, average position, click-through rate, and — critically — the actual query someone typed. GA4 has no equivalent to that last one; a session it labels "Organic Search" carries a channel and a landing page, never the search term behind it [1].
GA4 takes over for anything about what happened after the click: how long someone stayed, which pages they viewed next, whether they completed a goal you have configured. Neither tool should be asked to answer the other's question, and a report that pulls the wrong one for a given claim is where most "the data doesn't add up" conversations actually start.
A common mistake is quoting a Search Console click count next to a GA4 conversion rate as if the two were drawn from the same population of visitors. They are close, but not identical — some clicks Search Console logged never became a countable GA4 session at all, for every reason covered above, so a conversion rate calculated against the Search Console number will always read slightly lower than one calculated against GA4's own session count. Be explicit in the report about which denominator a rate is using; it is a two-word fix that prevents a real misunderstanding.
How far back can each tool actually see?
Not the same distance, which matters the first time someone asks for a three-year trend. Search Console's Performance report holds a maximum of sixteen months of history, a hard ceiling that applies to every property regardless of size [2].
16 months
GA4 is different, and the difference is easy to get wrong. Its standard, aggregated reports — the ones this whole guide has been describing — are not bound by the property's data retention setting the same way. That setting, configurable up to fourteen months on a standard property, governs the detailed Explorations and funnel reports, not the headline totals you would put in a monthly report [4]. In practice, that means GA4 can show you organic sessions going back further than Search Console can show you the queries behind them — plan to export and archive Search Console data on a schedule if a client ever wants to see further back than sixteen months.
How do you combine the two without doing double the work?
Through GA4's own Search Console link, which surfaces Search Console data — queries, impressions, position — inside a small set of GA4 reports without a manual export step [5]. It is a convenience layer, not a data merge: the two data models stay separate underneath it, and a blended dashboard built in a tool like Looker Studio is still the better option once you need to combine the two into custom charts rather than just view them side by side.
Building that dashboard covers the mechanics in full, including the join fields that make a blend between the two actually reliable rather than approximate.
What about branded search specifically?
This is one place GA4's blind spot really shows. Because GA4 carries no query, it cannot tell you what share of "Organic Search" sessions arrived through your own brand name versus a non-branded query — that split has to be built from Search Console's query data, filtered by a regex for your brand terms.
Share of search is the metric built around exactly that Search Console-only view: how much of your visibility is people already looking for you by name, tracked over time rather than in a single snapshot. It is a question GA4 was never going to be able to answer on its own, however the report is built.
This is also where the two tools' different histories become a practical constraint rather than a trivia point. A brand-tracking trend that needs to reach back further than sixteen months has to be built from exported and archived Search Console data, not pulled live from the tool — one more reason to treat the sixteen-month ceiling as a planning constraint rather than something to discover the day a board asks for a longer view.
So which tool actually wins?
Neither — they were never competing. A monthly report that leans on only one of the two is missing either the query behind the traffic or the behaviour after the click, and either gap will eventually show up as a question a report cannot answer. SEO reporting tools covers where a third tool, a CRM, or a paid dashboard platform fits once this pairing alone stops being enough.
If you only have time to fix one habit after reading this, make it the denominator problem from earlier: state, every time a rate or a percentage appears in a report, which tool's number it is built from. That one sentence does more to prevent a confused follow-up question than any dashboard redesign, and it costs nothing to add.
Questions people also ask
Why does Search Console show more clicks than GA4 sessions?
Search Console logs a click the moment Google records it. GA4 only counts a session once a browser has accepted analytics tracking and the measurement script has run. Ad blockers, rejected consent banners and bot filtering differences all widen that gap.
Which tool should I trust for keyword data?
Search Console, always. GA4 does not carry a search query dimension for organic traffic at all — it tells you a session arrived from Organic Search, not what someone typed to find you.
Which tool should I trust for revenue or lead data?
Neither, on its own. GA4 can show goal completions if you have configured them; actual qualified leads or closed revenue lives in your CRM, matched back to the session that started it.
Can I link Search Console and GA4 together?
Yes, through GA4's own Search Console link, which lets you view Search Console data inside GA4 reports without a manual export. It does not merge the two data models into one number — they stay separate underneath the shared view.
Is a discrepancy between the two tools a sign something is broken?
Not by itself. A stable, moderate gap is normal and expected. A sudden, large change in the size of that gap — not the numbers themselves — is the pattern worth investigating.
How far back can I see data in each tool?
Search Console's Performance report caps out at sixteen months. GA4's standard, aggregated reports are not bound by that limit the way its detailed Explorations are, which follow your property's separate data retention setting.
Sources
- Using Search Console and Google Analytics data for SEO — Google Search Central (checked 23 September 2026)
- Performance report (Search results): Overview and basic setup — Google Search Central (checked 23 September 2026)
- [GA4] Traffic acquisition report — Google Analytics Help (checked 23 September 2026)
- Data retention — Google Analytics Help (checked 23 September 2026)
- Connect Search Console to Google Analytics — Google Analytics Help (checked 23 September 2026)
Let us reconcile these two tools into one report you can trust
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Jeremy ZavaCo-founder
Leads growth and client partnerships.
Works on: CRO, SEO
Reviewed before publishing by Ibrahem Helal, Co-founder.
- SEO reporting: what a good report showsA guide to SEO reporting: what a monthly report must include, which KPIs matter at each stage, and how to tie organic search to real revenue.
- SEO Reporting Tools: What to Actually UseThe real categories of SEO reporting tools, what each one is for, and why most teams need two of them rather than one all-in-one platform.
- How to Build an SEO Dashboard in Looker StudioConnecting Search Console and GA4 in Looker Studio, blending them without breaking the numbers, and why the dashboard is sometimes a few days behind reality.
- Share of Search: What It MeasuresWhat share of search measures, how to calculate it from Google Trends, and why it belongs in a mature SEO report.