Join Search Console and GA4 without mixing the numbers
Search Console shows what happened before the visit and GA4 what happened after. They are not meant to match. This playbook explains why they differ, how to join them on a clean landing-page key, and how to watch the ratio between them so a broken tag shows up as a break in the line.
✓ Checked against Google documentation and the workspace · 7 October 2026
Two tools, two questions
Search Console tells you what happened before the visit: how often your pages appeared in Google and how often people clicked. GA4 tells you what happened after: how many sessions started, what visitors did and which key events they completed. The numbers answer different questions and are not meant to match. The task is to join them on a landing page so you can say, for each page, how many clicks became sessions and what those sessions did.
Why the numbers differ
| Difference | Search Console | GA4 |
|---|---|---|
| What is counted | a click that leaves Google Search, Discover or News | a session that started on your site |
| Who is counted | everyone who clicked, with or without scripts | only visitors whose browser runs the tag, which needs JavaScript |
| Privacy | rare queries are not shown | follows your consent and collection settings |
| Timing | usually available after two to three days; daily data use Pacific Time | can be near real time; uses the property’s time zone |
| Scope | Google Search, Discover and News | every traffic source |
Google documents these causes in its page on data discrepancies and defines a click in what are impressions, position and clicks. No source gives a fixed ratio between the two tools, so do not look for one in advance.
Step 1: pair the right property with the right site
A wrong pair produces plausible nonsense, not an error. Choose the GA4 property explicitly when you open a GA4 report. The workspace can match a property to a site by name, but when no property matches it now asks you to select one instead of guessing. If you also want the join inside Google Analytics, you can link the two products in Admin under Product links, Search Console Links; the account must be a verified owner of the Search Console property (connect Search Console to Analytics).
Step 2: join on a clean landing-page key
- Take the page path. Search Console gives a full URL; GA4’s landing page is a path, or a path plus query string in the separate query-string dimension (GA4 Data API schema). Cut the host from the Search Console URL.
- Drop parameters and fragments. Tracking parameters create a different GA4 key for the same page; remove them on both sides.
- Normalise the form. Use one convention for the trailing slash and for letter case, and apply it to both sides.
- Filter GA4 to Google organic. Search Console covers Google only, so compare it with sessions whose default channel group is Organic Search and whose source is google, not with all organic sessions.
Step 3: compare the ratio, not equality
Because the tools count differently, track sessions divided by clicks over time. A stable ratio means both tools agree on the trend; a broken ratio means one of them changed.
| Week | GSC clicks | GA4 Google organic sessions | Ratio |
|---|---|---|---|
| 1 | 3,000 | 2,640 | 88.0 % |
| 2 | 3,100 | 2,700 | 87.1 % |
| 3 | 2,950 | 2,580 | 87.5 % |
| 4 | 3,050 | 2,660 | 87.2 % |
| 5 | 3,020 | 2,650 | 87.7 % |
| 6 | 3,080 | 2,150 | 69.8 % |
The first five weeks average 87.5 percent with a standard deviation of 0.37 points, so anything below about 86.8 percent is outside normal variation. Week six, at 69.8 percent, is far outside it, while clicks barely moved: the likely cause is lost measurement, such as a broken tag, a new consent banner or a redirect that strips the tracking, not a loss of traffic. The numbers here are illustrative; your own ratio will differ.
Step 4: read each page by its mismatch
| Pattern for a page | First thing to check |
|---|---|
| Many clicks, few sessions | is the GA4 tag on the page, does a redirect or consent banner block it, does the page load slowly |
| Sessions fine, clicks falling | rankings and snippets; see the content decay and CTR playbooks |
| Clicks and sessions both fine, no key events | the page’s offer and path to the goal, not search |
| Sessions without clicks | other sources, or a different landing-page key |
Step 5: let the Blended report do the daily work
The Blended report in the workspace puts Search Console clicks and GA4 sessions on one chart by day, week or month and keeps them as separate series. It does not turn sessions into clicks or the reverse. Use it to spot the weeks where the two lines stop moving together, then use the table above to explain why (GA4 in the workspace).
Joining Search Console and GA4, answered
Why are my GA4 sessions lower than Search Console clicks?
The tools count different things, and GA4 misses visitors without scripts or consent; there is no fixed ratio to expect.
Which GA4 filter matches Search Console?
Organic Search with source google, since Search Console covers Google only.
Can I add the numbers together?
No. Clicks and sessions are different units; compare them, do not sum them.
What to read next
Open Google Analytics 4 in the workspace, then build a monitoring routine that includes the ratio check.