What is AI Search External?
AI Search External is the identity Cloudflare AI Search uses when a crawl leaves the customer's own Cloudflare account and reaches another domain. It is not a separate global search engine. A Cloudflare customer starts the indexing job, and Cloudflare performs the external request on that customer's behalf.
External traversal is off by default. In the AI Search discovery settings, a customer must enable external links or subdomains before the crawler follows them beyond the source host. On domains inside the customer's Cloudflare account the crawler identifies as Cloudflare-AI-Search; on a domain outside that account it switches to Cloudflare-AI-Search-External.
Cloudflare's AI Search documentation says a website data source is fetched, converted to Markdown, split into chunks, and added to the customer's index. That index can support retrieval or generated answers in the application the customer builds. The customer also decides whether to expose search, chat completion, or MCP endpoints.
An external crawl can therefore make a page searchable inside one customer's AI Search instance. It does not place the page in a universal Cloudflare index, and it does not promise a public citation. Cloudflare does not document this crawler as a source of foundation-model training data, so a visit should not be described as model training.
The complete recorded user agent is Cloudflare-AI-Search-External (https://developers.cloudflare.com/ai-search; [email protected]). The stable token is Cloudflare-AI-Search-External. It states the operator, documentation location, and contact address without relying on a changing browser version.
Robots behavior needs a qualified answer. This page's structured bot status is unknown, while the supplied Cloudflare directory record marks the external variant as not following robots.txt. Current AI Search product documentation says pages disallowed by robots.txt are recorded as blocked_by_robots_txt instead of being indexed. Because those records disagree, publish a specific directive but use an actual deny rule when exclusion must be certain.
Cloudflare signs these requests with Web Bot Auth. The public key directory for the external identity is https://search.ai.cloudflare.com/external/.well-known/http-message-signatures-directory. Validating the HTTP message signature can prove that Cloudflare sent the request; it does not identify which Cloudflare customer configured the crawl or what that customer will do with indexed results.
