EngineeringEngineering note

Three-Quarters of Our 'Visitors' Were Three Old Versions of Chrome

Modern bots run a real browser, scroll, wait and pass every engagement test. What they rarely do is update. Desktop Chrome updates itself every four weeks, so a large crowd of desktop visitors stuck on old versions is a fingerprint.

Author

DueClix Engineering

Published

Reading time

3 min read

We run our own small visitor counter next to Google Analytics, because most of what Google Analytics showed for dueclix.com was bot traffic. The counter only counts a visitor as real if the page stays visible for 10 seconds, or the visitor scrolls, clicks or types.

On 12 November it reported real visitors up 630% and an overall verdict of "Improving". Nothing we had done that week explained it. Before celebrating, we opened the server's access log.

What the log showed

Every page view sends a small beacon to the counter, and the server logs the browser that sent it. Grouping the beacons by browser and version made the problem obvious:

Counter beacons by browser, dueclix.com, 11-17 November 2026 (10,635 in total)
BrowserBeaconsShare
Chrome 154, Windows4,80745%
Chrome 152, Linux3,10229%
Chrome 151, Windows2903%
Chrome 157, Windows (current)6987%
Everything else1,73816%

Three versions that were months out of date sent 77% of all beacons. An earlier check of 8-12 November showed the Chrome 154 traffic coming from about 22,000 different IP addresses, the pattern of a residential proxy network, and the Chrome 152 traffic from cloud servers. The same browsers were also probing for pages that do not exist on our site.

These were not crude bots. They ran JavaScript, landed on our directory, moved through category pages and stayed long enough to pass the engagement test. Blocking by IP would never have worked with that many addresses.

The rule we added

Desktop Chrome updates itself roughly every four weeks, and almost nobody stays far behind. So the counter now ignores a beacon from desktop Chrome more than two releases behind the current one. The current version is worked out from the release cadence, so the rule needs no upkeep.

// Desktop Chrome more than two releases behind today's is treated as a bot.
$chromeNow = 157 + intdiv(max(0, time() - 1794441600), 28 * 86400); // 157 on 12 Nov 2026
if (!preg_match('/Mobile|Android|iPhone|iPad/i', $ua)
    && preg_match('#Chrome/(\d+)\.#', $ua, $m)
    && (int) $m[1] < $chromeNow - 2) {
    exit; // not counted
}

Phones are left alone. Mobile updates lag, especially on Android, and real visitors on older phones are common. The rule also only affects our own counter. Nobody is blocked from reading the site.

What changed

On 12 November, 1,254 counter beacons came from our directory's main page. Since the rule went live, the ones that still pass are 10 to 51 a day. Our counter's "real visitors" for the week fell from 1,700 to 604, and that lower number is the honest one. Visitors arriving from Google, other search engines, AI assistants and other websites rose from 21 to 49 in the same week, which is the trend that actually matters.

Check your own analytics in five minutes

  1. Find a report that lists browser versions. Most hosting panels include log statistics (AWStats in cPanel, for example) with a browser-version table. A raw access log works too: the user agent is the last field on each line.
  2. Look at the top rows for desktop Chrome. On a normal site the current and previous versions lead. A version several releases old near the top is a warning sign.
  3. Compare with Direct traffic in your analytics. If Direct jumped on the same days the old versions did, they are probably the same visitors.
  4. Count the addresses. Thousands of IPs sharing one old browser string, in one day, is not a crowd of real people.
  5. Decide what to do with it. For reporting, exclude it. For a site under load, a firewall rule on the same pattern is an option, but test it against real visitors first.

If your traffic numbers do not match your enquiries, tell us what you are seeing. We will check whether the visitors are real before anyone changes the site.

Written by

DueClix EngineeringEngineering team

The team that designs and builds DueClix systems. We write about the parts of the work that are worth writing down.

Have a process worth improving?

Let's build the system behind it. Tell us what the process is and where it breaks — the first conversation is about constraints, not technology.