Dashboard · Detection

Bots & AI agents

Bad bots, good bots, and the one signal that can prove a negative.

How much of your traffic was not produced by a person.

Two kinds#

Bad bots: automation trying to look like a real browser. The navigator.webdriver flag, driver tooling artefacts, non-browser clients sending browser headers.

Good bots: known, self-declaring crawlers such as search engines and link previewers. They are recognised and not counted as suspicious.

Why this signal is different#

Almost every other check records only when it fires, so absence proves nothing. Bots are the exception: every SDK version reads navigator.webdriver, so a visit that read it and fired nothing was measured and clean.

That is why this screen can show a real rate, "x of y measured visits", while Smart Signals usually shows a detected count with no denominator.

Two tabs#

Overview: counts and a series chart, split by kind.

Events: the matching visits. This is Identification with a filter already applied, so every filter there still works.

An honestly self-declaring bot is not a problem to block. Blocking a search engine's crawler is the quickest way to disappear from its results.