Safe Official docs Other Agents

TurnitinBot

Operated by Turnitin

Quick Facts

User-Agent:
TurnitinBot
Category:
Other Agents
Operator:
Turnitin
Safety:
Safe
Blocking Impact:
Varies - Evaluate before blocking
SEO Impact Score:
0/10
Official docs:
www.turnitin.com

Confirmed by the operator

Turnitin names TurnitinBot on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is TurnitinBot?

The bot user-agent for Turnitin's plagiarism detection service.

The bot user-agent for Turnitin's plagiarism detection service.
TurnitinBot crawls websites using the user-agent TurnitinBot. Review the safety rating and blocking impact below.

What happens if you block TurnitinBot?

❓ Impact Unknown - The SEO consequences of blocking TurnitinBot are not fully documented. Before blocking, check your analytics to confirm whether this bot generates referral traffic, review your server logs for crawl frequency, and test in a staging environment if possible.
Generally safe to allow; provides legitimate crawling value.

How to block TurnitinBot with robots.txt

<code>User-agent: TurnitinBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: TurnitinBot Disallow: /
Allow all (robots.txt)
User-agent: TurnitinBot Allow: /
Block private only (robots.txt)
User-agent: TurnitinBot Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block TurnitinBot if ($http_user_agent ~* "TurnitinBot") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block TurnitinBot SetEnvIfNoCase User-Agent "TurnitinBot" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is TurnitinBot safe to allow?

Yes, TurnitinBot is a safe and legitimate crawler. It is operated by Turnitin, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string TurnitinBot is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).
Verify by reverse-DNS lookup: legitimate TurnitinBot requests resolve to turnitin's domain.

What does TurnitinBot do?

Understanding TurnitinBot's purpose helps you decide whether to allow or block it.

  • Performs specialized web crawling tasks
  • May be used for research or data collection
  • Purpose varies depending on the specific bot
  • Check official documentation for details
  • Impact of blocking depends on your use case

TurnitinBot in context

TurnitinBot is a utility crawler operated by Turnitin. In plain terms, it harvests pages for a dataset or data product. Our database files it under other agents and ranks it Tier 6, the lowest priority: scrapers and tools that offer most sites little or nothing. 4 of the 4 other agents in our database share this tier.

Its safety rating is safe and its blocking impact is not documented. So the decision about TurnitinBot rests on what you want from Turnitin, not on its behaviour. How we rate safety and impact.

How site owners treat TurnitinBot

Our robots.txt study of the Tranco top 10,000 did not track TurnitinBot as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

TurnitinBot's operator does not clearly document how it treats robots.txt. Write the TurnitinBot rule anyway, then confirm in your logs that its requests stop.

Turnitin crawlers and close alternatives

Turnitin runs only this one crawler in our database, so a single User-agent: TurnitinBot group controls everything Turnitin fetches through it.

Other other agents that do the same job (harvests pages for a dataset or data product) include archive.org_bot from Internet Archive, Arquivo-web-crawler from Arquivo.pt, ia_archiver from Internet Archive. Deciding about TurnitinBot is usually a decision about the whole group, so check how your file treats these too.

We first recorded TurnitinBot on March 17, 2026. Turnitin documents it on turnitin.com, and we recheck that page before each release.

Which rule TurnitinBot actually follows

TurnitinBot reads exactly one group in robots.txt, the most specific one that names TurnitinBot, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: TurnitinBot
Disallow: /drafts/
  1. Find the group. TurnitinBot looks for a group naming TurnitinBot. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to TurnitinBot, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to TurnitinBot if the file also has a User-agent: TurnitinBot group?

No. Once a group names it, TurnitinBot reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking TurnitinBot remove your pages from AI answers?

Often, yes. TurnitinBot is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: turnitinbot the same as User-agent: TurnitinBot?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow TurnitinBot? Decide by situation

Recommended setting for TurnitinBot by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itLow stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI trainingBlocking it does not stop training, because TurnitinBot is a utility crawler. Block the operator's training crawler instead.
You run an online shopAllow it unless your logs show it is costly.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check TurnitinBot on your own site

  1. Open /robots.txt on your domain and search for TurnitinBot. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group TurnitinBot follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse TurnitinBot even when robots.txt allows it, and that never shows in the file.
  4. Run our AI crawler access test to see how TurnitinBot and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with TurnitinBot

The errors we see most often with TurnitinBot in the files and firewalls we test:

  1. Treating TurnitinBot as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
  2. Relying on robots.txt alone when TurnitinBot is rated caution or aggressive. Back the rule with a server-side block.
  3. Blocking TurnitinBot by IP alone. Ranges change; match the token and verify with logs.

All three hide inside a file that looks correct, so check TurnitinBot from outside after every change.

Spotting TurnitinBot in your logs

robots.txt says what TurnitinBot 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 "TurnitinBot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "TurnitinBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the TurnitinBot user-agent, so confirm the source before acting on a match:

  • TurnitinBot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable TurnitinBot request with caution.

Frequently Asked Questions

What is the official user-agent string for TurnitinBot?
The official user-agent string for TurnitinBot is: TurnitinBot. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from TurnitinBot by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.
Is TurnitinBot safe?
Yes, TurnitinBot is a safe and legitimate crawler. It is operated by Turnitin, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string TurnitinBot is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).
Will blocking TurnitinBot hurt my SEO?
❓ Impact Unknown - The SEO consequences of blocking TurnitinBot are not fully documented. Before blocking, check your analytics to confirm whether this bot generates referral traffic, review your server logs for crawl frequency, and test in a staging environment if possible.
How do I block TurnitinBot in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: TurnitinBot
Disallow: /

This instructs TurnitinBot not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt.
Does TurnitinBot respect robots.txt?
Yes - TurnitinBot is a well-behaved bot operated by Turnitin. It fetches and parses /robots.txt before crawling any page, following RFC 9309.
How do I verify if TurnitinBot is crawling my site?
Search your web server access logs for the string TurnitinBot (case-insensitive grep: grep -i "TurnitinBot" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For TurnitinBot specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).
What is the crawl frequency of TurnitinBot?
TurnitinBot crawls at a moderate rate. If you notice excessive traffic in your logs, you can add a Crawl-delay directive: 
User-agent: TurnitinBot
Crawl-delay: 10
(10 second delay between requests).
Can I block TurnitinBot from specific pages only?
Yes. Instead of a global Disallow: / you can restrict TurnitinBot to specific paths:
User-agent: TurnitinBot
Disallow: /private/
Disallow: /staging/
Allow: /

This allows TurnitinBot everywhere except the listed paths. Path matching in robots.txt uses prefix matching - Disallow: /private/ blocks /private/page.html but NOT /public/private/.
Is TurnitinBot causing high server load?
If TurnitinBot is generating excessive requests, you can:
1. Add Crawl-delay: 30 below the User-agent directive in robots.txt.
2. Rate-limit the user-agent via Nginx's limit_req_zone or Apache's mod_ratelimit.
3. Block it outright at Cloudflare WAF with rule: http.user_agent contains "TurnitinBot".
4. Use fail2ban to auto-block IPs exceeding request thresholds.

Related Bots

WhatsApp us