Assistant fetchers
QualifiedBot is a bot operated by Qualified that fetches single pages on demand for an AI assistant. QualifiedBot is Qualified's web crawler that analyzes customer websites to provide contextual information for their AI-powered chatbots and conversational marketing platf…. 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
"QualifiedBot"
Checked against
Nothing published
Live check
No operator check exists for QualifiedBot. This still shows what the address really is.
Reference
| User agent | QualifiedBotToken only: match on the substring. |
|---|---|
| Operator | Qualified |
| Purpose | Assistant fetchers |
| 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 | No explicit frequency provided. |
| Robots.txt tokens | QualifiedBot |
| Operator documentation | None published |
QualifiedBot is Qualified's web crawler that analyzes customer websites to provide contextual information for their AI-powered chatbots and conversational marketing platf…
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: QualifiedBot
Disallow: /User-agent: QualifiedBot
Allow: /User-agent: QualifiedBot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking QualifiedBot means a person who asks about one of your URLs gets an error instead of a summary. That is a support and reputation trade-off, not a training one.
Build a file for every crawlerFAQ
QualifiedBot is a bot operated by Qualified that fetches single pages on demand for an AI assistant. QualifiedBot is Qualified's web crawler that analyzes customer websites to provide contextual information for their AI-powered chatbots and conversational marketing platf…. 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 QualifiedBot 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 QualifiedBot 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 QualifiedBot means a person who asks about one of your URLs gets an error instead of a summary. That is a support and reputation trade-off, not a training one.