Why Google Search Console and GA4 Numbers Don’t Match

Search Console clicks and GA4 organic sessions measure different things, collected by different systems, at different moments, under different rules. A Search Console click is recorded by Google when someone clicks a result on a Google search page. A GA4 session is recorded by your site’s tag when a browser loads the page, runs the tag and is allowed to send data. Google’s own troubleshooting page says Search Console data “can differ from the data displayed in other tools (such as Google Analytics) for several reasons” (Search Console data discrepancies). The goal is not to make the numbers match; it is to know why they differ and whether the gap is stable.

The two measurements

Reasons the numbers differ

1. Clicks are not sessions. One person can click a result, leave, and click it again: two clicks, which GA4 may record as one session if the second visit falls within the session timeout. GA4’s default session timeout is 30 minutes of inactivity (how GA4 defines a session). The reverse also happens: one click can start a session that is split into two if the user goes idle and returns.

2. The tag may not run. A click in Search Console happens before your page loads. If the user leaves before the tag fires, blocks scripts, uses a browser that blocks analytics, or declines consent, there is a Search Console click and no GA4 session (or a modeled one, depending on consent settings).

3. Attribution rules. GA4 assigns a session’s source from the referrer and campaign parameters. A Google click can arrive without a referrer, and GA4 then reports it as Direct. Google’s AI Overviews and AI Mode clicks, according to GA4’s channel definitions, are part of Organic Search (GA4 default channel group), while visits from AI assistants such as ChatGPT have a channel of their own.

4. Scope. Search Console counts only Google Search. GA4 “Organic Search” includes other search engines (Bing, DuckDuckGo and others). Filter GA4 to google / organic before comparing. Search Console also reports Discover in its own report, outside the web search figures, so a site with Discover traffic should check where those visits land in GA4 before comparing totals.

5. Time zones. Search Console reports in Pacific Time. A GA4 property in another time zone splits days differently, so daily figures do not line up even when totals over a month are close.

6. Privacy and thresholds. Search Console’s query tables omit anonymized queries but include them in chart totals; GA4 can apply data thresholds to reports with demographic or signals data.

7. Landing page versus canonical. Search Console attributes clicks to the canonical URL Google selected. GA4 records the URL the browser loaded, including parameters. A click on a canonical URL that redirects or carries parameters may land on a different page path in GA4.

8. Processing differences. Google’s troubleshooting page notes that processing of source data, for example to eliminate duplicates, can cause differences from other sources.

A worked reconciliation example

Imagine a month in which Search Console reports 10,000 clicks for a site, and GA4 reports 7,800 organic sessions from google / organic. The analyst estimates each reason in turn, using the site’s own data where possible:

The illustrative arithmetic: 10,000 minus 10 percent is 9,000; minus 600 is 8,400; minus 400 is 8,000; minus 200 is 7,800. The steps that cannot be measured directly are labeled as estimates.

The useful conclusion is not the exact breakdown but its stability. If next month Search Console reports 10,200 clicks and GA4 reports 5,100 sessions, the ratio changed sharply, which points to a tracking problem (a tag removed, a consent change, a redirect stripping the referrer) rather than to search performance.

How to compare the two properly

1. Filter GA4 to google / organic.
2. Compare at the landing page level using GA4’s Search Console integration reports, which pair Search Console metrics with landing pages. Google notes Search Console metrics in GA4 are compatible only with Search Console dimensions and the Landing page, Device and Country dimensions (GA4 Search Console integration).
3. Use weekly or monthly totals to reduce time zone effects.
4. Track the ratio over time (GA4 sessions per Search Console click). A stable ratio suggests neither system’s collection has changed; a sudden change points to a change in one of them, to be confirmed against tag, consent and redirect history.
5. Annotate changes to consent banners, tags, redirects and site structure.

Which number to use for what

• Search performance (visibility, CTR, which queries and pages earn clicks): Search Console.
• What visitors did after arriving (engagement, key events, revenue): GA4.
• Trends in organic traffic: either, as long as the same source is used consistently.
• Reporting to stakeholders: label each figure with its source and definition. “10,000 clicks (Search Console)” and “7,800 sessions (GA4)” are both correct.

Warning signs that something is broken

• GA4 organic sessions exceed Search Console clicks by a large margin for Google traffic: possible double-tagging or self-referrals.
• The ratio between the two drops suddenly: consent or tag changes, redirects stripping referrers, a template without the tag.
• GA4 shows organic sessions to pages Search Console never reports clicks for: possible misattribution, or pages reached from other search engines.

When both tools are working and nothing in consent, tagging or redirects has changed, their trends should move in the same direction even when the magnitudes differ. Use each for what it measures, compare them with care, and watch the gap rather than trying to close it.