# Why Search Console clicks and Plausible visits never match, and when to worry

> A gap between Google Search Console clicks and Plausible visits is normal. A gap that changes is not. How to tell the two apart in five minutes.

Source: https://rankpane.com/blog/search-console-clicks-vs-plausible-visits
Published by RankPane · 2026-11-07

**In short:** Search Console counts clicks on Google's results page; Plausible counts visits when your page loads and its script runs, so Plausible is usually lower. The gap itself is normal. Watch the ratio of Plausible visits from Google to Search Console clicks instead: if it moves more than 15% between two equal periods, one side changed how it counts, and you should check tracking before touching content.

Open Google Search Console and Plausible side by side and the numbers almost never agree. Search Console says your site earned 1,240 clicks from Google last week. Plausible says 930 visits came from Google. Neither tool is broken, and chasing the gap itself is usually a waste of time.

What matters is whether the gap **changes**. This guide explains where the difference comes from, how to measure it with one number, and what to check when that number moves.

## Why the numbers differ

Search Console and Plausible measure two different events at two different points.

- **Search Console counts clicks on Google's side.** A click is recorded when someone clicks your result on a Google search page. Google does not know or care whether your page finished loading.
- **Plausible counts visits on your side.** A visit is recorded when your page loads, the Plausible script runs, and it can send an event back to your Plausible instance.

Everything that happens between those two moments can make the numbers drift apart:

- **Blocked scripts.** Some ad blockers and privacy browsers block analytics scripts, including Plausible. The click happened; the visit was never recorded. Serving the script from your own domain (Plausible calls this proxying) reduces this.
- **Bounces before load.** A visitor who clicks and then hits back before the page loads is a click with no visit.
- **Lost referrers.** Redirect chains, some in-app browsers and strict referrer policies can strip the information that the visit came from Google. Plausible then files it under Direct / None.
- **Different units.** Search Console counts clicks per search result. Plausible groups pageviews into visits that end after 30 minutes of inactivity. One person who clicks your result twice in ten minutes is two clicks and one visit.
- **Different scopes.** Search Console's default Performance report covers web search. Clicks from Google Discover, Google News and image search are reported separately, while Plausible may still attribute those visits to Google.
- **Time zones and delays.** Search Console reports in Pacific Time and its data usually lags by two to three days. Plausible uses your site's time zone and is real-time. Comparing "last 7 days" in both tools at the same moment compares different windows.

None of these are bugs. Together they mean that **sessions ÷ clicks is usually below 1.0**, and it varies by site, audience and tech stack.

## The one number to watch

Instead of comparing raw totals, divide one by the other:

> **Ratio = Plausible visits from Google ÷ Search Console clicks**, for the same date range.

For a given site, that ratio is remarkably stable from one period to the next. Your audience's share of ad blockers, your redirect setup and your page speed do not change much week to week. So when the ratio moves, it is telling you that **one side changed how it counts**.

| Period | GSC clicks | Plausible visits from Google | Ratio |
| --- | ---: | ---: | ---: |
| Previous 28 days | 11,240 | 10,450 | 0.93 |
| Last 28 days | 12,490 | 9,370 | 0.75 |

*Example figures for illustration.*

Clicks went **up** by about 11%. Visits went **down** by about 10%. The ratio dropped from 0.93 to 0.75, a change of almost 20%. If you only looked at Plausible, you would conclude that SEO is failing. Search Console shows that demand from Google actually grew. Something between the search result and the Plausible script is losing visits.

A practical threshold: **treat a ratio change of more than 15% between two equal periods as a signal worth investigating.** Smaller wobbles are normal noise.

## How to calculate it by hand

1. Pick a date range that ends **at least three days ago**, so Search Console's data is complete. Use the same range in both tools.
2. In Search Console, open **Performance → Search results** and note **Total clicks**.
3. In Plausible, set the same range, open the **Top Sources** panel and note the visits for **Google**. (Click it to filter the whole dashboard to Google traffic.)
4. Divide visits by clicks. Repeat for the previous period of the same length.
5. Compare the two ratios.

Do the same with **Bing Webmaster Tools** clicks and Plausible's **Bing** visits. Having a second engine is useful: if the Google ratio drops but the Bing ratio holds, the problem is probably specific to how Google traffic reaches you. If both ratios drop together, the problem is almost certainly on your site.

## What to check when the ratio drifts

Start with whatever changed on your site around the time the ratio moved.

1. **The tracking snippet.** Did a theme update, a new template or a CMS migration remove or break the Plausible script on some pages? View the source of a few top landing pages and confirm the script is present.
2. **Consent banners.** A new cookie banner that delays or blocks scripts until the visitor clicks can cut recorded visits sharply, even though Plausible does not need consent in most setups.
3. **Redirects.** New redirects, especially through another domain, can drop the referrer. Visits then show up as Direct / None instead of Google.
4. **New pages without the script.** Landing pages built outside your main template (docs, tools, campaign pages) are often missing analytics.
5. **Script blocking.** If you serve the Plausible script from a third-party domain, consider proxying it through your own domain.

Then narrow it down to pages. Compare Search Console clicks and Plausible entry-page visits **per landing page**. A page with healthy clicks but very few visits is where to look first. A page-level gap is much easier to debug than a site-wide one.

## When the ratio holds but traffic falls

If both tools fall together and the ratio stays steady, the measurement is fine and the change is real. That is when it makes sense to dig into rankings ([here is the full diagnosis](https://rankpane.com/blog/ranking-drop-or-broken-tracking)): which queries lost position, whether only Google or also Bing dropped, and whether the loss is in brand or non-brand searches. The next step is a structured weekly review, covered in [A 15-minute weekly SEO review with GSC, Bing Webmaster Tools and Plausible](https://rankpane.com/blog/weekly-seo-review-gsc-bing-plausible).

## Summary

- Search Console clicks and Plausible visits measure different things. A gap is normal.
- Track **visits ÷ clicks** per engine, not the raw gap.
- A change of **more than 15%** between two equal periods means one side changed how it counts.
- Check the snippet, consent banner, redirects and new templates before changing any content.
- If the ratio holds, the traffic change is real, and it is time to look at rankings.

## Sources
- [What are impressions, position, and clicks? (Search Console Help)](https://support.google.com/webmasters/answer/7042828)
- [Performance report (Search results): Overview (Search Console Help)](https://support.google.com/webmasters/answer/7576553)
- [A deep dive into Search Console performance data filtering and limits (Google Search Central Blog)](https://developers.google.com/search/blog/2022/10/performance-data-deep-dive)
- [Traffic sources, referrers and UTM campaigns (Plausible docs)](https://plausible.io/docs/top-referrers)
- [Bypass adblockers with a proxy (Plausible docs)](https://plausible.io/docs/proxy/introduction)