If you compare your website traffic in SiteGround Site Tools, Google Analytics, and a privacy-focused analytics tool like Microanalytics, you may see very different numbers.
For example, SiteGround might show 59 unique visitors for a day, while Microanalytics shows 2. That looks wrong at first glance, but it usually comes down to one simple point: different analytics tools measure different things.
Hosting statistics are usually based on server logs. Browser-based analytics tools are based on tracking code that loads in a real visitor's browser. Those two approaches can produce very different results.
The short answer
SiteGround and similar hosting dashboards often count traffic from server requests. That can include:
- Real human visitors
- Search engine crawlers
- SEO bots
- Uptime monitors
- Security scanners
- Spam bots
- Image, CSS, JavaScript, or file requests
- Preview tools and link unfurlers
- Repeated visits from the same network or IP address
Microanalytics only counts a visit when the tracking script loads successfully in the visitor's browser on a page where the script is installed.
So the numbers do not always match because the tools are not counting the same underlying activity.
How SiteGround Site Tools usually counts visitors
Hosting dashboards such as SiteGround Site Tools are close to the server. They can see requests made to your website even when those requests are not normal human pageviews.
That visibility is useful for server health, bandwidth, and high-level traffic monitoring. But it can make visitor counts look higher than what a browser-based analytics tool reports.
A hosting log may include requests from:
- Googlebot, Bingbot, and other search crawlers
- AI crawlers and content scrapers
- WordPress bots checking common login or plugin URLs
- Monitoring tools checking whether the site is online
- Security tools scanning for vulnerabilities
- Social media preview bots loading a page to generate a link card
- Visitors who load only an asset, not a full page
Depending on how the hosting provider defines a “unique visitor,” it may also use IP addresses or request patterns. That is not the same as a browser analytics session.
How Google Analytics and Microanalytics count traffic
Google Analytics and Microanalytics are browser-based analytics tools. They generally count a visit when a JavaScript tracking script runs in the browser.
That means a visit may not be counted if:
- JavaScript is disabled
- The tracking script is blocked by a browser extension
- A privacy-focused browser blocks analytics scripts
- An ad blocker blocks the request
- The tracking code is missing from some pages
- A caching or optimization plugin removes or delays the script
- The page does not fully load before the visitor leaves
This is why browser-based analytics often reports lower numbers than raw hosting statistics. In many cases, that lower number is closer to actual human page activity.
Why Microanalytics may show fewer visitors than SiteGround
If SiteGround reports many more visitors than Microanalytics, the most common explanations are:
1. Bot traffic is included in the hosting stats
Server logs see a lot of automated traffic. Some bots are useful, like search engine crawlers. Others are spam, scraping, or vulnerability scans.
A privacy-focused analytics tool will usually ignore much of this because bots often do not execute the tracking script like a real browser visitor.
2. The tracking code is not installed on every page
If Microanalytics is installed only on some pages, it can only count visits to those pages.
This is common on sites using multiple themes, landing page builders, custom templates, or cached static pages.
Check that your tracking code is present on every public page you want to measure.
3. JavaScript or analytics requests are blocked
Some visitors use tools that block analytics scripts. This can affect Google Analytics, Microanalytics, Plausible, Fathom, and most other browser-based analytics platforms.
The exact block rate depends on the audience, browser, device, country, and privacy settings.
4. Caching or optimization plugins interfere with scripts
Performance plugins can combine, defer, delay, or remove scripts. If the analytics script is loaded too late, blocked by consent logic, or omitted from cached pages, visits may not be recorded.
If your analytics numbers look unusually low, test the page source and browser network requests to confirm the script is loading.
5. Different tools define “unique visitor” differently
“Unique visitor” is not a universal metric.
One tool might use cookies. Another might use anonymous browser/session signals. A hosting provider might use IP addresses. Google Analytics may model or process data differently depending on privacy settings and consent mode.
The label can be the same while the calculation is different.
Which number should you trust?
It depends on the question you are trying to answer.
Use hosting statistics when you want to understand:
- Server load
- Bandwidth usage
- Requests hitting your site
- Bot or crawler activity
- Spikes in raw traffic
Use browser-based analytics when you want to understand:
- Human pageviews
- Visitor behavior
- Traffic sources
- Campaign performance
- Popular pages
- Conversions and goals
For marketing and product decisions, browser-based analytics is usually more useful. For infrastructure and security monitoring, hosting logs are useful.
They are complementary, not interchangeable.
What to check if the difference is very large
If your hosting dashboard shows dramatically more visitors than Microanalytics or Google Analytics, run this checklist:
- Open your website in a browser.
- View the page source and search for the analytics tracking code.
- Check multiple page types, not just the homepage.
- Use the browser developer tools network tab to confirm the analytics script loads.
- Disable caching or optimization temporarily and test again.
- Check whether a cookie consent banner is blocking analytics until consent is given.
- Look at server logs for bot-heavy paths such as
/wp-login.php,/xmlrpc.php, or random 404 URLs. - Compare trends over time instead of expecting exact daily matches.
If the tracking code is missing or blocked, browser-based analytics will undercount real users. If the server logs are full of bots, hosting analytics will overcount meaningful visitors.
Example: SiteGround shows 59 visitors, Microanalytics shows 2
A gap like this usually means SiteGround is seeing many raw requests that Microanalytics does not count as tracked browser visits.
That could be because:
- Most of the 59 were bots or crawlers
- The Microanalytics script is installed only on a few pages
- Visitors are hitting files or URLs that do not load the tracking script
- A plugin, cache layer, or browser setting is blocking the analytics script
- SiteGround is using IP/request-based counting while Microanalytics is using browser-based page tracking
The best next step is to verify installation on the actual site pages. If the script is installed correctly and loading, then the difference is likely caused by bot/server-log traffic.
Bottom line
SiteGround, Google Analytics, and Microanalytics can all be working correctly while showing different visitor counts.
The key is to understand what each tool measures:
- SiteGround/Site Tools: server-side requests and unique visitor estimates from hosting logs
- Google Analytics: browser-based analytics with Google’s processing, consent, and filtering rules
- Microanalytics: lightweight browser-based analytics focused on real page activity and privacy
If you want to measure human website behavior, make sure your browser-based analytics script is installed on every important page and loading correctly. If you want to understand raw server activity, use hosting logs alongside your analytics dashboard.
For more background, see our guides on cookieless analytics, IP anonymization in web analytics, and whether Google Analytics is accurate.