Search Console Says 600 Clicks. GA4 Says 400 Sessions. Neither Is Broken.

Every few weeks someone shows me two screenshots and asks which one is lying. Search Console reports 600 clicks last month. GA4 reports 400 organic sessions. Same site, same dates, and a 200-visit hole nobody can account for.

Neither is lying. They are not measuring the same thing, they never were, and the gap between them is not an error to eliminate. It is a number with a composition, and once you can name the parts, the gap becomes one of the more useful diagnostics you have.

You are comparing two different events

This is the whole article in one idea: a click and a session are different events, recorded in different places, by parties with different powers.

Look at where each one is counted. Search Console counts on Google's side of the click, before your server is even contacted. GA4 counts inside the visitor's browser, after your page loads and your tag runs. Everything that follows is a consequence of that one architectural difference.

Which direction is the gap leaning?

Before diagnosing anything, note which number is bigger. The direction narrows the cause list immediately, because the two failure modes are mirror images:

When Search Console reports more

The common case, and it has gotten worse. Something stopped GA4 from recording an arrival that genuinely happened:

• Declined consent. Under Consent Mode v2, a visitor who says no produces no session. Search Console counted their click ten seconds earlier and never asked.
• Ad blockers and privacy browsers. The tag never loads. Estimates of blocking rates vary by audience, and technical audiences block hardest, which is why developer-facing sites see the widest gaps.
• The impatient bounce. Click, see a slow page, hit back. The click is logged; the page_view event never fires.
• Broken or missing tags. A template that lost its GA4 snippet produces exactly this pattern, confined to the URLs using that template.

That last one is the reason this direction is worth reading rather than shrugging at. Consent and ad blockers apply evenly across your site. A broken tag does not. If the gap is concentrated on one section, you have found a tagging bug, not a privacy trend.

When GA4 reports more

Less common, and more often mistaken for a mystery. Here one click is being counted more than once, or credited later:

• The 30-minute rule. GA4 closes a session after 30 minutes of inactivity. A reader who opens your guide, makes coffee, and comes back has produced two sessions from one Google click.
• Attribution carryover. GA4's last non-direct model credits a later direct or bookmarked visit back to the original organic click, within a lookback window that runs to six months. Loyal audiences inflate this considerably.
• Organic Search is not Google Search. GA4's Organic Search channel pools Bing, DuckDuckGo, Yahoo, Ecosia and the rest. Search Console reports Google alone, so a site with real Bing traffic will always show this direction.

Check scope before you check causes

Half the dramatic gaps I get asked about are not measurement at all. They are two different questions being compared. Four scope checks, in the order they go wrong:

1. Property coverage. A URL-prefix GSC property for www.example.com against a GA4 property collecting every subdomain is not a comparison. A Domain property covering all variants against the same GA4 scope is.
2. Channel filter. Comparing all GA4 traffic to Search Console clicks is the single most common mistake. Filter GA4 to Organic Search at minimum, and to the google / organic source and medium if you want the closest match.
3. Date range and timezone. Search Console reports in Pacific Time and lags two to three days, so its recent days are incomplete. GA4 uses your property timezone. Compare closed weeks, aligned.
4. Search type. Search Console's default Performance view is Web only. Image, Video, News and Discover clicks live in separate tabs, and they are real arrivals that GA4 counted.

What size of gap is normal

There is no universal figure, but there are useful bands. A 20 to 30 percent difference with Search Console higher is ordinary and worth no investigation at all. Consent Mode v2 enforcement and rising ad blocker adoption have widened this: some sites now report gaps past 50 percent, where Search Console shows roughly double GA4.

Which means the absolute size tells you much less than its stability:

• A steady gap is measurement. Whatever its size, if the ratio holds week to week, both tools are working and the difference is structural.
• A gap that widens suddenly is a change. A new consent banner, a tag deployment, a migration that dropped the snippet from one template.
• A gap that narrows suddenly is also a change, and usually a worse one: Search Console clicks falling while GA4 holds steady means you lost rankings, not tracking.

Track the ratio as its own metric. It is more informative than either number alone, and it costs nothing to compute once you have both properties connected.

Using both instead of reconciling them

The reconciliation project is a trap. These two systems are answering different questions, and the productive move is to ask each one the question it can answer:

That last row is the one nobody has a workflow for, and it is the interesting one.

The third source that explains the other two

Here is the pattern that makes the gap worth caring about. Clicks on a page drop 40 percent. GA4 says the visitors who did arrive engaged normally. So demand held, and behavior held, and something between the two changed.

Search Console cannot tell you what, because it does not read your page. GA4 cannot tell you either, because it only meets people who already arrived. The answer lives in a crawl of the page itself:

• The title or meta description changed, so the same ranking now earns fewer clicks. A CTR collapse at a steady position is the fingerprint.
• The page slowed down after a template change, and the impatient bounces started before the tag fired. Our SERP preview tool shows the listing Google renders, which is the half of the CTR story you cannot see in either dashboard.
• A canonical or noindex shifted, and the page is quietly being consolidated into another. The Page indexing report confirms it.

Three sources, joined on the URL, answer in one step what any of them alone can only gesture at. That join is the entire premise of CrawlRaven: your Search Console and GA4 data synced daily, crawled against the live page, and ranked so the explanation arrives with the alarm.

For the reporting side of the same problem, see connecting Search Console to GA4 for the link itself, and keeping GSC data past 16 months for the history that makes a year-over-year comparison possible in the first place.