Updated May 29, 2026
What is llms.txt?
llms.txt is a root-level Markdown file that summarizes the pages you want AI systems to understand first. Think of it as a source map for your best documentation and policy pages, not a ranking shortcut.
When it helps most
llms.txt works best when you already have pages that answer one clear question with concrete detail. It can improve discovery of those pages by grouping them into a readable map.
- Docs-heavy websites: API docs, setup tutorials, and changelogs.
- B2B product sites: pricing rules, security policy, onboarding docs.
- Publisher knowledge bases: evergreen explainers and reference pages.
What it cannot guarantee
Publishing llms.txt does not guarantee indexing, ranking, or citations. Search and answer systems still prioritize crawlability, page quality, freshness, and trust signals.
How to deploy it correctly
- Publish at
/llms.txtfrom your root host. - Ensure it returns
200with no auth wall. - Use absolute canonical URLs in link lists.
- Keep the file concise: summary first, then grouped primary pages.
# Minimal deployment checks
curl -I https://yourdomain.com/llms.txt
curl -s https://yourdomain.com/llms.txt | sed -n '1,120p'
curl -I https://yourdomain.com/links-map.txtHow to keep it reliable
Treat llms.txt like a living index. Update it whenever your source pages change materially.
- Weekly: check links and remove stale URLs.
- Monthly: rebalance which pages deserve to be in the primary set.
- After migrations: refresh canonical URLs and verify redirects.
Related operations pages: How to test llms.txt, how many links to include, and update cadence guide.
Example llms.txt
# Example Product
> Example Product helps engineering teams monitor API reliability.
## Summary
Example Product publishes documentation, pricing, security notes, and release information for teams evaluating the product.
## Primary Pages
- [Documentation](https://example.com/docs): Product setup and API reference.
- [Pricing](https://example.com/pricing): Plan limits and billing rules.
- [Security](https://example.com/security): Data handling, compliance, and controls.How it fits SEO and GEO
For Google and Bing, core SEO fundamentals still dominate outcomes: crawlable HTML, clear intent per page, useful original information, and stable technical quality. llms.txt should support that work, not replace it.
For AI answer visibility, the winning pattern is simple: publish citeable pages, link them coherently, then map them with llms.txt.
For content-heavy sites, start with the WordPress blog source-page checklist before listing every post.