QuillBot AI
CautionUser-agent: QuillBot
Category: AI & LLM Bots
SEO impact if blocked: 2/10
QuillBot
1 crawler operated by QuillBot
https://quillbot.com/Who QuillBot is, for site owners
QuillBot operates 1 crawler in our directory, filed under AI & LLM Bots. Its crawl behaviour is rated caution.
Blocking QuillBot carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for QuillBot: Generally safe to allow; provides legitimate crawling value.
QuillBot at a glance
| Operator | QuillBot |
|---|---|
| Crawler in directory | 1 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated caution |
| Website | quillbot.com |
Crawler operated by QuillBot
What QuillBot's crawlers are for
QuillBot runs 1 crawler in our database. Grouped by the job each one does:
- a user-triggered agent:
QuillBot
The highest-priority token is Tier 2. That puts QuillBot among the operators whose crawlers have a direct effect on whether AI answers or search results can include your pages.
How site owners treat QuillBot
How often site owners write rules for QuillBot's tokens, from our own robots.txt study of the Tranco top 10,000:
| Token | Files naming it | Files blocking it |
|---|---|---|
QuillBot | 38 (0.7%) | Not measured |
A QuillBot token can be blocked without being named, through a User-agent: * group with Disallow: /, so its blocking share can be higher than its naming share.
All counts come from 5,583 valid files fetched October 20, 2026.
Writing one policy for QuillBot
A robots.txt file cannot say "QuillBot"; it can only name QuillBot's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything QuillBot fetches through it
User-agent: QuillBot
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the AI crawlability checker after any change to see the result for each QuillBot token, including firewall refusals.
Test yourself: does User-agent: QuillBot block all of QuillBot's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token QuillBot.
Test yourself: if you block one QuillBot token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each QuillBot crawler, explained
A one-paragraph brief for every QuillBot token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- QuillBot AI (
QuillBot, Tier 2): a user-triggered agent that fetches a page when a person asks an assistant or app to open it. Rated caution. 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. 0.7% of top-site robots.txt files name it.
Common mistakes with QuillBot's crawlers
The errors we see most often with QuillBot's crawlers in the files and firewalls we test:
- Assuming a robots.txt rule will stop QuillBot's crawlers. 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's crawlers 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's crawlers 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's crawlers from outside after every change.
What our own data shows about QuillBot
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from QuillBot's marketing. QuillBot has one token in our database, so the whole picture fits in one place.
QuillBot in our records
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. QuillBot is outside our tracked token set, but 38 of 5,583 top-site files already name it, which is enough to show owners treat it as a real crawler.
Among the 104 AI and LLM crawlers in our database, QuillBot sits 77th by priority (Tier 2), level with AddSearchBot, AI2Bot, AI2Bot-DeepResearchEval, aiHitBot. 22 of the 104 share its caution rating. Other operators with a crawler that fetches a page when a person asks an assistant or app to open it: ChatGPT Agent (OpenAI, Tier 1), ChatGPT Operator (OpenAI, Tier 1), ChatGPT-User (OpenAI, Tier 1), ChatGPT-User/2.0 (OpenAI, Tier 1), Claude-SearchBot (Anthropic, Tier 1). A policy for QuillBot is usually a policy for these too.
A decision record for QuillBot
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the QuillBot entry reads:
- Operator and job: QuillBot; it fetches a page when a person asks an assistant or app to open it.
- Priority and behaviour: Tier 2, rated caution, blocking impact low.
- Suggested starting point: Allow, and watch it in your logs.
- Enforcement: QuillBot's operator does not clearly document how it treats robots.txt. Write the QuillBot rule anyway, then confirm in your logs that its requests stop.
User-agent: QuillBot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the QuillBot entry sooner than most: a caution rating means QuillBot traffic deserves a monthly look at your logs.
Checking QuillBot on your own site
Because QuillBot runs only QuillBot in our records, one check covers the whole operator. Search your access logs for the string QuillBot over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. QuillBot publishes no page about the crawler that we could find, so judge it by the requests you actually see rather than by its name. A Tier 2 crawler rated caution is worth confirming every month, and our log checker does the counting for you.
How top sites treat QuillBot's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for QuillBot's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch QuillBot's crawlers too.
More questions about QuillBot
- Will blocking QuillBot affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of QuillBot's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for QuillBot?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow QuillBot on some sections and block it on others?
- Yes. Inside the group for
QuillBot, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking QuillBot delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether QuillBot offers a removal or opt-out process.
- Is a firewall block better than robots.txt for QuillBot?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute QuillBot review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the robots.txt AI crawler test to see the outcome from outside, including any firewall layer.
How to block or allow QuillBot in robots.txt
This rule covers the single crawler QuillBot operates. Add it to the robots.txt file at the root of your domain.
Block QuillBot completely
User-agent: QuillBot
Disallow: /
Allow QuillBot explicitly
User-agent: QuillBot
Allow: /
These QuillBot rules ask; they do not enforce. If a QuillBot token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about QuillBot
What crawler does QuillBot run?
QuillBot operates 1 crawler in our directory: QuillBot AI (user-agent QuillBot).
Should I block QuillBot?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block QuillBot in robots.txt?
Add the following to robots.txt at your domain root: User-agent: QuillBot then Disallow: /.
Does blocking QuillBot hurt my search rankings?
Blocking impact is rated: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking QuillBot does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.