Website Visitor Numbers: Why No Two Dashboards Agree

If your website analytics, Google Search Console and your Google Business Profile each report a different number of visitors, one of them must be broken. Nearly every business owner reaches that conclusion the first time they open all three in the same week. It is wrong. Acting on it costs more than most people expect.

Consider a composite case, not any one customer, but a pattern that turns up in support conversations every few months. A hurley maker in Tipperary gets a few minutes on local radio. The following Monday the owner opens three dashboards to see what it did. Site analytics shows a modest bump of a few dozen visitors. Search Console shows several hundred clicks from Google. The Business Profile reports more views than either, plus a run of calls. Three tools, three stories, and a well-meaning relative suggests installing a fourth tracking plugin to settle the argument.

Nothing was broken. Every one of those dashboards was counting something real. They were counting different things, on different clocks, with different blind spots, and once you know which is which, the disagreement stops being alarming and starts being useful.

Myth one: a click from Google and a visit to your site are the same thing

Search Console counts clicks on your listings in Google Search. Your analytics counts visits from everywhere: Google, Facebook, a link in a newsletter, someone typing your address off the side of a van. Different units. A click is an event on Google's results page. Visits happen on your website.

Google says as much about its own products. Its Search Central guide to using Search Console and Google Analytics together states that "although the total counts don't match exactly, what's important is that the general trends have the same pattern." If Google's two flagship measurement tools do not reconcile with each other, there is no reason to expect yours to.

Several mechanics pull the two apart:

One click, several pages. A searcher who clicks once and browses four pages is one click and one session, but four pageviews. Dashboards that headline pageviews make the gap look bigger than it is.
Different addresses for the same page. That same Google guide explains that Search Console reports only on the canonical version of a URL, while Analytics reports whatever URL actually loaded. Same visit, filed under different names.
Files that are not pages. A PDF price list clicked from Google counts as a click in Search Console. No analytics script runs inside a PDF, so the visit never shows up on your side.
Clicks that never become visits. Someone taps your result on a weak signal, the page is slow to arrive, and they go back before the tracking code fires. Google counted the click. Your site recorded nobody.

The eight-hour day

Then there is the clock. Google's Search Console Help says the Performance report "tracks and labels daily data in Pacific Time." Ireland sits eight hours ahead of California for most of the year, and seven for a few weeks around the clock changes, because the US and Europe switch on different Sundays. So Search Console's Monday runs from roughly 8am Monday to 8am Tuesday, Irish time. Your own analytics almost certainly runs on Irish time. Compare a single day across the two and you are comparing two different 24-hour windows.

Add the lag. The same help page says collected data is usually available within two to three days, and the newest figures are flagged as preliminary because they can still change. Check Search Console first thing on Monday to see how the weekend went and you are reading a half-finished picture.

So what does that mean in practice? Compare weeks, not days, and leave the most recent three days out. That single habit removes most of the apparent disagreement before you have to think about anything else.

Myth two: Google Analytics counts everyone who visits

This is the myth that does real damage.

In its standard setup, Google Analytics relies on cookies. Ireland's Data Protection Commission does not hedge on whether those need consent: its FAQ on analytics cookies answers the question with a single word, "Yes." So a compliant Irish website shows a banner, and some share of visitors decline. How large a share varies enormously with banner design and audience, and I would not trust anyone who quotes you one number for it.

What happens to the people who say no? Google's answer is consent mode, which estimates the missing visitors from the behaviour of the ones it can see. Read the eligibility rules in Google's Analytics Help, though. Behavioural modelling only switches on when a property collects at least 1,000 events a day from visitors who declined, for at least seven days, and also has at least 1,000 daily users who accepted, on at least 7 of the previous 28 days. Below that, Google states plainly that "events triggered by users who decline consent aren't reported."

A thousand consenting visitors a day. Very few local businesses come anywhere near it. A hurley maker does not. Neither does a two-partner solicitor's practice or a village pharmacy. For the overwhelming majority of small sites, the visitors who click reject are not estimated or modelled. They are gone.

The week the banner went in

Stack the other gaps on top. Google's own Search Console Help notes that tools such as Google Analytics only track visitors who have JavaScript enabled, and browser privacy features and ad blockers routinely stop analytics scripts loading at all. Every one of those gaps shaves visitors off the same side of the ledger.

It also explains the most common panic call of all. The week a consent banner is deployed to production, Google Analytics traffic appears to fall off a cliff. Nothing about the business changed. The counting did.

The cost of misreading this is specific. You pay for a radio slot, a local paper ad or a sponsored post. Analytics shows a flicker. You decide the campaign failed and do not book the next one, while the enquiries it generated sit in your inbox and your call log. Revenue gone before you even knew it was there, because you trusted the dashboard with the largest blind spot. The legal detail of what a banner must offer is covered in our guide to analytics without cookie consent for Irish businesses, so I will not repeat it here.

Myth three: a bigger number means more customers

The opposite mistake catches people too. Some hosting control panels ship raw hit or visit counters built from server logs. They count every request that reaches the server, and a growing share of those requests are not people.

Imperva, the security firm now part of Thales, reported in its Bad Bot Report 2026 that automated traffic made up more than 53% of all web traffic in 2025, up from 51% the year before, with human activity down to roughly 47%. Treat that as a global average across Imperva's own customer base, not a figure for your site. A small brochure site with modest human traffic can see a far higher proportion of bots; a busy shop with loyal regulars, usually lower. Either way, a counter that does not separate machines from people is largely counting machines.

Google's Search Central guide notes that Google Analytics automatically excludes traffic from known bots, while Search Console "doesn't necessarily filter them out." Different tools, different filters, different totals.

A dashboard that doubles overnight is far more likely to be a crawler than a breakthrough. Verify against something that requires a human being: phone calls, form enquiries, orders. If those did not move, neither did your audience.

This is also where agency monthly reports earn their reputation. A PDF with a big visits figure on the front page is easy to produce and pleasant to read. Whether it counts people is a different question, and most owners never get to ask it, because the report arrives by email and the logins stay with the agency. Owning your own WordPress site means owning the dashboards too.

Myth four: Business Profile views are website visits

Your Google Business Profile has its own performance screen, and it measures something else again. Google's Business Profile Help describes profile views as "the number of unique visitors who viewed your profile," counted once a day per person at most, and only the views of the profile itself rather than every appearance of your business on Google.

A profile view happens on Google. It never touches your website. Someone searches your name, reads your opening hours on the profile, taps Call and books a job. That customer shows up in your profile's view and call figures and nowhere in your website analytics, because they never visited it. The Website clicks figure on the profile counts something narrower still: taps on the link to your site.

For trades, local services and shops, this gap is often the largest of the lot. It does not mean the website is failing. Some of those callers will have read your site days earlier on a different device, and no free tool links those two moments together for you. People frequently act on the profile. The website is often where they made up their mind.

Four dashboards, four different jobs

Dashboard	What it counts	What it cannot see
Google Search Console	Clicks and impressions on your Google Search listings, in Pacific Time days	Visitors from anywhere other than Google Search, and anything they do after the click
Google Analytics (cookie-based)	Visits from people who accepted cookies and loaded the script	Visitors who declined consent on smaller sites, blocked scripts, PDF downloads
Google Business Profile	Unique people viewing your profile each day, plus calls, directions and website taps	Anything that happens on your website
Cookie-free site analytics	Visits to your own pages without needing a consent banner	Search queries typed into Google, ad attribution, one person across several devices

One stream of visitors, measured in several different ways.

What a sensible measurement setup looks like

Before naming any product, it helps to be clear about what a small business actually needs from on-site analytics. I would put it at four things.

It counts the visitors who say no to cookies. If your on-site figures depend on consent, a small site will always undercount, for the reasons in myth two. A tool that needs no cookie consent closes that hole.
It runs on infrastructure you can account for. Visitor data can be personal data under GDPR. You should know where it is stored and who handles it.
You can read it in two minutes. The useful questions are simple. Is traffic up or down on last month? Which pages do people land on, and where did they come from? If answering that needs a training course, the tool is wrong for you.
It sits alongside Search Console, not in place of it. Only Google can tell you what people typed before they clicked. Nothing on your own site can see that.

Web60 is built to that standard. Every site includes privacy-first analytics that does not need cookie consent for analytics tracking, so the visitor who rejects a banner elsewhere is still counted on your own pages. It runs on SmartHost's sovereign Irish cloud, where all data stays in Ireland. And it is part of the €60 a year rather than a bolt-on, which matters because the business owner who builds their own site with the AI builder should not need a second subscription just to find out whether it is working. If you want to see what a site looks like with that already included, you can try the AI builder and see everything a Web60 site comes with before spending anything.

Cookie-free does not mean disclosure-free. You should still describe your analytics in your privacy policy, and it is worth checking with your solicitor on any remaining obligations for your type of business.

What cookie-free analytics cannot do

There is a genuine trade-off, and you should know it before a customer or a consultant points it out. Without a cookie, analytics tools as a class have no reliable way to recognise the same person coming back next week, or switching from phone to laptop. Monthly unique visitors is therefore an estimate, and one customer can be counted twice. Nor will a cookie-free tool tell you which Google Ads click turned into which sale.

That leads to the honest exception. If you spend serious money on Google Ads every month, your site comfortably clears Google's modelling thresholds, and you have someone who will actually maintain a proper consent setup, then Google Analytics linked to your ads account is the better tool for ad attribution, run alongside your site analytics. Because the site is full WordPress, which W3Techs measures at roughly four in ten of all websites, adding it later is a plugin rather than a rebuild. That is a real use case. It is not the hurley maker, and it is not most local businesses.

Counting visitors on your own site, without asking them to accept cookies first.

Reading the numbers without losing your nerve

None of this needs a spreadsheet. It needs a few habits.

Compare trends, not totals. Google itself says the general pattern is what matters. Two lines moving the same way is a healthy website.
Work in weeks, and leave the last three days out. This removes the Pacific Time offset and the two-to-three-day lag in one move.
Give each dashboard one question. Search Console answers how people find you on Google. Site analytics answers what they do once they arrive. The Business Profile answers who rang or asked for directions without visiting at all.
Label your own campaign links. Links in newsletters, social posts and printed QR codes all tend to land in the same vague bucket. Tagging those links with UTM parameters lets your analytics tell them apart.
Verify against the till. Ask new customers how they found you, and write the answer down. It is the one measurement no dashboard can distort.

When the trends genuinely diverge, that is worth investigating. Search Console clicks climbing steadily for a month while your site analytics falls usually points to something that changed on your side: a new banner, a theme swap, tracking missing from a template. That is a conflict to verify, not a reason to install another plugin.

The Number That Matters

Three dashboards disagreeing is the normal state of a healthy website. Each one is accurate about the thing it measures and blind to the things it does not, and the disagreement itself tells you something: how many people find you on Google, how many decide on your site, how many simply pick up the phone.

Once you stop expecting them to agree, they become far more useful. Use Search Console for search, your own analytics for what happens on your pages, your profile for the calls, and your customers for the truth. The next time a campaign runs, you will know which figure to read first, and what it is and is not telling you.

Frequently Asked Questions

Why does Search Console show more clicks than Google Analytics shows visitors?

The two tools count different things. Search Console counts clicks on your listings in Google Search, while Google Analytics counts sessions from visitors who accepted cookies and loaded its tracking script. On a small website, visitors who decline the cookie banner are usually not reported in Google Analytics at all, because the site is below the traffic thresholds Google needs to estimate them. Search Console also uses Pacific Time for its daily figures, so single days rarely line up. Compare weekly trends rather than totals.

Why does my Google Business Profile show more views than my website gets visitors?

A profile view happens on Google Search or Maps, not on your website. Google counts unique people who viewed your profile, at most once a day each, and many of them get what they need, such as your phone number, hours or directions, without ever clicking through. Those customers appear in your profile figures and nowhere in your website analytics. The Website clicks figure on your profile is the number to compare with your site.

Is my website analytics broken if the numbers do not match Google?

Almost certainly not. Google's own documentation says Search Console and Google Analytics totals will not match exactly and that the general trend is what matters. Worry when the trends diverge: if Search Console shows clicks rising steadily for a month while your site analytics shows visits falling, verify that the tracking is still in place on every page and that nothing changed recently, such as a new cookie banner or theme.

Do I need a cookie banner for website analytics in Ireland?

If your analytics uses cookies, yes. The Data Protection Commission states that analytics cookies require consent. Analytics that works without cookies avoids the consent requirement for that tracking, but you should still describe it in your privacy policy, and it is worth checking with your solicitor on any remaining disclosure obligations for your business.

How often should a small business check its website numbers?

Once a month is enough for most local businesses, with a quick weekly glance during a campaign. Compare the same period against the previous month or the same month last year, and leave out the most recent two to three days, because Search Console data is usually still being collected for that long. Pair the numbers with something human, such as asking new customers how they found you.

Website Visitor Numbers: Why Google, Your Analytics and Your Business Profile Never Agree