Organic traffic dropped in GA4 but Search Console looks fine (or the reverse): how to reconcile them
If GA4 shows organic traffic falling while Google Search Console clicks are flat, the problem is almost always measurement, not rankings: something stopped GA4 from recording or correctly labelling visits that Google still sent you. If it is the other way round (Search Console down, GA4 stable), you usually lost Google visibility while other search engines or other Google surfaces made up the difference, or you are looking at the wrong Search Console property or filter.
The two tools will never show the same number, and that is fine. What matters is whether the gap between them changed. This guide shows you how to compare them properly, which differences are normal, and a step-by-step way to find the cause when the gap suddenly moves.
Why GA4 and Search Console never match
They measure different things:
| Google Search Console | GA4 "Organic Search" | |
|---|---|---|
| What is counted | Clicks on Google search results | Sessions that started on your site and ran the GA4 tag |
| Which search engines | Google only | Google, Bing, Yahoo, DuckDuckGo, Yandex, Baidu and others |
| Needs JavaScript / consent | No, Google counts the click on its side | Yes, the tag must load (and, with Consent Mode, usually needs consent) |
| Time zone | Pacific Time (PT) | Your GA4 property's time zone |
| Freshness | Usually 2–3 days behind; recent days are preliminary | Usually 24–48 hours for standard reports |
| Page attribution | The canonical URL / the final URL after redirects | The page where the session actually started |
| Privacy filtering | Rare (anonymized) queries are left out of the query table | Data thresholds can hide rows in some reports |
Google lists several of these reasons itself in the Search Console help article on troubleshooting data discrepancies: privacy filtering, processing, the 2–3 day lag, Pacific Time, and the fact that tools like Google Analytics only see visitors whose browser runs JavaScript.
There are also behavioural reasons a click does not become a session: the visitor hits "back" before the page (and tag) loads, an ad blocker or privacy browser blocks Google Analytics, or the visitor declines cookies. In the other direction, GA4 can merge two Google clicks into one session if they happen within the same session window.
So a gap is normal. For many sites, GA4 records noticeably fewer Google organic sessions than Search Console reports clicks, especially in regions with strict consent banners. What you are looking for is a gap that suddenly changes size.
Step 1: Compare like with like
Most "they disagree" panics come from comparing different things. Before investigating, line them up:
- In GA4, open Reports → Acquisition → Traffic acquisition, change the primary dimension to Session source / medium and look at google / organic only, not the whole Organic Search channel (which includes Bing and others).
- In Search Console, open Performance → Search results, keep Search type: Web (also check Image and Video if they matter for you), and remove any query or page filters.
- Use whole weeks and the same date range in both. Because of the Pacific Time vs. property time zone difference, single days will never line up, but weekly totals will be close enough.
- Skip the last 3 days. Search Console's most recent days are preliminary and GA4 may still be processing.
- Check you are in the right Search Console property. A URL-prefix property (
https://www.example.com/) does not includeexample.com,http://or other subdomains. If you moved to a new domain or subdomain, the clicks may simply be counted in a different property. A Domain property avoids this.
Step 2: Track the ratio, not the totals
Divide GA4 google / organic sessions by Search Console clicks, week by week, for the last 8–12 weeks.
Example (illustrative numbers): if your ratio has been about 0.8 for months and suddenly falls to 0.5, while Search Console clicks are steady, GA4 lost a large share of Google visitors. Nothing changed in Google; something changed in your measurement or your site.
If the ratio is stable and both lines fall together, the drop is real: go to the traffic drop checklist and investigate rankings.
You can also see both data sets side by side inside GA4. Link the properties under Admin → Product links → Search Console links; GA4 then provides a Search Console report collection (with a Queries report and a Google organic search traffic report) that you may need to publish from the Library before it appears in the navigation. The "Google organic search traffic" report shows Search Console clicks next to GA4 sessions per landing page, which makes the next step much faster.
Step 3: GA4 organic down, Search Console stable
This is a measurement or attribution problem. Check these in order, starting with what changed around the date the ratio moved.
The tag stopped firing on some pages
A new template, page builder, landing-page tool or blog subdomain without the GA4 tag shows up exactly like this: Search Console still counts clicks to those URLs, GA4 sees nothing. Compare landing pages: the pages with Search Console clicks but no GA4 sessions are your suspects. If GA4 is missing data more broadly, work through why GA4 shows no data.
A consent banner was added or changed
If you launched or reconfigured a cookie banner, visitors who decline may no longer be measured (with Consent Mode in basic mode the tag does not load until consent is given). The signature is a drop across every channel, not just organic, starting on the day the banner went live. See Google's Consent Mode overview.
Google visits are being labelled as something else
Sessions are not lost, they moved to another row. Check whether Direct or Referral grew by roughly the amount organic lost. Common causes:
- UTM parameters on internal links. In GA4, clicking an internal link tagged with
utm_sourcestarts attributing the visit to that campaign instead of Google. - Redirect chains that drop the referrer, for example JavaScript or meta-refresh redirects, or links that send visitors from HTTPS to an HTTP page (browsers normally strip the referrer on that downgrade).
- A new consent or cookie tool that loads the tag only after a page reload, so the first page view (which carries the referrer) is never recorded.
Real visitors, but fewer of them reach the tag
A much slower page (for example a heavy new script loaded before GA4) means more visitors leave before the tag fires. Check Core Web Vitals in Search Console and whether GA4 loads early in the page.
Filters or settings changed in GA4
A new internal traffic filter, a changed data filter or a new property used in reports can all remove sessions. Look at Admin → Data collection and modification → Data filters and the property's change history.
Step 4: Search Console down, GA4 organic stable
This direction is less common, and it usually means something real is happening on Google that other sources are hiding.
- Other search engines grew. GA4's Organic Search channel includes Bing, DuckDuckGo, Yahoo and others. If Google fell and Bing rose, the channel total may look flat. Look at google / organic specifically.
- Discover or Google News changed. Search Console reports Discover and Google News in separate reports, not in Search results. Traffic from those surfaces may appear in GA4 under different source / medium labels, so a gain there can mask a loss in web search.
- The property or filter is wrong. A page filter, a query filter or the wrong search type silently changes totals. Remember that the query table hides anonymized queries and shows at most 1,000 rows, so filtered rows rarely add up to the chart total (how Search Console groups data).
- URLs moved. After a migration, canonical changes or new redirects, Search Console credits clicks to the canonical or final URL. If those URLs live in another property (new subdomain, new domain), clicks "disappear" from the old one.
- You are looking at preliminary days. The last 2–3 days in Search Console often fill in later.
If none of these apply and Google clicks really fell, treat it as a visibility drop: check whether impressions fell too (rankings) or only clicks (search features, AI Overviews, snippets), and compare the dates with Google's Search Status Dashboard.
A 15-minute reconciliation routine
| Step | Where | What you are checking |
|---|---|---|
| 1 | GA4 Traffic acquisition, google / organic | Weekly sessions for 8–12 weeks |
| 2 | Search Console Performance, Web | Weekly clicks for the same weeks |
| 3 | Spreadsheet or notes | Ratio GA4 ÷ GSC per week: stable or broken? |
| 4 | GA4 Search Console report | Landing pages with clicks but no sessions |
| 5 | GA4 Traffic acquisition | Did Direct / Referral grow when organic fell? |
| 6 | Your change log | Tag, template, banner, redirect or domain changes on the break date |
Doing this by hand is fine once. Our free GA4 traffic drop checker automates the GA4 side: it compares two periods and tells you which channel, page, country or device explains the change.
FAQ
How big a gap between GA4 and Search Console is normal?
There is no universal number. It depends on your audience's consent rate, ad blocker use, page speed and how much of your traffic comes from other search engines. Measure your own ratio over a few months and treat that as your baseline.
Which one should I trust for SEO?
For Google search performance (impressions, clicks, queries, positions), use Search Console: it is measured on Google's side. For what visitors do after they arrive (engagement, key events, revenue), use GA4. Use the ratio between them to detect tracking problems.
Why doesn't the GA4 "Organic Search" channel equal Search Console clicks even for Google?
Because GA4 counts sessions, only when its tag runs, in your property's time zone, while Search Console counts clicks in Pacific Time whether or not your page ever loaded. Comparing weekly totals of google / organic sessions against Web search clicks is the closest match you can get.
Summary
- A gap between GA4 and Search Console is normal; a change in the gap is the signal.
- GA4 down, Search Console flat: look for missing tags, consent changes, attribution moving to Direct/Referral, or GA4 filters.
- Search Console down, GA4 flat: look at Google vs. other engines, Discover/News, property and filter choice, and URL moves, then treat it as a real visibility drop if needed.
- Compare whole weeks, skip the last 3 days, and track the ratio over time.