HomeArticlesrobots.txt & llms.txt Guide
Deploy Edge Fixer →
Technical Infrastructure & Crawler Policy

The Definitive Guide to robots.txt & llms.txt for AI Search Engines (2026)

Over 42% of websites that complain of zero citations in ChatGPT Search and Perplexity have misconfigured their robots.txt, blocked user-agents via Cloudflare Bot Fight Mode, or failed to publish an llms.txt index. Here is the complete production blueprint.

By Optymia AI Systems Engineering•Updated: October 2026•14 min read•Verified for GPT-5, Claude 3.7 & Gemini 2.5

1. The 2026 AI Crawler Taxonomy: Who Is Knocking on Your Door?

In 2024, webmasters viewed AI bots as a monolithic threat scraping content without attribution. By 2026, the ecosystem has fractured into two distinct classes: Model Pre-training Crawlers (which vacuum raw text for foundation models) and Live Search & Retrieval Crawlers (which fetch real-time answers and generate high-intent outbound clicks to your domain).

User-AgentOperatorPrimary PurposeImpact if BlockedRecommended Rule
OAI-SearchBotOpenAIChatGPT Search live indexingZero ChatGPT citationsAllow
GPTBotOpenAIFoundation model pre-trainingExcludes training dataDisallow or Allow
PerplexityBotPerplexity AIPerplexity Pro real-time RAGZero Perplexity citationsAllow
ClaudeBotAnthropicClaude search & artifacts retrievalExcluded from Claude citationsAllow
Google-ExtendedGoogleGemini & Vertex training controlBlocks Gemini, NOT Google SearchAllow for Gemini AEO
Applebot-ExtendedAppleApple Intelligence generative searchExcluded from Siri/Apple answersAllow

2. The Production-Grade robots.txt File for 2026

Below is the standard robots.txt pattern implemented across enterprise sites using Optymia. It grants full access to search and retrieval bots while safeguarding sensitive admin panels, internal APIs, and auth gates:

# ========================================================
# Optymia AI Optimized robots.txt (Updated 2026)
# ========================================================
User-agent: *
Allow: /
Disallow: /admin/
Disallow: /api/internal/
Disallow: /checkout/
Disallow: /dashboard/
# Live Search & Retrieval Bots (CRITICAL FOR CITATIONS)
User-agent: OAI-SearchBot
User-agent: PerplexityBot
User-agent: ClaudeBot
User-agent: Applebot-Extended
User-agent: Google-Extended
Allow: /
# Optional: If you want to block AI foundation model training
User-agent: GPTBot
User-agent: anthropic-ai
User-agent: CCBot
# Disallow: / (Uncomment only to block raw training scrape)
Sitemap: https://optymia.xyz/sitemap.xml
Sitemap: https://optymia.xyz/sitemap-blog.xml

3. Why Every Brand Needs an llms.txt File

Large Language Models operate on strict token budgets. When a user asks Perplexity or SearchGPT a question like "What is the best AI search tracker for Shopify stores?", the model doesn't want to scrape 50MB of CSS, unminified JavaScript bundles, and header tracking pixels.

The llms.txt standard provides an ultra-clean, Markdown-only interface. AI engines inspect this file to build an instant mental model of your architecture:

Structure of /llms.txt:

  • H1 Title: Brand name and core category statement.
  • Blockquote: Concise 2-sentence mission summary (direct snippet candidate).
  • Core Capabilities: Bullet points specifying exact features, technical specs, and pricing tiers.
  • Canonical Documentation: Clean Markdown links to programmatic solutions, developer guides, and comparative benchmarks.

Test Your Domain's AI Crawler Readiness

Enter your website URL below to test if GPTBot, PerplexityBot, and Google-Extended are granted access, inspect schema density, and calculate your live Astra Score.

Interactive Test · robots.txt & llms.txt Audit
Zero installation · 100% Free

Test your domain for AI search citations & Share of Model

Simulate how ChatGPT, Gemini, Perplexity, and Claude perceive your website.

4. Fixing Cloudflare & WAF False Positives

If your domain is behind Cloudflare, standard Bot Fight Mode frequently flags PerplexityBot and OAI-SearchBot as scraping attacks. To resolve this:

  1. Log into your Cloudflare Dashboard and navigate to Security > WAF > Custom Rules.
  2. Click Create Rule and name it "Allow Verified AI Search Engines".
  3. Set the rule expression to: (http.user_agent contains "PerplexityBot" or http.user_agent contains "OAI-SearchBot" or http.user_agent contains "ClaudeBot")
  4. Set Action to Skip > Select "All remaining custom rules" and "Bot Fight Mode".
  5. Deploy the rule. Verification will show 100% crawl success in your server logs within minutes.