Search Console vs Google Analytics: why the numbers differ

Updated 2026-08-04

The two tools measure different things at different points in the journey. Here is what each one counts and why they will never reconcile.

Search Console clicks and Analytics organic sessions will never match. They are not measuring the same event, and the gap is expected rather than a tracking fault.

What each one measures

Search Console measures activity on Google: a click leaving the results page. It is recorded by Google, before the user reaches you.

Analytics measures activity on your site: a session, recorded by JavaScript after the page loads.

Everything between those two points is where the discrepancy lives.

Why Analytics is usually lower

• The user leaves before the tag fires. Slow page, impatient user — a click with no session.
• Consent and blockers. Declined analytics consent, tracker-blocking browsers and extensions all suppress the session, never the click.
• Redirects that drop the referrer. The session lands in Direct instead of Organic.
• Tag missing on some templates. Common on error pages and legacy sections.

Why Analytics is sometimes higher

• Sessions restart. One click can produce more than one session — the classic case is a session timing out and resuming.
• Non-Google organic. If your Analytics view lumps all search engines together, Bing and others are in there and are not in Search Console at all.

Which to trust

Use each for what it uniquely knows.

• Search Console is the only source of queries, impressions and position. Analytics has never had query data.
• Analytics is the only source of what happened after arrival — engagement, conversions, revenue.

A 10–20% gap is unremarkable. A gap that suddenly widens is worth investigating: that usually means a tagging or consent change, not a traffic change.