Scraper
WPBot
Bulk content copiers. They take your pages and give nothing back.
Last updated
At a glance
| Category | Scraper |
|---|---|
| User agent match | contains "wpbot" |
| Executes JavaScript | No |
| Respects robots.txt | No |
| Identity verifiable | No, the name is only a claim |
| IVT class | SIVT (sophisticated invalid traffic) |
What WPBot is
WPBot copies content in bulk. Unlike a search crawler it sends no readers back, and unlike an AI assistant it cites nothing: pages go in, nothing comes out. Its visits cost bandwidth and inflate raw traffic numbers while serving no interest of yours.
Can the name be trusted?
There is no published way to verify WPBot: 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?
Block WPBot without hesitation; a declared scraper has no legitimate claim on a content site. Just keep expectations honest: the ones that announce themselves are the polite minority, and the impolite majority fakes a browser name instead. Blocking the declared ones is cheap hygiene, not a security program.
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 WPBot 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 never executes JavaScript, a browser-only tracker cannot see it at all; it is visible through server-side collection, which is how the visits reach your report.