Local SEO

Why Google Analytics and Search Console Don't Match

You open both reports, and Google's two free tools disagree about how many people found you on Google. Google says that is expected. Here is why, and when a gap means something is broken.

Search Console says a certain number of people clicked through to your site from Google last month. Google Analytics says a different number came from Google search. Both tools are made by Google. Which one is wrong?

Neither one. They count different events at different moments. Google has two pages that explain the gap, and the newer one is dated November 12, 2026.

They are not supposed to match

Google's own words: "Although the total counts don't match exactly, what's important is that the general trends have the same pattern."

If both lines go up in the same months and dip in the same weeks, that is the pattern Google says to look for. If the difference between them is small, Google says "it's not something you need to fix."

It only becomes worth a closer look when the gap is large, or when one line moves and the other does not.

Compare the right two numbers

Start with the right pair. Google says the two that are "the most comparable" are:

  • Clicks in Search Console. Someone clicked your link in a Google result.
  • Sessions in Google Analytics. Someone spent time on your site.

Compare those two, for the same dates, and only for organic Google search traffic.

Why the numbers drift apart

Google's newer page names four common reasons.

1. Privacy settings. Google says browser privacy settings, extensions, ad blockers and consent choices "can block analytics scripts." If a visitor declines tracking or runs an ad blocker, Analytics may never see them. Search Console still counts their click, because the click happened on Google's side.

2. Redirects on your own site. If a page sends visitors on to another address using a script, the trail back to Google can get lost. Google says those redirects "may replace the Referer with your own page's URL." The Referer is the note a browser sends that says where the visitor came from. When it gets replaced, Analytics can lose track of where the visitor came from.

3. Click versus page load. Google says Search Console "records a click when a user selects a link in Google Search," while Analytics records a visit "only after the destination page loads and executes the tracking code." If someone taps your result and leaves before the page finishes loading, Search Console counts a click and Analytics counts nothing. That is more likely on a slow phone connection.

4. Paid ads. Search Console counts only free, organic clicks. Google says it "doesn't include clicks on Google Ads," while Analytics may include paid traffic in its totals, depending on how it is set up.

A few more reasons from Google's older page

Google's earlier page on this, last updated January 7, 2026, adds some more. Three of them matter for small business sites:

  • Time zones. You can set the time zone in Analytics. You cannot in Search Console, which uses Pacific Time. Hawaii does not change its clocks, so a Search Console day ends at 10 PM Hawaii time in winter and 9 PM in summer. Your evening visitors can land on a different day in each tool.
  • Page addresses. Search Console reports only the main version of each page that Google picked. Analytics reports every address that carries the tracking code. So Analytics will usually list more pages.
  • Bots. Google says Analytics "automatically excludes traffic from known bots," while Search Console "doesn't necessarily filter them out."

One more from the same page: "Search Console data can be delayed by a couple of days." If you check on Monday morning and last weekend looks empty, wait before you worry.

Sometimes the browser hides where the visitor came from

When someone clicks your link in Google, the browser sends that Referer note saying the visit came from google.com. That is how Analytics knows to file it under Google search.

Google's newer page says the note is sometimes missing. It lists private browsing, opening a result in a new tab in some browsers, moving from a phone's search widget to a browser, and privacy extensions. Google also warns that search visits can show up under "direct" or "referral" when the settings that sort them are off. More on that below.

The note also never carries the search words. Google is clear: "The Referer header doesn't include the search query that the user entered." To see what people typed to find you, use the Performance report in Search Console.

So which one do you trust?

Google answers this one directly: "The source of truth for Search performance will always be Search Console, while the source of truth for behavior inside your site will be Google Analytics."

So use Search Console to learn how you do on Google, and use Analytics to learn what people do once they arrive.

When a gap is worth fixing

If the two lines move together, leave it alone. If they do not, I check three things first:

  • Is the Analytics tag on every page? Google names a missing tag as one cause of a big gap. A page that was added later and never got the tag is invisible to Analytics.
  • Is Google traffic being filed somewhere else? Google says custom channel rules, referral exclusions and filters in Analytics can push search traffic into "referral" or "direct."
  • Do any of your pages redirect with a script? That can wipe out the source.

If your Search Console line itself is falling, that is a different problem. See what Google says to check first when traffic drops.

How we help

Our SEO Management includes monthly reporting, where somebody reads both tools side by side and tells you whether a gap means anything. If you want a quick outside look at your site first, run it through our free Site Check. It grades SEO, accessibility and performance and lists the fixes that matter most, in about a minute.