Why Search Console clicks don't match GA4 sessions

Search Console clicks and GA4 sessions count different things, so they never match exactly. Search Console counts a click when someone clicks a Google Search result that leads to your site. GA4 counts a session when its tag runs on a page and no session is already active. Google's own guidance names the gaps: the GA4 tag has to load and be allowed by the visitor's consent choice, GA4 drops known bots while Search Console doesn't necessarily, Search Console reports only Google Search and only the canonical URL, Search Console's days run on Pacific Time while GA4 uses the property's time zone, and GA4's Organic Search channel includes every search engine. GA4 also doesn't start a new session when a second click arrives within the same visit. Google's advice is to compare trends rather than totals. For a fair comparison, put Search Console's site total for web search next to GA4 sessions with source google and medium organic, add them up by week, and watch the ratio between them rather than the gap.

What each number counts

Google's Search Central guide on using Search Console and Google Analytics data calls clicks and sessions the most similar metrics the two tools have, and still says the totals won't match exactly; what matters, it says, is that the general trends have the same pattern.

The documented reasons, and which way each one pushes

Most rows push in the same direction: sessions come out lower than clicks, because a click is recorded before the visitor reaches the page and a session only if the page and the tag load and are allowed to run. The one large exception is the channel scope. GA4's default channel group puts a session in Organic Search when its source is any site on Google's list of search engines or its medium is exactly organic, and Google adds that this includes visits from its AI Overviews and AI Mode. Comparing that whole channel with Search Console's Google-only clicks overstates GA4.

Two items on the list are easy to get wrong. GA4 doesn't restart a session when new campaign parameters arrive or at midnight, unlike Universal Analytics, so a visitor who goes back to the results page and clicks your site again within half an hour adds one click and no session. And anonymized queries are not a reason for this gap: Search Console leaves rare queries out of its query table but keeps their clicks in the chart totals, so a site total compared with GA4 already includes them. They only matter if you add up the query table and compare that.

How to compare them fairly

1. Search Console: open Performance → Search results, set Search type to Web and the date range to the last three full months, and read the chart totals rather than summing the query table. Export the daily totals.
2. GA4: open Reports → Acquisition → Traffic acquisition, switch the primary dimension to Session source / medium, filter to google / organic, and use the same date range.
3. Line them up by week. Divide GA4 sessions by Search Console clicks for each week. The level of that ratio tells you little; a break in it tells you a lot. A step down usually lines up with a release: a new consent banner, a template that lost the tag, a migration that changed canonical URLs.
4. Page by page: link Search Console in GA4. Google's linking guide says the link adds a Google Organic Search Traffic report that puts each landing page's Search Console clicks next to its GA4 sessions, that one web data stream links to one Search Console property, and that the Search Console data appears 48 hours after collection and covers the last 16 months.

For row-level reconciliation, Google's own recommendation is to export both to BigQuery — Search Console through its bulk data export, GA4 through its BigQuery export — and join them there.

Side by side in one query

TableBI syncs Search Console and GA4 into one workspace, so the like-for-like comparison is one statement over two tables: search_console_totals_raw holds Search Console's site totals, including the clicks from anonymized queries, and ga4_sources_raw holds GA4 sessions by source and medium. TableBI does not reconcile the two — no tool can — and every answer that uses both carries a caveat saying the numbers are counted differently.

# weekly Search Console clicks next to GA4 google / organic sessions
tablebi ask "WITH g AS (
  SELECT date_trunc('week', date) AS week, SUM(clicks) AS gsc_clicks
  FROM search_console_totals_raw
  WHERE site = 'example.com' AND search_type = 'web' GROUP BY 1),
a AS (
  SELECT date_trunc('week', date) AS week, SUM(sessions) AS ga4_sessions
  FROM ga4_sources_raw
  WHERE property = '123456789' AND source = 'google' AND medium = 'organic' GROUP BY 1)
SELECT g.week, g.gsc_clicks, a.ga4_sessions,
       ROUND(a.ga4_sessions / NULLIF(g.gsc_clicks, 0), 2) AS sessions_per_click
FROM g LEFT JOIN a USING (week) ORDER BY g.week DESC LIMIT 12"

The limit, stated plainly: TableBI's GA4 sync has no landing-page dimension outside AI-assistant referrals, so it compares the two at site level only. For page-level checks, use the report GA4 builds once you link Search Console. To try it without connecting anything, the live demo shows a Search Console dashboard on real data and walks through both connections.

FAQ

Related guides

• How to export more than 1,000 rows from Search Console
• Connect Search Console to Power BI
• Connect GA4 to Claude
• Live demo: a Search Console dashboard on real data

Sources

Each source was read on October 1, 2026.

• Google Search Central — Using Search Console and Google Analytics data for SEO (updated January 7, 2026)
• Search Console Help — Performance report: troubleshooting data discrepancies
• Analytics Help — Default channel group
• Analytics Help — About Analytics sessions
• Analytics Help — Comparing metrics: Google Analytics vs. Universal Analytics
• Analytics Help — Connect Search Console to Google Analytics

npm i -g @tablebi/cli && tablebi install