Why don't bots show up in my analytics?

What an analytics tag actually measures

Conventional web analytics puts a small JavaScript tag on your page. When a browser loads the page and runs the tag, it reports a session. Pageviews, time on page and bounce rate all depend on that initial event.

This assumes a person using a browser. It worked well for 20 years. As automated traffic grew, it became less representative of the work a site serves, without any corresponding warning in the dashboard.

Two filters, both working as intended

The first filter is technical. Most automated clients fetch HTML without executing JavaScript. The tag never runs, so analytics never counts the request.

The second is deliberate. Analytics products remove known bots from their reports because marketing teams want reader counts. Both filters work as intended. Together, they exclude most of the automated activity you now need to understand.

A clean dashboard is the wrong reassurance

When people hear “bots”, they tend to worry about inflated numbers. For most sites, reader counts are roughly accurate. The missing information is the server workload: a majority of those requests never appear in the report.

That affects decisions about capacity, caching and registration. It also makes it harder to tell whether a traffic spike came from readers or a crawler. You are using only the visible half to make those decisions.

Logs, firewall and edge: what each one can see

Origin logs record every request, including those excluded by analytics, but the path and time do not explain the activity. A firewall checks for malicious requests. Most of the traffic in question is not malicious.

The CDN edge sees automated requests before this filtering. Supertab Connect measures there, so its figures rarely agree with analytics. The reports count different things. The edge report includes the automated traffic you need to examine.

Getting a count that includes what analytics drops

You need the automated share of requests, the operators responsible and the paths they concentrate on. Your analytics dashboard cannot provide those 3 figures. Supertab Connect deploys into your existing CDN without a proxy, a DNS change or an agreement with an AI company. The first report uses your own traffic and arrives within hours.

Compare the edge report with analytics. The difference shows how much of your site's workload you have been managing without visibility.