Skip to content

See where you stand

Change it

Works withWordPressShopifyWebflowGitHubGoogleSlackAll integrations
FixesFixes now ship to WordPress, Shopify, Webflow and GitHub

By team

By goal

Done for you

Not sure where to start? Take a guided tour.Book a demo
Customer storyHow the voice AI company Futuro grew its traffic3×AI traffic in 60 days

Learn

Data and research

FreeAI Site GraderAI Query Scannerllms.txt GeneratorAll free tools
Open dataWhere AI sends people, across more than 6,000 sites

ExaAI search crawler

ExaSearchBot

ExaSearchBot is a crawler for Exa’s search engine. Exa says its purpose is search and retrieval: connecting people and applications to your content and sending them back to your site.

Needed to be found in its search index.

Get the robots.txt ruleExa documentation
Is ExaSearchBot allowed on your site?
  • ExaSearchBotSearch
    Not checked

Reads your live robots.txt and applies the same rules these crawlers use. Nothing is stored.

robots.txt token
ExaSearchBot
Follows robots.txt
Yes, documented
Last checked
17 September 2026

Should you block ExaSearchBot?

Not if you want to be found. Blocking it can remove your pages from results that Exa serves to the AI tools and agents built on its index.

robots.txt
User-agent: ExaSearchBot
Disallow: /

Asks ExaSearchBot not to crawl any page. Add it to the robots.txt file at the root of your site, above any wider rules.

Ignored robots.txt?

Spot it in your logs.

Match the name, then check where the request came from. Anyone can copy a user-agent. Search your own logs for ExaSearchBot.

User-agentsource
Mozilla/5.0 (compatible; ExaSearchBot/1.0; +https://crawler.exa.ai/)

Version numbers change. Match the highlighted name, not the whole string.

  1. 1

    Match the name

    Search your server or CDN log for ExaSearchBot, case-insensitive. A match is a clue, not proof.

  2. 2

    Check the signed requests (Web Bot Auth)

    Exa signs every ExaSearchBot request with HTTP Message Signatures (RFC 9421), so the check holds regardless of IP address. crawler.exa.ai/.well-known/http-message-signatures-directory

Is this really ExaSearchBot?

Signed requests

Exa signs each ExaSearchBot request with HTTP Message Signatures (RFC 9421), so its address proves nothing. A genuine request carries Signature, Signature-Input and Signature-Agent headers, and the signature checks out against Exa’s published keys.

Many CDNs, Cloudflare included, check these signatures for you and mark the request as a verified bot. Without a signature, it isn’t ExaSearchBot.

crawler.exa.ai/.well-known/http-message-signatures-directory

Serve the content in HTML

The cited operator material does not verify JavaScript rendering. Serve useful HTML before client-side JavaScript where possible.

If ExaSearchBot is not named in robots.txt, Exa says it follows your rules for major search engines, then the * group. Robots.txt controls crawling, not indexing: use a noindex meta tag or X-Robots-Tag header to remove a page from Exa’s index.

How active is ExaSearchBot?

Measured across the sites connected to Trakkr, 10 August 2026 to 8 November 2026.

33%

of connected sites saw ExaSearchBot in the four weeks to 8 November 2026. That is 36 of 110.

100%75%50%25%35%
ExaSearchBot visited between 0% and 35% of connected sites each week from 10 August 2026 to 8 November 2026.

Share of connected sites it visited each week

Rank by reach
18 of 28
Typical site, per week
1,231 requests
Sites reached, 13 weeks
36 of 138

Most widespread AI crawlers

Share of connected sites each one visited, last four weeks.

  1. 1OAI-SearchBot83%
  2. 2ClaudeBot80%
  3. 3GPTBot66%
  4. 4Amazonbot63%
  5. 5PerplexityBot57%
  6. 6ChatGPT-User56%
  7. 7Bytespider56%
  8. 18ExaSearchBot33%
All 28 measured crawlers
How this is measured

Finalized daily crawler summaries from sites connected to Trakkr, grouped by the crawler named in each request. Trakkr’s own site is excluded. A site counts as reached in a week when it logged at least one request from ExaSearchBot. The typical figure is the median weekly requests among the sites it reached.

  • This is a sample of connected sites, not the whole web.
  • A matching user-agent does not prove the named operator sent the request.
  • Requests are not unique pages, training use or citations.
  • Crawlers seen on fewer than 10 sites are not shown. Classic search crawlers such as Googlebot are not collected on every site, so they are left out.

Questions, answered.

ExaSearchBot is a crawler for Exa's search engine. Exa says its purpose is search and retrieval: connecting people and applications to your content and sending them back to your site.

Sources.

Officially documented. Operator facts and Trakkr’s measurements keep separate dates.

  1. [1]
    Exa crawler documentation

    Officially documented · checked 17 September 2026

    crawler.exa.ai/

First verified 17 September 2026. Last source check 17 September 2026. Activity measured to 8 November 2026.

All AI crawlers

See which AI crawlers read your site.

Trakkr shows which bots, ExaSearchBot included, visit which pages each day, and whether the answers they feed mention you.

14-day free trial. Cancel anytime.