ExaBot
ExaBot is a bot operated by Exa that crawls pages into a dataset that is then reused or sold. ExaBot is a web crawler that indexes web content to power Exa's AI search engine and semantic search APIs for AI applications. 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.
ExaBot at a glance
| User agent | ExaBotToken only. The operator has not published a full user-agent string, so match on the substring rather than an exact header. |
|---|---|
| Operator | Exa |
| Purpose | Data scrapers and resellers |
| 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 | Not published |
| Robots.txt tokens | ExaBot |
| Operator documentation | None published |
ExaBot is a web crawler that indexes web content to power Exa's AI search engine and semantic search APIs for AI applications.
Allow or block ExaBot
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.
User-agent: ExaBot
Disallow: /Blocks every path for this crawler only.
User-agent: ExaBot
Allow: /Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.
User-agent: ExaBot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own account, checkout and search URLs.
What blocking actually costs you
Blocking ExaBot stops your content being packaged and resold to third parties. Whoever bought earlier crawls still has them.
Block every crawler in the directory at onceIs that really ExaBot?
A user-agent header is a string the client chooses. Scrapers copy ExaBot 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.
Related crawlers
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.