WordPress traffic numbers you can put in front of a client

Why WordPress traffic numbers never seem to agree

The disagreement is not random. Every measurement method is wrong in its own predictable direction.

Google Analytics is blocked for a meaningful share of visitors. Ad blockers stop the script, and people decline the cookie banner. Those visits are never recorded, so the totals come in low and nobody can tell you by how much.

Server logs and server-side counters have the opposite failing. They count crawlers, uptime monitors, prefetches and automated browsers as if they were people. The totals come in high, and the busiest visitor of the month is often a bot.

So the agency ends up with three tools showing three numbers and a client asking which one is right. Meanwhile the only two questions that client actually cares about, how many people visited this month and where did they come from, go unanswered. Most WordPress dashboards cannot answer either one honestly.

Introducing Traffic Analysis in WPCentrify

Traffic Analysis counts visitors, page views and sessions in the visitor's own browser, on the site itself. There are no cookies and nothing for a visitor to consent to.

It tells you where those visitors came from. It filters out bots and automated traffic, then shows you the totals of what it removed, so you can watch the filter working rather than take it on trust. And it lets you paste in a Google Analytics export and compare the two figures day by day, so every difference has a reason attached to it.

The point of all of this is narrow and deliberate: numbers you can put in front of a client and stand behind.

What you see for every site

• Real visitors, page views and sessions, defined the same way Google Analytics defines them, so the two sets of figures can be compared rather than argued over.
• Where visitors came from: search engines, social networks, email, campaigns and referring sites, with the busiest sources listed.
• Bots and noise filtered out, including crawlers, monitoring tools, prefetches, automated browsers and WPCentrify's own checks.
• Your own team excluded. Add your office or client addresses and their visits stop counting.
• Distinct visitors over any period, so you can answer how many different people came in a month, not just per day.
• Cookie-free and privacy-first. No cookies, no personal data stored, nothing to consent to.
• Works with caching. Visitors on cached pages are counted too, which plain server logs miss.
• Fleet view and client reports, with totals across every site you manage.

The definitions, in plain English

Visitors are the different browsers that loaded a page on a given day. Somebody who comes back tomorrow counts again tomorrow. Page views are pages that actually opened in a real browser. Sessions are visits, and a pause of thirty minutes starts a new one, which is the same rule Google Analytics uses.

Distinct visitors is how many different browsers came across the whole period, each counted once, shown as an estimate. Channels are Direct, Organic search, Organic social, Referral, Email, Paid search, Paid social, Display and Affiliate.

What we leave out, and why we show it

Most analytics tools tell you what they counted. Very few tell you what they threw away.

Bot traffic filtering happens on every site, and the totals of what was excluded are shown alongside the totals of what was kept. If a crawler hammered a site for two days, you can see that it was removed rather than wonder whether a traffic spike was real. The same goes for your own team: once your office addresses are added, your visits stop inflating the client's numbers.

That transparency is the difference between a figure you report and a figure you can defend. We show what we did not count, not only what we did.

Cookie-free WordPress traffic analytics by design

Traffic Analysis is cookie-free website analytics in the literal sense. It sets no cookies, stores no personal data, and needs no consent banner in front of it. That makes it privacy-friendly analytics for WordPress by construction rather than by configuration.

It also means you can track WordPress traffic without a cookie banner standing between a visitor and your client's content, which is worth something on its own for conversion.

Because counting happens in the visitor's browser rather than at the server, it keeps working when a caching plugin or a CDN is serving the page. That is the case where server-side WordPress visitor tracking usually goes quiet.

How it compares with Google Analytics

This is a Google Analytics alternative for WordPress that is designed to sit next to Google Analytics, not to replace it. When the two disagree, the reasons are knowable:

• Our page views are usually a little higher, because ad blockers stop Google Analytics and do not stop us.
• We count a person once per day and forget them overnight, on purpose. Google Analytics keeps a cookie for up to two years. Compare day by day, or use Distinct visitors for a longer view.
• We do not count error pages, feeds or admin screens as content views.
• Google Analytics can take up to forty-eight hours to process. Ours is live.

Paste a Google Analytics export in and you get the comparison day by day, which turns an awkward client conversation into a short one.

Built for agencies managing many sites

Traffic Analysis was built for people who manage multiple WordPress sites, not one. A single site can be handled by almost anything. Thirty sites, each with its own client asking the same two questions every month, cannot.

So traffic sits inside the same WordPress agency dashboard as everything else you run, with a fleet view for totals across every site. And it feeds straight into client reporting for WordPress agencies, alongside uptime monitoring and the rest of the month's work, in the client reports your clients already receive. Website traffic sources arrive in the report as a section a client can read, not a screenshot of somebody else's tool.

Getting started

If a site is already connected to WPCentrify, open it and go to the Traffic tab. Data starts collecting from the moment it is switched on.

From there, add your own addresses so your team's visits stop counting, and paste in a Google Analytics export if you want the two compared. The full feature details are on the traffic analytics page, and every capability sits on every plan, which you can check on pricing or across all features.