Does Thinkbot respect robots.txt?

No. Thinkbot is documented as ignoring robots.txt, so a Disallow line will not stop it. Blocking needs to happen at the edge, by user agent or by source address.

How do I block Thinkbot?

Add the Thinkbot 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

Other automated crawlers

Thinkbot

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

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.

Thinkbot is a bot that crawls the web automatically. Collects data for analysis on AI usage and automation. 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.

Thinkbot at a glance

Reference data for the Thinkbot crawler
User agent	`Thinkbot` Token only. The operator has not published a full user-agent string, so match on the substring rather than an exact header.
Operator	Thinkbot
Purpose	Insights on AI integration and automation.
Respects robots.txt	No
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	Not published
Robots.txt tokens	`Thinkbot`
Operator documentation	None published

Collects data for analysis on AI usage and automation.

robots.txt

Allow or block Thinkbot

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. Thinkbot is documented as ignoring robots.txt, so treat the block below as a statement of intent and enforce it at your CDN.

Block Thinkbot

User-agent: Thinkbot
Disallow: /

Blocks every path for this crawler only.

Allow Thinkbot

User-agent: Thinkbot
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: Thinkbot
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 Thinkbot stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.

Block every crawler in the directory at once

Verification

Is that really Thinkbot?

A user-agent header is a string the client chooses. Scrapers copy Thinkbot 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

facebookexternalhitMeta/Facebook · Other automated crawlers OpenAIOpenAI · Other automated crawlers BuddyBotBuddyBotLearning · Other automated crawlers EchoboxBotEchobox · Other automated crawlers Google-FirebaseGoogle · Other automated crawlers

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