ExaUser (Exa): what it is and how to allow or block it
Updated · checked against the operator's documentation on
ExaUser is the fetcher Exa uses to load a page live when a user, or an application using the Exa API, asks for its current content. Exa says it does not crawl on its own and that robots.txt may not apply to these user-initiated fetches. Every request is signed with Web Bot Auth. Its robots.txt token is ExaUser.
Seen ExaUser/1.0 in your logs?
Mozilla/5.0 (compatible; ExaUser/1.0; +https://exauser.crawler.exa.ai)The example string from Exa's documentation. Version numbers change; the token ExaUser stays.
- What it is
- An AI user-triggered fetcher run by Exa.
- Honors robots.txt
- DependsMay not apply, per Exa.
- Real or fake?
- No official checkThe user agent is only a claim, and Exa publishes no IP list or DNS check we could find.
- If you block it
- Exa says ExaUser does not decide whether your content appears in Exa search, so a rule for it does not remove you from search.
Facts
- Operator
- Exa
- Category
- AI user-triggered fetcher
- robots.txt token
ExaUser
- Honors robots.txt?
- May not apply, per Exa. Exa says that because the fetches are user-initiated, robots.txt rules may not apply to them. To opt out of search inclusion and automatic crawling it names the ExaSearchBot token, not ExaUser.
- User-agent example
Mozilla/5.0 (compatible; ExaUser/1.0; +https://exauser.crawler.exa.ai)
- Official source
- Exa: ExaUser
- Compared with the source
What it is used for
Per Exa, ExaUser fetches a page live when a user, or an application using the Exa API, requests its current content. It does not crawl the web automatically; that is ExaSearchBot's job, and images are fetched by ExaUser-Images. Exa says it fetches only public content, does not bypass logins, paywalls or CAPTCHAs, and submits no forms.
Opens one page because a person (or an answer being generated) needs it. The operator may treat robots.txt differently for these requests.
What happens if you block it
Exa says ExaUser does not decide whether your content appears in Exa search, so a rule for it does not remove you from search. To opt out of search and automatic crawling, Exa points to ExaSearchBot.
Exa publishes no IP list for ExaUser. It says every request is signed with Web Bot Auth (RFC 9421) and that the public key directory is at https://exauser.crawler.exa.ai/.well-known/http-message-signatures-directory; verifying means checking the signature against that directory. The Signature headers alone prove nothing.
Is it really ExaUser?
Anyone can send ExaUser as a user agent, and Exa publishes no IP list or reverse-DNS method that we could find, so a log line cannot prove a request is real. Check whether it fetched /robots.txt and whether the address belongs to the operator's network.
- We did not find an IP list or a reverse-DNS method in the official source we compared on 2026-11-09, so the user agent alone cannot show that a request is genuine. Check the operator's page for updates.
- Guide: Which crawlers send Web Bot Auth headers? 34 hours of requests to a small site.
- Guide: Fake Googlebots and PHP scanners: what hit our new server in 48 hours.
- Paste any user agent from your logs into the user-agent lookup, or follow the scripts in Fake Googlebots and PHP scanners.
How to allow or block ExaUser
Add one of these groups to the robots.txt at the root of your domain. A group that names the bot overrides a general User-agent: * group.
User-agent: ExaUser Allow: /
User-agent: ExaUser Disallow: /
Block ExaUser at the server
robots.txt asks; a server rule refuses. These answer 403 to any request whose user agent contains exauser/ (case-insensitive). They stop only bots that name themselves honestly, so keep the robots.txt group as well.
# server { ... }
if ($http_user_agent ~* "exauser/") {
return 403;
}RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} exauser/ [NC]
RewriteRule .* - [F,L]Step by step, with a test command: Block AI bots in nginx by user agent · Block AI bots in Apache with .htaccess · Block AI crawlers on Cloudflare · Block AI bots on Vercel
Does your site allow ExaUser today? The checker evaluates your robots.txt for this and every other bot.Check my site
What we see on this site
Live counter, last 30 days: 24 requests on 10 days identified as ExaUser (latest: ). That is a small sample: read it as an example, not as a measurement of the web.
- Content pages: 16
- robots.txt: 7
- Home page: 1
Counts come from this site's own server; they hold no IP addresses or URLs, and a user agent is only a claim. See the bot traffic data and the methodology.
Questions about ExaUser
What is ExaUser?
Exa's on-demand fetcher that loads a page when a user or an API client asks for it. Per Exa, ExaUser fetches a page live when a user, or an application using the Exa API, requests its current content. It does not crawl the web automatically; that is ExaSearchBot's job, and images are fetched by ExaUser-Images. Exa says it fetches only public content, does not bypass logins, paywalls or CAPTCHAs, and submits no forms.
Is ExaUser safe and legitimate?
The real ExaUser is an AI user-triggered fetcher run by Exa. A user-agent string is only a claim, though, so anyone can send it. We did not find an IP list or reverse-DNS method in the official source we compared on 2026-11-09, so the user agent alone cannot prove a request is real.
Does ExaUser obey robots.txt?
May not apply, per Exa. Exa says that because the fetches are user-initiated, robots.txt rules may not apply to them. To opt out of search inclusion and automatic crawling it names the ExaSearchBot token, not ExaUser.
How do I block ExaUser?
Robots.txt may not stop it. Exa says that because the fetches are user-initiated, robots.txt rules may not apply to them. To opt out of search inclusion and automatic crawling it names the ExaSearchBot token, not ExaUser. If you add a group anyway, use User-agent: ExaUser followed by Disallow: /. To refuse it outright, use the nginx or Apache rule on this page, which answers 403 to its user agent.
Will blocking ExaUser hurt my Google rankings or AI visibility?
Exa says ExaUser does not decide whether your content is in Exa search; that is controlled with the ExaSearchBot token. Blocking ExaUser does not change your rankings in Google.
What does the user agent "ExaUser/1.0; +https://exauser.crawler.exa.ai" mean?
Per Exa, it is a fetch made on demand for a user or an application using the Exa API, not a scheduled crawl. Exa signs these requests with Web Bot Auth and says robots.txt may not apply to them.
What does "Mozilla/5.0 (compatible; ExaUser/1.0; +https://exauser.crawler.exa.ai)" mean in my logs?
It is the user-agent string in Exa's documentation for ExaUser, an AI user-triggered fetcher run by Exa. The part that robots.txt rules match is the token ExaUser. The string is only a claim, because anyone can send it; the section "Is it really ExaUser?" above shows how to check a request.
Related bots
More from Exa
Other AI user-triggered fetchers
- ChatGPT-User OpenAIThe fetcher ChatGPT and Custom GPTs use when a person asks them to open a web page.
- Claude-User AnthropicThe agent Claude uses to open a web page when a person asks a question that needs one.
- Perplexity-User PerplexityThe fetcher Perplexity uses to visit a page when a person's question needs it.
- meta-externalfetcher MetaMeta's fetcher that retrieves individual URLs when a user asks, for example to help an AI complete a task.
All AI User-Triggered Fetchers · Bot directory · Bots from Exa · Which bots to allow or block · robots.txt generator · See a page as a bot