Headless browser
Chrome headless shell
Real browsers driven by scripts. The tooling behind sophisticated automation.
Last updated
At a glance
| Category | Headless browser |
|---|---|
| User agent match | contains "chrome-headless-shell" |
| Executes JavaScript | Yes |
| Respects robots.txt | No |
| Identity verifiable | No, the name is only a claim |
| IVT class | SIVT (sophisticated invalid traffic) |
What Chrome headless shell is
Chrome headless shell is browser automation: a real browser engine driven by a script instead of a person. It executes JavaScript, which makes it the tooling of choice for automation that wants to look human. Honest uses exist, mostly testing and archiving, but on a public content site the honest uses are rare.
Can the name be trusted?
There is no published way to verify Chrome headless shell: the operator provides no IP ranges and no reverse DNS scheme, so the name in the user agent is only a claim. Any script can send it. TrueVisit still names the traffic, and weighs the claim against behavioral signals instead of trusting it.
Should you block it?
Traffic announcing itself as Chrome headless shell is automation that did not even try to hide, and blocking it costs a content site nothing. Keep perspective though: the sophisticated version of this traffic strips the telltale name out. That version is caught behaviorally, not by name, and is a verification problem rather than a blocklist problem.
For enforcement rather than a polite request, the Cloudflare blocking guide generates copy-paste WAF rules from this same signature list, with guardrails that keep verified search engines safe.
How TrueVisit reports it
Visits from Chrome headless shell appear in your bot report under this exact name, never as an anonymous percentage, and every verdict stores the reason it was reached. Because this client executes JavaScript, it can appear through the browser tracker as well as the server-side path, and behavioral signals carry more of the verdict.