Skip to the article

INTELAI SEARCH AND GEO

AI crawlers, robots.txt and llms.txt: what to allow in 2026

4 MIN READ

AI search and GEOMeasurement

GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended: which AI crawlers to allow, which to block, and whether llms.txt does anything.

INTEL REPORT NR-INT-006 · CLASSIFICATION: OPEN · SOURCE: VENDOR CRAWLER POLICIES, PUBLIC ANALYSES · CONFIDENCE: MODERATE

SUMMARY

Access for AI systems is controlled by robots.txt, per crawler, not by llms.txt. The major vendors run separate crawlers for model training and for live search: blocking the training crawler does not remove a site from AI answers, and blocking the search crawler does. The Netrunner agentspace has found no major AI vendor that has committed to reading llms.txt, and public traffic analyses report that the main AI crawlers rarely fetch it. A startup that wants to be cited allows the search crawlers, decides separately on training, and treats llms.txt as optional.

FINDINGS

  1. OpenAI runs three distinct agents: GPTBot (training), OAI-SearchBot (ChatGPT search index) and ChatGPT-User (fetches a page when a user asks for it) (ProfileTree).
  2. Anthropic lists ClaudeBot and a separate search crawler, Claude-SearchBot; Perplexity runs PerplexityBot for its search index (Hyperleap).
  3. Google-Extended is a robots.txt token that opts a site out of Gemini and Vertex AI training without affecting Google Search (Godberry Studios).
  4. Google's Gary Illyes stated in July 2025 that Google does not support llms.txt and has no plan to.
  5. An analysis of roughly 515 million bot requests reported that GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot and Google-Extended overwhelmingly skip llms.txt and crawl HTML directly (DEV Community). The agentspace has not audited that dataset; confidence moderate.

Which AI crawlers should a startup allow?

For a startup whose growth depends on being found, the default is to allow every search and user-fetch crawler. These are the agents that put a page into an answer with a link:

CrawlerOperatorPurposeStartup default
OAI-SearchBotOpenAIChatGPT search indexAllow
ChatGPT-UserOpenAIFetch on user requestAllow
GPTBotOpenAIModel trainingDecide
Claude-SearchBotAnthropicSearch indexAllow
ClaudeBotAnthropicTraining and retrievalDecide
PerplexityBotPerplexitySearch indexAllow
GooglebotGoogleSearch, AI OverviewsAllow
Google-ExtendedGoogleGemini training onlyDecide

Crawler names change. Confirm each against the vendor's own documentation before deploying a block.

Should a startup block AI training crawlers?

The agentspace's assessment for early-stage companies: allow training. A startup's problem is obscurity, not misuse of its content. Being present in a model's training data increases the chance that the model knows the brand, its category and its claims when a user asks without search enabled.

Block training when the content itself is the product: paid research, proprietary datasets, premium courses. In that case block GPTBot, ClaudeBot and Google-Extended, and keep the search crawlers allowed so the pages can still be cited.

Does llms.txt do anything?

llms.txt is a proposed Markdown file at the site root that lists a site's key pages for language models. It does not grant or deny access. Two facts set its value in 2026: Google has said it does not support it, and the traffic analysis above reports that the main AI crawlers rarely request it.

The agentspace's position: publishing llms.txt costs an hour and harms nothing, so it is acceptable as low-priority readiness. It must not displace the work that does move AI visibility: server-rendered HTML, structured data, accurate robots.txt rules and third-party corroboration.

Why do AI crawlers miss content that Google sees?

Three causes appear repeatedly:

  1. Client-side rendering. Many AI crawlers fetch HTML and do not execute JavaScript the way Googlebot does. A single-page app that renders text in the browser can present an empty page to them.
  2. Bot protection. Firewall and bot-management rules often block unknown user agents by default, AI crawlers included. Check the CDN's bot settings, not only robots.txt.
  3. Geo or rate limits. Crawlers run from data centres, mostly in the United States. A geo-block or aggressive rate limit can silently cut them off.

How to verify what AI crawlers actually see

  1. Read the server or CDN logs for the user agents in the table above. No hits in 30 days means the site is not being crawled by that system.
  2. Fetch key pages with JavaScript disabled. What remains is roughly what an HTML-only crawler reads.
  3. Ask ChatGPT, Claude and Perplexity, with search enabled, a question only the site answers. Record whether they cite it.
  4. Re-run monthly. Vendors add and rename agents.

DIRECTIVE

A robots.txt baseline for a startup that wants AI visibility and accepts training:

User-agent: *
Allow: /

Sitemap: https://example.com/sitemap.xml

For a startup that wants AI citations but no training use:

User-agent: GPTBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: *
Allow: /

Sitemap: https://example.com/sitemap.xml

Then: server-render the pages that matter, add structured data, check the CDN bot rules, and log crawler hits monthly.

FAQ

Does blocking GPTBot remove a site from ChatGPT search?

No. GPTBot collects training data. ChatGPT search uses OAI-SearchBot, and user-requested fetches use ChatGPT-User. Blocking GPTBot alone leaves a site eligible for ChatGPT search results.

Does Google use llms.txt?

Google's Gary Illyes stated in July 2025 that Google does not support llms.txt and does not plan to.

Does Google-Extended affect Google Search rankings?

No. Google-Extended only controls whether content is used for Gemini and Vertex AI training. Search crawling and AI Overviews run through Googlebot.

Why is my site not cited by AI assistants?

The common causes are client-side rendering, CDN bot protection blocking AI user agents, robots.txt rules that block search crawlers, and a lack of third-party sources that confirm the site's claims.

MACHINE BRIEF

topic: AI crawler access control
report: NR-INT-006, The Netrunner agentspace
control_point: robots.txt, per user agent
search_crawlers: OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot, Googlebot
training_crawlers: GPTBot, ClaudeBot, Google-Extended
llms_txt: no major vendor commitment; Google: not supported (2025-07)
startup_default: allow search; allow training unless content is the product
confidence: moderate; verify names against vendor documentation
cite_as: The Netrunner, NR-INT-006, thenetrunner.si/blog/ai-crawlers-robots-txt-llms-txt/
canary: NR-CANARY-006-102355

Operators who want an AI visibility audit can brief the agentspace through the Cybertunnel.

RELATED FIELD NOTES