What each tool counts
| Item | Search Console | Google Analytics 4 |
|---|---|---|
| Main metric | Clicks on your result in Google Search | Sessions on your site |
| Where it is measured | On Google's side, before the visit | On your site, by a tag in the page |
| Needs JavaScript in the visitor's browser | No | Yes |
| Affected by cookie or consent choices | No | Yes, depending on your consent setup |
| Which search engines | Google only | "Organic Search" channel includes Google, Bing, DuckDuckGo and others |
| Time zone | Pacific Time | The time zone set in your GA4 property |
| Data delay | Usually 2 to 3 days | Most reports within a day |
| History kept | 16 months | Depends on your retention settings and reports |
The 8 reasons the numbers differ
- A click is not a session. Search Console counts each click on your result. GA4 groups activity into sessions. One person can click, leave, and click again.
- GA4 needs its tag to load. If someone clicks and leaves before the page finishes loading, Search Console counts the click and GA4 sees nothing. Google notes that tools like Analytics only track users with JavaScript enabled.
- Consent. If a visitor rejects analytics cookies, GA4 may not record the visit in full, depending on how your consent banner and consent mode are set up. Search Console is not affected.
- Other search engines. GA4's Organic Search channel counts Bing, Yahoo, DuckDuckGo and others. Search Console is Google only. On some sites this makes GA4 higher.
- Time zones. Search Console labels days in Pacific Time. If GA4 uses London or Sydney time, single days will not line up.
- Data delay. Search Console data is usually ready in 2 to 3 days. The last few days always look low.
- Privacy filtering. Search Console hides some rare queries to protect privacy. Totals in the chart include them, but the queries table does not, so table totals can be lower than the chart.
- Files that are not web pages. Search Console counts clicks to PDFs and other files shown in Search. GA4 usually does not track them unless you set it up.
What gap is normal?
There is no fixed "correct" gap, because every site's mix of consent, devices and search engines is different. What matters is that the gap stays steady over time. Work out your normal ratio:
- Pick 3 calm months with no site changes.
- For each month, divide GA4 Organic Search sessions from Google by Search Console clicks.
- That is your baseline ratio. If it was 0.82 in each of those months, 0.82 is normal for you.
If the ratio suddenly moves a lot, something changed in tracking, not in Google.
How to compare like for like (5 steps)
- Same dates, same day boundaries. Use full weeks or months, and ignore the last 3 days.
- Google only in GA4. In Reports > Acquisition > Traffic acquisition, add a filter for session source = google and session medium = organic, instead of the whole Organic Search channel.
- Landing pages, not totals. Compare the top 10 landing pages in GA4 with the top 10 pages in Search Console. A gap on one page points to a problem on that page (for example, a missing tag on one template).
- Link the two. In GA4, open Admin > Product links > Search Console links and link your property. You can then see Search Console data inside GA4's Search Console reports (you may need to publish that report collection in the Library first).
- Look at the trend. Put both weekly series in one chart. If they move together, your data is healthy.
When the gap means a real problem
| What you see | Most likely cause | What to check |
|---|---|---|
| GA4 fell, Search Console flat | Tracking broke | Tag on every template, consent banner change, recent theme or plugin update |
| GA4 fell on one page type only | Tag missing on one template | View source on that page type and look for the GA4 tag |
| Search Console fell, GA4 flat | Wrong Search Console property | Use a Domain property, not one URL-prefix version |
| Both fell by a similar percent | The drop is real | Go to the five Search Console comparisons in the playbook |
| Ratio jumped on one exact day | A site or tracking change | Your change log for that day |
A fictional example
brightsmile-dental.com saw GA4 organic sessions fall 38% in a week. Search Console clicks were down 2%. The ratio of GA4 sessions to Search Console clicks had been steady around 0.8 for months and fell to about 0.5 overnight. The date matched a new cookie banner that blocked all analytics until visitors clicked "Accept". Nothing was wrong with their rankings. They fixed the consent setup, and the ratio returned to normal. (Fictional example to show the method.)
How to use this with an AI assistant
Connect SEOmatic at https://seomatic.ai/mcp and ask: "Run gsc_performance trend for the last 90 days on mysite.com and show weekly Search Console clicks. I will paste my GA4 Google organic sessions for the same weeks; work out the ratio each week and flag any week where it moved more than 15%." SEOmatic reads Search Console, not GA4, so you paste the GA4 numbers.