Why Don't Search Console and Google Analytics Match?

They measure different events, so they are never supposed to match. Search Console counts clicks on your listing in Google's results; GA4 counts sessions that its tag successfully recorded on your site. A click that never loads the tag exists in one tool and not the other. A gap of roughly 10–20% is normal.

The core distinction

Everything below follows from one thing: the two tools sit on opposite sides of the click.

	Search Console	Google Analytics 4
Measures	Clicks on your result in Google Search	Sessions recorded by the tag on your site
Source of data	Google's own serving logs	JavaScript running in the visitor's browser
Covers	Google only	Every source, including Bing and direct
Blocked by	Nothing the visitor controls	Ad blockers, consent refusals, JS failures
Available	~2–3 days behind	Near real time

Search Console is a pre-click tool. GA4 is a post-click tool. Asking which is correct is like asking whether the ticket barrier count or the seat count is the right measure of a train — they count different moments, and the difference between them is itself information.

The eleven reasons the numbers diverge

Roughly in order of how much damage each one does.

1. The visitor left before the tag fired. Someone clicks, the page starts loading, they hit back. Search Console logged the click. GA4 never ran. Slow pages widen this gap considerably, and on mobile it is larger than most people expect.

2. Ad blockers and privacy browsers. A meaningful share of visitors block Google Analytics entirely. Search Console does not depend on anything running in the browser, so it is unaffected. This alone accounts for a large part of the typical shortfall, and it varies enormously by audience — a developer-focused site loses far more than a local services site.

3. Consent banners. Under GDPR-style consent, GA4 records nothing for visitors who decline until consent is granted. Search Console is unaffected. If you launched a consent banner and organic sessions dropped while Search Console clicks held steady, you have found your answer.

4. Sessions are not clicks. GA4 groups activity into sessions with a 30-minute inactivity window. A visitor who clicks your result, wanders off, and clicks another of your results twenty minutes later generates two clicks and one session. Any site ranking for several related queries sees this constantly.

5. GA4 organic includes other search engines. GA4's Organic Search channel covers Bing, DuckDuckGo, Yahoo and the rest. Search Console covers Google. This one pushes GA4 higher, partly offsetting the others — which is why comparing totals can look deceptively close while both numbers are wrong.

6. Lost referrers become Direct. If the referrer is stripped — some app browsers, some redirect chains, some privacy settings — GA4 has no evidence the visit came from search and files it under Direct. The click is still in Search Console under organic.

7. Time zones. Search Console reports in Pacific Time, always. GA4 reports in whatever time zone the property is configured for. If you are in London, roughly a third of each Search Console "day" belongs to your previous day. On daily comparisons this is a real distortion; on 28-day totals it mostly washes out.

8. Data freshness. Search Console lags two to three days and backfills. Comparing a period that includes the last 72 hours will always show Search Console short. Always compare completed periods.

9. Canonical URLs versus actual URLs. Search Console attributes performance to the canonical URL Google selected. GA4 records the URL the browser actually loaded — including query parameters, tracking tags and variants. One canonical row in Search Console can correspond to a dozen page rows in GA4. See what is a canonical tag.

10. Redirects. If a ranked URL redirects, Search Console credits the URL that appeared in results while GA4 credits the destination that loaded. On a site with legacy 301 redirects, page-level comparisons can look wildly inconsistent while the totals are fine.

11. Both tools withhold data. Search Console filters out rare queries for privacy, so query rows never sum to the reported totals. GA4 applies cardinality limits that bucket low-volume dimension values into (other), and applies sampling in some explorations. Neither tool is showing you a complete table.

How big a gap is normal?

There is no published universal figure, and any site quoting one is guessing — the size depends almost entirely on your audience's blocker and consent behaviour. As a working rule:

Gap (GA4 sessions vs GSC clicks)	Reading
GA4 within about 10–20% below	Normal. Stop investigating.
GA4 20–40% below	Plausible for a technical or privacy-conscious audience; worth confirming tag coverage
GA4 more than 50% below	Something is broken — start the checklist below
GA4 above Search Console clicks	Expected if other search engines send meaningful traffic; suspicious otherwise

The direction matters as much as the size. GA4 sitting below Search Console is the normal state of the world. GA4 sitting far above it, with little Bing traffic to explain it, usually means bot traffic, an internal-traffic filter that is not working, or a misconfigured channel grouping counting paid or referral visits as organic.

A diagnostic checklist for a gap that looks wrong

Work through these in order — the first three resolve most cases.

Compare like periods. Both tools set to the same completed date range, ending at least three days ago. Set the GA4 property time zone to Pacific temporarily if you are chasing a daily discrepancy.
Compare like metrics. Search Console clicks against GA4 sessions where session source/medium is google / organic — not total users, not all organic.
Check tag coverage. Confirm the GA4 tag fires on every template, including any pages served by a different system — a separate blog subdomain, a help centre, a landing page builder.
Check the consent configuration. Look at whether consent mode is set up and what share of visitors decline.
Check the property scope. A domain-level Search Console property includes every subdomain and protocol; a URL-prefix property does not. Your GA4 property may cover a different set of hosts entirely.
Check for a redirect between the ranked URL and the loaded one. Page-level mismatches almost always come from here.
Check internal and bot traffic filters in GA4 if the numbers are too high rather than too low.

Which tool to trust, for what

The useful answer is not "one of them." Use each for the job it can actually do.

Use Search Console for anything before the click: impressions, queries, average position, click-through rate, index coverage. GA4 knows none of this. Query data in particular exists nowhere else — see what is a good click-through rate in Search Console.

Use GA4 for anything after the click: engagement, conversions, revenue, paths through the site, and the behaviour of everything that is not Google. Search Console cannot tell you whether a visit was worth anything.

For ROI, pick one and declare it. Since the calculation needs conversion values, that will normally be GA4. Say so in the report. Switching source mid-year is how a set of numbers stops being comparable — the full method is in how do I measure SEO ROI.

For AI search, expect neither to help much. AI Overview clicks are folded into Search Console's ordinary Web totals with no separate breakout, and assistants like ChatGPT and Perplexity appear in GA4 as ordinary referrals if they appear at all. How to track AI search traffic covers what is actually measurable.

The reconciliation nobody needs

It is worth saying plainly: you do not need these two numbers to agree. Time spent forcing a reconciliation is time not spent on the work that moves either of them.

The gap becomes worth investigating in exactly two situations — when it changes suddenly (something broke, or a banner shipped), and when it is large enough to suggest the tag is missing on part of the site. Otherwise, record roughly what your normal gap is, and move on.

What actually moves both numbers is the same thing: ranking for more queries that matter, which comes down to relevance, content quality and authority. On the authority side, Backlinkster arranges one-for-one in-content link swaps between real site owners and verifies each one live by code. Five swaps a month on the free plan; see the plans.

Frequently asked questions

Why does Search Console show more clicks than Google Analytics shows sessions? Because clicks are logged by Google before your site loads, while sessions require the GA4 tag to run. Visitors who bounce before the page loads, block analytics, or decline consent appear in one tool and not the other.

Is Search Console or Google Analytics more accurate? Neither — they measure different events. Search Console is authoritative for clicks, impressions, queries and position. GA4 is authoritative for what happened on the site afterwards. Use each for its own side of the click.

What is a normal discrepancy between GSC and GA4? GA4 sessions typically run somewhere around 10–20% below Search Console clicks, but the figure depends heavily on how much of your audience blocks analytics or declines consent. Establish your own normal and watch for changes to it.

Why did my GA4 organic traffic drop but Search Console stayed flat? The most common causes are a new or changed consent banner, a broken or missing tag on some templates, or a change to channel grouping that moved sessions into Direct or Referral. Search Console holding steady is evidence the traffic still exists.

Do Search Console and Analytics use the same time zone? No. Search Console always reports in Pacific Time. GA4 uses the time zone set on the property. This shifts daily comparisons and is a common source of apparent mismatches.

Why don't my Search Console query numbers add up to the total? Google filters out rare queries to protect user privacy, so the query table is an incomplete subset by design. The Pages and Queries views are also aggregated differently and will not reconcile with each other.

Should I try to make the two tools match? No. They are counting different things and cannot be reconciled. Note your typical gap, investigate only when it changes suddenly or is extreme, and use each tool for what it measures well.

The bottom line

Search Console and GA4 disagree because one counts clicks in Google's logs and the other counts sessions in your visitors' browsers, and a great many clicks never become sessions. That gap is a fact about the internet, not a fault in your setup. Learn what your normal gap looks like, use Search Console for everything before the click and GA4 for everything after it, and only start digging when the relationship between them changes.