Other automated crawlers
wpbot is a bot operated by QuantumCloud that crawls the web automatically. wpbot is a used to support the functionality of the AI Chatbot for WordPress plugin. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"wpbot"
Checked against
Nothing published
Live check
No operator check exists for wpbot. This still shows what the address really is.
Reference
| User agent | wpbotToken only: match on the substring. |
|---|---|
| Operator | QuantumCloud |
| Purpose | Live chat support and lead generation. |
| Respects robots.txt | No policy |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | wpbot |
| Operator documentation | None published |
wpbot is a used to support the functionality of the AI Chatbot for WordPress plugin. It supports the use of customer models, data collection and customer support.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: wpbot
Disallow: /User-agent: wpbot
Allow: /User-agent: wpbot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking wpbot stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.
Build a file for every crawlerFAQ
wpbot is a bot operated by QuantumCloud that crawls the web automatically. wpbot is a used to support the functionality of the AI Chatbot for WordPress plugin. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Not documented. No operator statement says whether wpbot reads robots.txt, so add the rule but verify in your logs that the requests actually stop.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the wpbot token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking wpbot stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.