Analytics
GA4 vs Search Console: Why Clicks and Sessions Never Match
Open Search Console and GA4 side by side for the same month and the numbers will not agree. Search Console shows more clicks than GA4 shows organic sessions from Google, sometimes by a wide margin, and the gap moves from month to month. It is one of the most common questions we get in analytics reviews, and the answer is reassuring: the two tools measure different things, in different places, with different rules. Once you know where the differences come from, you can use each one for what it does best.
What each tool actually counts
Search Console counts what happens on Google’s side. A click is recorded when someone clicks your result on a Google Search results page. Google knows about that click whether or not your page ever loads, and whether or not your site runs any tracking at all. Web search sits in the main Performance report; Discover and Google News have reports of their own.
GA4 counts what happens on your side. A session only exists if your page loads, the Google tag runs, and the visitor’s browser and consent settings allow the data to be sent. GA4 then decides which channel the session belongs to, based on where the visitor came from.
So Search Console measures demand that reached your listing, and GA4 measures visits your site was able to record. They overlap heavily, but they are not the same event.
Reason 1: the tag never gets a chance to fire
Every Search Console click starts a journey, but not every journey ends in a recorded GA4 session:
- The visitor leaves before the tag loads. On a slow page, someone who clicks and immediately presses back is a click in Search Console and nothing in GA4.
- Ad and tracking blockers. Many browser extensions and some browsers block Google Analytics requests outright. The click still counts in Search Console.
- Errors and redirects. A broken page, a redirect chain or a misfiring tag can lose the session entirely.
The faster and more reliable your pages, the smaller this part of the gap.
Reason 2: consent decides what GA4 may record
If you use a cookie banner with Google Consent Mode, visitors who decline analytics cookies do not produce normal GA4 sessions. Depending on your setup, GA4 may fill part of that gap with modelled data, but it will not reproduce every visit. Search Console is unaffected by your banner, because the click happened on Google before your site was involved.
On sites with a lot of European traffic, consent is often the single biggest reason the two tools diverge. If your acceptance rate changes, for example after a redesign of the banner, the gap changes with it.
Reason 3: “organic” means different things
In GA4, the Organic Search channel includes sessions from every search engine GA4 recognises, not only Google: Bing, DuckDuckGo, Ecosia and others. Search Console only knows about Google.
To compare like with like, filter GA4 to session source google and medium organic. Even then, remember that Google Discover and Google News traffic may be classified differently in GA4 from how Search Console reports it.
Reason 4: time zones and dates
Search Console reports days in Pacific Time. GA4 uses the time zone set in your property. For a UK or Greek business that is a difference of eight to ten hours, so a click late in the evening in London can land on one day in Search Console and the next day in GA4. Over a month this mostly evens out; over a single day or a week it can be very visible.
Search Console also keeps 16 months of data. GA4 standard reports go back as far as your property does, but explorations are limited by your data retention setting.
Reason 5: URLs and queries are grouped differently
Search Console reports clicks against the canonical URL Google chose for your page. GA4 records the page as it was actually loaded, including query parameters, tracking codes and whatever URL a redirect ended on. One Search Console page can therefore appear in GA4 as several landing page rows, or under a different path altogether.
Queries differ too. Search Console anonymises rare queries for privacy, so the query table never adds up to the total clicks. GA4, for its part, does not see search queries at all; Google stopped passing them to websites years ago.
Reason 6: one click, different sessions
A single click does not map neatly onto a single session. Someone can click your result, read, leave the tab open for an hour and come back: that is one click but may be two sessions. Someone else can click your result twice in a row: two clicks, but possibly one session. A visitor who arrives from Google and returns later directly may be credited differently depending on the report and the attribution settings you use.
GA4’s session counts are also estimates rather than exact counts, as we explain in why your GA4 session numbers don’t add up.
Which tool to trust for what
Neither tool is “right”. Each answers a different question:
| Question | Use |
|---|---|
| How visible are we in Google, and for which searches? | Search Console |
| Which pages earn clicks, and at what position and click-through rate? | Search Console |
| Did a ranking drop or a technical issue hit Google traffic? | Search Console |
| What did search visitors do on the site? Did they enquire or buy? | GA4 |
| How does organic search compare with ads, email or referrals? | GA4 |
| How engaged are visitors from search? | GA4 (see bounce rate vs engagement rate) |
A healthy reporting set-up uses Search Console for visibility and GA4 for behaviour and results, and does not try to make the two totals agree.
Bring them closer together
You will never close the gap completely, but you can make it smaller and easier to explain:
- Link Search Console to GA4. In GA4, go to Admin → Product links → Search Console links. Once linked, you can publish the Search Console reports in the GA4 report library and see queries and landing pages next to your GA4 data.
- Compare the right slice. Use google / organic in GA4, the same date range, and remember the time zone offset.
- Keep the tag healthy. Load the Google tag early, fix slow pages and broken redirects, and test changes before they reach the live property, ideally in a staging GA4 environment.
- Track the ratio, not the totals. GA4 organic sessions from Google divided by Search Console clicks is a useful health check. If that ratio suddenly falls while clicks hold steady, something changed on your site: a tag, a consent banner, a redirect.
Key takeaways
- Search Console counts clicks on Google; GA4 counts sessions your site managed to record.
- Slow pages, blockers and declined consent all reduce GA4 sessions but never Search Console clicks.
- GA4’s Organic Search includes other search engines; filter to google / organic to compare.
- Different time zones, canonical URLs versus loaded URLs and anonymised queries explain the rest.
- Use Search Console for visibility and GA4 for behaviour and results, and watch the ratio between them.
Keeping these two tools in step is part of our Google Analytics and Tag Manager services. If your search numbers raise more questions than they answer, get in touch.