QuillBot AI
Operated by QuillBot
Quick Facts
- User-Agent:
- QuillBot
- Category:
- AI & LLM Bots
- Operator:
- QuillBot
- Safety:
- Use Caution
- Blocking Impact:
- Low - No SEO ranking impact
- SEO Impact Score:
- 2/10
- Official docs:
- None published by QuillBot
Reported, not operator documented
QuillBot has not published a crawler page that names QuillBot. It is listed here on our own evidence. Verified by AI Crawler Check: 38 of the 5,583 valid robots.txt files in the Tranco top 10,000 carry a rule for QuillBot, so site owners treat it as a real crawler name (how we measure this). That proves the spelling is in use, not who sends it. Reported QuillBot fetcher. No vendor page.
What that means for you: the QuillBot rule on this page is the best available spelling, but QuillBot has made no statement of purpose, crawl rate or robots.txt compliance. Treat a QuillBot request in your logs as a clue, not proof of who sent it, and add a firewall rule if that traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.
What is QuillBot AI?
QuillBot AI is an on-demand AI fetcher operated by QuillBot. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into QuillBot's assistant.
QuillBot AI is an on-demand AI fetcher operated by QuillBot. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into QuillBot's assistant.
QuillBot AI uses the user-agent token QuillBot. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.
What happens if you block QuillBot AI?
User-agent / Disallow: / without any SEO penalty.Want to see whether QuillBot AI actually visits you? Read how do I monitor AI bot traffic to my website?
How to block QuillBot AI with robots.txt
<code>User-agent: QuillBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is QuillBot AI safe to allow?
What does QuillBot AI do?
Understanding QuillBot AI's purpose helps you decide whether to allow or block it.
- Fetches a page only when a user asks an AI assistant to read it
- Summarizes or extracts the URL the user provided
- Triggered by real user intent, not bulk crawling
- Low traffic volume compared with training crawlers
- Blocking it prevents users from pulling your content into the assistant
QuillBot AI in context
QuillBot AI is a user-triggered agent operated by QuillBot. In plain terms, it fetches a page when a person asks an assistant or app to open it. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 of the 104 AI and LLM crawlers in our database share this tier.
Its safety rating is caution and its blocking impact is low. So the decision about QuillBot AI rests on what you want from QuillBot, not on its behaviour. How we rate safety and impact.
How site owners treat QuillBot AI
In our own scan of the Tranco top 10,000 (5,583 valid robots.txt files), 38 files (0.7%) name QuillBot in a User-agent line. That shows site owners treat the token as a real crawler worth a rule. It does not, on its own, prove who operates it.
Does it follow robots.txt?
QuillBot AI's operator does not clearly document how it treats robots.txt. Write the QuillBot AI rule anyway, then confirm in your logs that its requests stop.
QuillBot crawlers and close alternatives
QuillBot runs only this one crawler in our database, so a single User-agent: QuillBot group controls everything QuillBot fetches through it.
Other AI and LLM crawlers that do the same job (fetches a page when a person asks an assistant or app to open it) include ChatGPT Agent from OpenAI, ChatGPT Operator from OpenAI, ChatGPT-User from OpenAI, ChatGPT-User/2.0 from OpenAI, Claude-SearchBot from Anthropic, Claude-User from Anthropic. Deciding about QuillBot AI is usually a decision about the whole group, so check how your file treats these too.
We first recorded QuillBot on June 18, 2026. We could not find a page where QuillBot names it, so treat the token as reported rather than documented.
Which rule QuillBot AI actually follows
QuillBot AI reads exactly one group in robots.txt, the most specific one that names QuillBot, and never combines rules across groups. This short file shows the trap:
User-agent: *
Disallow: /private/
User-agent: QuillBot
Disallow: /drafts/- Find the group. QuillBot AI looks for a group naming
QuillBot. One exists, so it ignoresUser-agent: *completely. - Apply only that group. It is refused
/drafts/and nothing else. - The surprise.
/private/is open to QuillBot AI, because that rule lives in the*group it no longer reads. To keep it out of both, repeatDisallow: /private/inside its own group.
Test yourself: does a rule under User-agent: * apply to QuillBot AI if the file also has a User-agent: QuillBot group?
No. Once a group names it, QuillBot AI reads only that group. Put every rule you want it to follow inside its own group.
Related: how AI engines choose their sources
Test yourself: will blocking QuillBot AI remove your pages from AI answers?
Often, yes. QuillBot AI is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.
Test yourself: is User-agent: quillbot the same as User-agent: QuillBot?
Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.
Should you allow QuillBot AI? Decide by situation
| If you are... | Recommended setting |
|---|---|
| You publish content and want AI answers to cite it | Allow it. QuillBot AI fetches pages for answers, so blocking it can remove you from them. |
| You license content and want to stop AI training | Blocking it does not stop training, because QuillBot AI is a user-triggered agent. Block the operator's training crawler instead. |
| You run an online shop | Allow it on product and category pages, which are the pages shoppers ask assistants about. |
| Your server is under load from bots | Rate-limit before blocking. It is rated caution in our database. |
Check QuillBot AI on your own site
- Open
/robots.txton your domain and search forQuillBot. If it is not named, it followsUser-agent: *. - List the
Disallowlines in the group QuillBot AI follows and test your key URLs against them; the longest match wins, andAllowwins a tie. - Look beyond the file. A firewall or bot manager can refuse QuillBot AI even when robots.txt allows it, and that never shows in the file.
- Run our AI crawlability test to see how QuillBot AI and every other crawler we track are treated in one pass, including firewall refusals.
Common mistakes with QuillBot AI
The errors we see most often with QuillBot AI in the files and firewalls we test:
- Assuming a robots.txt rule will stop QuillBot AI. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
- Blocking QuillBot AI as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
- Counting QuillBot AI visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.
All three hide inside a file that looks correct, so check QuillBot AI from outside after every change.
Spotting QuillBot AI in your logs
robots.txt says what QuillBot AI may do; your access logs show what it actually did.
Count requests
On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):
grep -iE "QuillBot" /var/log/nginx/access.log \
| awk '{print $4}' | cut -d: -f1 | sort | uniq -cAnd this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:
grep -iE "QuillBot" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20Check the requests are genuine
Anyone can send the QuillBot AI user-agent, so confirm the source before acting on a match:
QuillBot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable QuillBot AI request with caution.
Frequently Asked Questions
What user-agent string does QuillBot AI use?
QuillBot. Evidence that the spelling is in real use comes from our own robots.txt study: 38 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), not from QuillBot, which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.Is QuillBot AI safe?
Will blocking QuillBot AI hurt my SEO?
User-agent / Disallow: / without any SEO penalty.How do I block QuillBot AI in robots.txt?
/robots.txt file:User-agent: QuillBot Disallow: /
This instructs QuillBot AI not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does QuillBot AI respect robots.txt?
QuillBot will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.How do I verify if QuillBot AI is crawling my site?
QuillBot (for example grep -i "QuillBot" /var/log/nginx/access.log). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that QuillBot sent it.