Does QualifiedBot respect robots.txt?

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.

How do I block QualifiedBot?

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.

IPScanner

Assistant fetchers

QualifiedBot

Q: How do I verify a request really came from QualifiedBot?

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.

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.

Verify an IP that claimed to be QualifiedBot

No operator check exists for QualifiedBot, so this will not be able to confirm the name. What it can still tell you is what the address actually is: which network announces it, and whether it is a hosting range, a residential proxy or a Tor exit.

The check needs JavaScript. The evidence it uses is public either way: the operator's own documentation says how a request claiming to be QualifiedBot can be verified, and the table below repeats it.

QualifiedBot at a glance

Reference data for the QualifiedBot crawler
User agent	`QualifiedBot` Token only. The operator has not published a full user-agent string, so match on the substring rather than an exact header.
Operator	Qualified
Purpose	Assistant fetchers
Respects robots.txt	Not documented
Verification method	None 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

Allow or block QualifiedBot

Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.

Block QualifiedBot

User-agent: QualifiedBot
Disallow: /

Blocks every path for this crawler only.

Allow QualifiedBot

User-agent: QualifiedBot
Allow: /

Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.

Allow, except the pages you never want quoted

User-agent: QualifiedBot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /search

Edit the Disallow paths to match your own account, checkout and search URLs.

What blocking actually costs you

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.

Block every crawler in the directory at once

Verification

Is that really QualifiedBot?

A user-agent header is a string the client chooses. Scrapers copy QualifiedBot precisely because site owners allow it. 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.

Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.

Datacenter IP detectionNearly every real AI crawler egresses from cloud ranges. A residential IP claiming to be one is the first thing to check.IP reputation checkSee whether the address behind a fake crawler hit has a history of abuse elsewhere.Residential proxy detectionScrapers that get blocked by user agent often come back through residential proxy pools.

Related crawlers

Amzn-UserAmazon · Assistant fetchers ChatGPT-UserOpenAI · Assistant fetchers Claude-UserAnthropic · Assistant fetchers DuckAssistBotOperator unknown · Assistant fetchers Google-NotebookLMGoogle · Assistant fetchers

Agentscan

Identify crawlers automatically instead of by hand

Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.

How Agentscan works API reference Pricing What is my IP

FAQ