You install a visitor counter next to Google Analytics, or you compare your counter with your hosting statistics, and the numbers do not match. This is one of the most common questions website owners ask, and the answer is reassuring: analytics tools almost never agree, because each one counts differently. This guide explains the main reasons for the differences, how large a gap is normal and how to find out whether something is actually wrong.
Every tool measures a slightly different thing
A visitor counter, Google Analytics and your server log all observe the same website, but from different places and with different rules. A JavaScript counter records a page view when its code runs in the visitor’s browser. Google Analytics does the same with its own code, then applies its own definitions of sessions, users and engagement. A server log records every request that reaches the server, including images, scripts and visits from software that never runs JavaScript at all.
None of these is the single “true” number. Each is accurate for what it measures. The skill is knowing what each tool includes and leaves out.
The seven most common reasons for differences
1. Different definitions of a visitor
Most tools identify a returning visitor with a cookie, but they differ in how long that identity lasts and how days are combined into weeks and months. One tool may count a person once per month; another may add up daily unique visitors. Both are legitimate, and they produce very different monthly totals. Our guide to sessions, visits and users explains these definitions.
2. Different bot filtering
Search engine crawlers, monitoring services and scrapers visit every public website. Each tool uses its own lists and rules to recognise them. GNRCounter identifies known crawlers by their browser signature (user agent) and records them separately from visitors. Google Analytics uses its own filters, and server logs usually include everything. Automated traffic that pretends to be a normal browser can slip through any of them, but not necessarily in the same way. See our guide to bot traffic for details.
3. Ad blockers and privacy tools
Browser extensions, privacy-focused browsers and some network-level filters block analytics scripts. Popular tools such as Google Analytics are on almost every block list, so they often miss a noticeable share of visitors, especially on technical and gaming sites whose audiences use blockers more often. Smaller counters are blocked less often, but not never. Server logs are not affected by blockers at all.
4. Cookie consent
Where visitors are asked for permission before analytics runs, those who decline are not counted by tools that respect the choice. If one tool waits for consent and another does not, or if they are linked to different consent categories, the totals will diverge, often strongly for visitors from the EEA and the UK.
5. Where the code is installed
This is the most common cause of large gaps. One tool may be installed on every page through a theme, while the other was added to the home page only, or is missing from a blog section, a shop or a landing page builder. Check several page types in a private browser window and confirm that both codes are present on each.
6. Timezones and reporting periods
“Yesterday” in one tool may run from midnight in UTC, and in another from midnight in your local timezone. For a site with a daily rhythm, that shifts a significant part of the traffic into a different day. Make sure both tools use the same timezone before comparing daily figures. In GNRCounter, the timezone is chosen when you create the counter.
7. Your own visits and testing
Many tools let you exclude internal traffic, but the settings are separate in each one. If you exclude yourself in Google Analytics but not in your counter, your own page views appear in only one of them. In GNRCounter, open a tracked page once with ?gnrc-hideme=1 added to the address to exclude your browser, and ?gnrc-hideme=0 to include it again.
How big a difference is normal?
For page views and visitors measured by two JavaScript tools on the same pages, a difference of roughly 10–30% is common. Larger gaps are normal when one tool waits for consent and the other does not, or when your audience uses ad blockers heavily. Server logs often show several times more “visits” than either JavaScript tool because they include bots and every file request.
What matters more than the size of the gap is its stability. If the difference is about 20% every week, both tools are telling the same story. If the gap suddenly changes, something changed in the installation, the filters or the traffic.
A quick diagnostic checklist
- Compare the same period and timezone. Use a full week or month rather than a single day.
- Compare the same metric. Page views with page views, visitors with users, not visitors with sessions.
- Check code coverage. Open the home page, an article, a category page and any special pages; confirm that both tools load on each.
- Check for duplicates. A tool installed twice on the same page doubles its page views.
- Check consent settings. Find out which tools wait for permission and in which regions.
- Compare top pages. If the order of your most viewed pages is similar in both tools, the measurements agree in substance.
- Look at referrers and countries. A sudden, unexplained source or country often points to automated traffic in one tool.
Which number should you trust?
Choose one tool as your primary reference and stay with it. Consistency is more valuable than precision: a stable measurement lets you see whether a change to your site helped, and switching between tools hides real trends behind differences in counting. Use a second tool to cross-check direction, not to reconcile every number.
A visible counter and a full analytics suite can also have different roles. The counter gives you and your visitors simple, readable figures such as today’s visitors and total visitors; a larger suite may be better for detailed conversion tracking. Both can sit on the same page without interfering with each other.
Frequently asked questions
My counter shows more visitors than Google Analytics. Is the counter inflating numbers?
Not usually. Google Analytics is blocked more often and may wait for consent, so it tends to report fewer visitors. Check the diagnostic list above, particularly code coverage and consent.
My hosting panel shows thousands more visits. Which is right?
Hosting statistics come from server logs and include bots, file requests and visits that never run JavaScript. They answer a different question: how much load your server handles.
Can I make the numbers match exactly?
No. Even with identical settings, differences in blocking and bot detection remain. Aim for a stable relationship, not identical figures.
Does a hidden counter count differently from a visible one?
No. The display setting changes only what appears on the page; the tracking is the same.
Next steps
Run through the checklist once, write down the typical gap between your tools and then focus on trends. To understand the terms involved, read unique visitors vs page views; to spot suspicious traffic, read bot traffic explained. If you do not have a counter yet, create one for free.