A WordPress statistics plugin that counts from the server log
A WordPress statistics plugin should tell you three things: how many real people came, where they came from, and which pages they read. Pagereckon answers those questions from the access log your server already writes, so it needs no cookies and no tracking script.
This guide explains what good statistics look like, why two plugins can show very different numbers for the same site, and what the free version of Pagereckon shows.
What a WordPress statistics plugin should show
Most site owners open their stats for a few quick answers. Did yesterday look normal? Which post is taking off? Did that newsletter send anyone? So the basics matter more than a hundred charts.
- Visitors and page views that leave bots out, so the trend means something.
- Top pages for today, the last 7 days and the last 30 days.
- Sources such as Google, Bing, social networks, newsletters, AI assistants and direct visits.
- Countries, devices and browser language, so you know who reads you.
- A live view, for the moment a post gets shared.
- Bots on their own list, because a crawler is not a reader.
Also, a good plugin should stay light. It should not slow pages down, and it should not need a cookie banner just to count visits.
JavaScript counters vs the server log
There are two ways a statistics plugin can count a visit. The first way adds a small script to every page. When the page loads in a browser, the script sends a hit to WordPress or to an outside service. The second way reads the access log, where the web server writes one line for every request.
| JavaScript counter | Server log (Pagereckon) | |
|---|---|---|
| What it sees | Browsers that run the script | Every request the server answers |
| Ad blockers | Can block the script | Cannot hide a log line |
| Bots | Mostly invisible | Visible, sorted by type |
| Cookies | Depends on the plugin | None |
| Setup | Install and go | Pick your log once |
Each line in a standard log holds the address, the time, the page, the status code, the referrer and the user agent. The Apache log docs list those fields. Because the server writes the line before any script runs, a blocker in the browser cannot remove it.
However, a script has one real advantage: it knows the visitor ran a browser. Pagereckon closes that gap with a 42-byte beacon image, loaded once per session. A request that never loads it gets a closer look.
Why bots inflate or hide your statistics
Bots break statistics in two opposite ways. A log tool that counts every line will inflate your numbers, because crawlers, scanners and scrapers often make more requests than people. On the other hand, a script counter hides bots almost completely, so you never learn that GPTBot read 400 pages last week.
Pagereckon sorts every request before it counts it. Known bots are matched by user agent. Scanners give themselves away by the paths they probe, such as old admin pages or leaked config files. Disguised bots show up by behavior, for example bursts of requests, HEAD requests, or pages opened without CSS or images. Only requests that pass all of that count as people.
What the free Pagereckon statistics plugin shows
The free plugin covers the daily questions without a Pro license. Everything below runs on your own server.
- Humans vs bots, with every bot named and grouped.
- Pages, sources, countries and cities, with a city map from the free DB-IP Lite database.
- Devices and browser language.
- Live view for the last 5 and 30 minutes, read from the end of the log.
- AI crawlers per page, split into training, AI search and live reads. See the AI crawler checker guide.
- AI referral visits from ChatGPT, Perplexity, Gemini, Copilot and Claude.
- Page panel in the admin bar with the last 24 hours of each page.
- Google watch, which shows whether Googlebot crawled a page after you edited it.
- Affiliate clicks on /go/ links, Pretty Links and ThirstyAffiliates.
Then, when you want Search Console data and a list of pages worth fixing, the optional Pro add-on builds on the same data. See pricing for the plans.
How to pick the best WordPress statistics plugin for you
There is no single best choice for every site. Instead, ask what you need to trust. If you mostly care about marketing events, a script plugin may fit better. For example, a script can track button clicks inside a page, and a log cannot see that.
Several good script-based plugins exist, and we compare them fairly. Read Pagereckon vs Independent Analytics, vs Burst Statistics, vs Koko Analytics and vs Site Kit before you decide.
But if you want honest visitor counts, bots on their own list and no cookie banner, a log-based WordPress statistics plugin is the stronger base. Pagereckon reads cPanel, Plesk, CWP, DirectAdmin, Apache, Nginx and LiteSpeed logs. When a host hides the log, it can write its own request log from PHP instead. That fallback is less complete, since pages served from a page cache never reach PHP, and the settings page says so.
WordPress statistics plugin questions
Is there a free WordPress statistics plugin without cookies?
Yes. The free Pagereckon plugin sets no cookies and stores no IP addresses. It reads the server log and only loads a 42-byte image once per session.
Will a log-based WordPress statistics plugin slow my site down?
No. Visitors only load the tiny beacon image. The plugin reads the log in the background every 10 minutes, in small steps, by WP cron or a server cron.
Why are my numbers different from Google Analytics?
Ad blockers hide many script hits but no log lines, so the log count is usually higher. In addition, Pagereckon removes bots that some tools count as people.
What if my host does not give access to the log?
Run the Find my log wizard first, since it checks the usual places. If nothing works, switch on the PHP request log. It misses pages served from a page cache, so treat it as a lower bound.