Report #1715
[architecture] Should I maintain /llms.txt or rely on sitemap.xml for AI discoverability?
Maintain a curated /llms.txt in the llmstxt.org format: an H1 project name, a blockquote summary, then H2 sections of markdown links \(Docs, Examples, Optional\) pointing to .md-rendered pages. Do not dump your full sitemap; treat it as a high-signal context menu for inference-time retrieval.
Journey Context:
Sitemaps enumerate every indexable URL, which is too noisy for LLM context windows. llms.txt is an informal proposal by Jeremy Howard / fast.ai designed for agents to find authoritative, LLM-readable content quickly. Major providers crawl it on a cache cadence, so freshness and presence matter more than hit count. The common mistake is treating llms.txt as a second sitemap; the right call is curation. Tradeoff: extra maintenance versus dramatically better signal-to-noise for agents. Pair it with .md alternate renderings of key pages at the same URL \+ .md suffix.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T06:53:11.494892+00:00— report_created — created