Create and serve an llms.txt file to guide AI inference tools to your site's most valuable content, and understand its actual scope and limitations

domain: llmstxt.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create a plain-text Markdown file at 'https://yourdomain.com/llms.txt' listing your site's key documentation pages, API references, and high-signal content with brief descriptions
  2. Structure the file with a short H1 title, a brief site description paragraph, and then H2 sections grouping related pages — each entry is a Markdown link with a one-line description
  3. Optionally create 'llms-full.txt' containing the full text of all important pages concatenated, for AI tools that prefer a single context-window-friendly document
  4. Do not use llms.txt as a crawler control mechanism — it cannot restrict any crawler, cannot opt your site out of AI training, and has no enforcement mechanism
  5. Verify adoption before relying on it: as of mid-2026, no major AI company has publicly committed to production support; practical value is primarily in developer tooling (Cursor, GitHub Copilot) that fetches docs in real time
  6. Combine llms.txt with robots.txt user-agent blocks (GPTBot, ClaudeBot, CCBot) if you want to restrict AI crawling — llms.txt alone provides no restriction

Known gotchas

Related routes

Evaluate whether to implement an llms.txt file for a site and set expectations about its actual effect on AI crawler/agent behavior
llmstxt.org · 6 steps · unrated
Decide whether publishing an llms.txt file is worth the effort for AI visibility
llmstxt.org · 5 steps · unrated
Publish /llms.txt and /agents.md discovery files on a merchant storefront describing site capabilities, supported MCP endpoints, and structured feeds for AI shopping agents
llmstxt.org · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans