Search Console vs GA4: Why Clicks and Sessions Differ

The short answer

Google's own Search Console help lists privacy filtering, data processing, time lag, time zones and JavaScript as reasons its numbers differ from tools such as Google Analytics¹. Add cookie consent, other search engines in GA4's Organic Search channel, canonical URLs and session timeouts, and the two will never agree. Compare them by week, by landing page and with GA4 filtered to Google organic, and watch the ratio between them rather than the absolute difference.

What each tool actually counts

Most of the confusion comes from treating a click and a session as the same thing. They are recorded by different systems, at different moments, under different rules.

Aspect	Search Console click	GA4 session
What is counted	A click on a Google Search result that takes the user to a page outside Google Search, Discover or News²	A period of activity on your site, which starts when someone views a page while no session is active⁵
Where it is recorded	On Google's side, before your page loads	In the visitor's browser, by your Analytics tag
Which searches	Google only	The Organic Search channel matches a list of search sites, not only Google⁸
Which URL	Usually the canonical URL Google chose for the page²	The page path and query string of the first page viewed in the session¹⁰
Time zone	Pacific Time, except in the 24-hour view³	The reporting time zone set for your property⁹
Exact or estimated	Counted, with rare queries hidden from tables for privacy⁴	Estimated from the number of unique session IDs⁵

Nine reasons the numbers differ

1. One click is not one session

Search Console counts repeat clicks conservatively: clicking a result, coming back and clicking the same link again "counts as only one click"². Analytics works the other way. A session ends after 30 minutes of inactivity by default⁵, and a new one starts when the visitor next views a page. A buyer who lands on your pricing page, leaves the tab open through a meeting and then opens another page has made one click and two sessions.

2. Analytics only sees browsers that run its tag

Google's Search Console help says plainly that "some tools, such as Google Analytics, track traffic only from users who have enabled JavaScript in their browser"¹. The same applies to anything else that stops your tag loading: a script blocker, a page that errors before the tag runs, or a template that is missing the tag altogether. Search Console has already counted the click by then.

3. Cookie consent removes or models sessions

Most UK sites ask for consent before setting analytics cookies, and what Analytics records then depends on how consent mode is set up. With the basic implementation, Google tags are blocked until the visitor grants consent, so declined visits are missing. With the advanced implementation, tags send cookieless pings when consent is declined, and Analytics can use them for behavioural modelling, if the property is eligible, to fill gaps in the data⁶. Search Console is not affected by your banner at all. A change to your consent banner or its default settings can therefore move GA4 sessions while clicks stay flat: log it in your website change log.

4. GA4 Organic Search is not only Google

In GA4's default channel group, a session counts as Organic Search when its source matches a list of search sites or its medium is exactly "organic"⁸. Search Console only reports Google. To compare like with like, filter GA4 to session source google and session medium organic rather than using the whole channel.

5. Search Console groups data under the canonical URL

Search Console assigns click, impression and position data for all variations of a page to the canonical URL Google selects, "although in some cases data might be assigned to the actual URL"². When a user clicks a duplicate URL, the click counts toward the canonical, not the URL the user visits³. GA4's landing page is whatever path and query string actually loaded¹⁰. Pages reachable with and without a trailing slash, with tracking parameters, or under an old URL that redirects will be split differently in the two tools. The URL Inspection tool shows which canonical Google chose.

6. Some clicks land where there is no tag

A click on a PDF datasheet, a whitepaper or any other file in the search results is a Search Console click, but a PDF cannot run your Analytics tag, so the click does not start a session unless you record file requests some other way, such as on the server. The Pages view in Search Console shows which file URLs receive clicks.

7. The days start at different times

Search Console tracks and labels daily data in Pacific Time, except in the 24-hour view¹³. GA4 records visits in your property's reporting time zone, so a visit made on Tuesday in the visitor's time zone but on Monday in yours is recorded as Monday⁹. For a UK property, a Search Console day starts at about 8am UK time for most of the year (7am for a few weeks in March and around the end of October, when UK and US clocks change on different dates), so single days will not line up. Compare whole weeks: Google's own help notes that aggregating by week or month neutralises the day-of-the-week effect¹¹.

8. Recent data is incomplete in different ways

Google says collected Search Console data is usually available in two to three days¹, and the newest data can be preliminary and change in the next few hours¹². Inside Analytics, the Search Console reports show data 48 hours after Search Console collects it, and cover at most 16 months, because that is all Search Console keeps⁷. Leave the last few days out of any comparison.

9. Each tool hides or removes some data

Search Console hides anonymised queries, those "that aren't issued by more than a few dozen users over a two-to-three month period", from its tables while keeping them in chart totals, and the table shows at most 1,000 rows⁴. So the rows will not add up to the total; our Search Console quick wins guide explains how to work with this. On the Analytics side, traffic from known bots and spiders is excluded automatically, and you cannot see how much was removed¹³. Analytics can also withhold data in a report through data thresholds when user or event counts are low, especially over a narrow date range¹⁴. Any internal traffic filter you have set up removes your own team from GA4 but has no effect on Search Console.

How to compare the two fairly

Link Search Console to Analytics. Once linked, the Google organic search traffic report in Analytics shows Search Console clicks and impressions next to Analytics metrics for each landing page¹⁰. Make sure the two properties cover the same set of pages¹⁰.
Filter GA4 to Google organic. Use session source google and session medium organic, not the whole Organic Search channel.
Use whole weeks. Monday to Sunday in both tools, and leave out the most recent three days.
Compare by landing page, not just in total. A sitewide ratio hides the pages where the gap comes from, such as PDFs or redirected URLs.
Track the ratio over time. Divide GA4 Google organic sessions by Search Console clicks each week. The level matters less than whether it is stable.

An illustrative example: a services page shows 400 Search Console clicks and 300 Google organic sessions a week, a ratio of 0.75, for three months. Then the ratio drops to 0.40 in a single week while clicks stay at 400. Search did not change; something on the site did. Possible causes are a new consent banner, a template release that dropped the tag, or a redirect sending visitors to a page without it.

When the gap is a real problem

Investigate when the ratio moves sharply from one week to the next, or when the gap is concentrated in a few pages. Check, in this order:

Did the consent banner, its default settings or the consent mode implementation change?
Is the Analytics tag present on every template, including landing pages built in a separate tool?
Is the tag installed twice, for example hard-coded and through Tag Manager? Double tagging double-counts events such as key events.
Did URLs change, or were redirects added, so that clicks now land somewhere new?
Are many clicks going to PDFs or other files?
Does Google's list of Search Console data anomalies cover your date range? Our guide to measuring website changes notes one that affected impressions but not clicks.

Which number to use for what

Question	Use	Why
Did a change to a page help it in Google Search?	Search Console clicks and impressions for that page	Counted before the visit, so not affected by consent, tags or timeouts
What do search visitors do on the site?	GA4, filtered to Google organic	Only Analytics sees behaviour after the landing page
Do search visitors become leads?	GA4 key events, checked against the CRM	Key events show on-site actions; the CRM is the record of leads
Is tracking working?	The ratio of GA4 sessions to Search Console clicks	A sudden change in the ratio points to a site or tracking change

For judging SEO changes, our guide to before-and-after SEO testing uses Search Console clicks with control pages. For lead tracking, see GA4 key events for B2B websites.

Where Artiweave fits

Artiweave measures each approved change against one metric chosen in advance, taken from the source that suits the question, which is the discipline this guide recommends. Mixing the two tools in one comparison is exactly how a gap between them gets mistaken for a result.

Frequently asked questions

Why are my GA4 organic sessions lower than Search Console clicks?

Usually because Analytics only records visitors whose browser runs the Analytics tag and, depending on your consent setup, who accept analytics cookies, while Search Console counts the click on Google's side. Clicks to PDFs and pages without the tag usually do not become sessions either.

Why are my GA4 organic sessions higher than Search Console clicks?

The GA4 Organic Search channel includes search sites other than Google, and one click can turn into more than one session, for example when a visitor is inactive for more than 30 minutes and then carries on.

Which number should I report for SEO?

Use Search Console clicks and impressions to judge how a page performs in Google Search, because they are counted before the visit and are not affected by cookie consent. Use GA4 for what visitors do after they arrive, and your CRM for leads.

How big a gap between Search Console and GA4 is normal?

Google does not publish a normal range, and it depends on your consent setup, your audience and your pages. What matters is whether the ratio between the two stays stable over time. A sudden change in the ratio usually means a tracking or site change, not a change in search.

Sources

Measure website changes with the right number for each question.

Artiweave publishes only the changes your team approves, with automatic rollback, and reports each outcome honestly against the metric you chose. It is in private beta.

Join the waitlist