Simple process
How to generate your llms.txt
-
Enter your site name & summary
Add your site or product name and a one-line description. This becomes the title and quote block at the top of your file.
-
Auto-discover pages (optional)
Enter your domain and the tool scans your sitemap.xml, grouping URLs by section automatically. No sitemap? Add links manually instead.
-
Organize into sections
Group links under clear headings — Docs, Guides, Pricing, API Reference — the same way you would organize a table of contents.
-
Download & upload
Copy or download the generated llms.txt, then upload it to your site root so it's reachable at yoursite.com/llms.txt.
What is llms.txt and why does it matter?
An optional markdown guide at your site root that summarizes your site and priority pages for systems that choose to use the proposed convention.
Definition
llms.txt is a proposed plain-text file placed at a site root to summarize the site, its intended audience, and selected priority links in a markdown-friendly format. It offers optional guidance to systems that choose to read it; it is not an access-control standard, a replacement for robots.txt or sitemaps, or a guarantee of crawling, ranking, citation, or AI use.
Some AI-assisted search products fetch and cite live web pages at query time. robots.txt controls crawler access; llms.txt is a separate, proposed convention for summarizing core docs, pricing, and key guides in a concise text format. Support varies, so treat the file as optional guidance rather than an access rule or ranking signal.
Adoption is still early and varies by product. A concise, maintained file can still serve as a useful machine-readable directory and editorial inventory, but publishers should evaluate it as an experiment and keep canonical pages, sitemaps, structured data, and crawl controls authoritative.
What a good llms.txt includes
Four pillars that separate a useful file from a dump of every URL on your site.
Clear identity
- Site or product name as H1
- One-line summary as a quote block
- No marketing fluff — direct, factual description
Organized sections
- Logical grouping (Docs, Guides, API, Pricing)
- Short labels, not full sentences
- Optional one-line notes per link
Curated, not exhaustive
- Your most important pages, not every URL on the site
- Prioritize docs, guides, and canonical reference pages
- Skip low-value pages (legal, archived content, thin tag pages)
Kept current
- Update when you add major docs or restructure sections
- Treat it like a sitemap for humans-reading-as-AI, not a one-time file
llms.txt vs. robots.txt vs. sitemap.xml
Three root files, three audiences — don’t confuse access rules with a curated AI summary.
These three files sound similar but serve different audiences. Confusing them is the most common mistake when adding llms.txt for the first time.
| robots.txt | sitemap.xml | llms.txt | |
|---|---|---|---|
| Audience | Search crawlers | Search engines | AI systems / LLMs |
| Purpose | Access rules | Full URL list | Curated summary |
| Format | Directives | XML | Markdown |
| Required? | Best practice | Best practice | Emerging convention |
Methodology & limitations
- Optional discovery fetches only public, same-origin robots.txt and sitemap resources through the shared SSRF-safe fetch layer; private and unsafe network targets are blocked.
- Sitemap discovery is bounded: the generator samples a limited number of same-origin child sitemaps and returns at most 200 URLs for review rather than treating every discovered page as important.
- You remain the editor. Remove utility, duplicate, private, thin, or outdated URLs and describe the site accurately before publishing the generated file.
- llms.txt is a proposed convention with varying adoption. A valid file does not control crawler access and cannot guarantee discovery, ranking, citation, summarization, or use by any AI product.
Frequently asked questions
Quick answers about format, placement, and how AI systems use the file.
What is llms.txt?
Who uses llms.txt?
Is llms.txt an official web standard?
Does llms.txt replace robots.txt or sitemap.xml?
Where do I upload the generated file?
What pages should I include?
Does sitemap auto-discovery work on every site?
How often should I update llms.txt?
Will this improve my Google rankings?
How is this different from the AEO Readiness Checker?
Why trust this llms.txt generator?
Same SSRF-safe tooling as our AEO checker — built for production sites, not a generic form wrapper.
Built by Maksut as part of the same AEO tooling behind the AEO Readiness Checker and AI Content Gap Finder — production WordPress and technical AEO work, not a generic form wrapper. Sitemap discovery uses the same SSRF-safe fetch infrastructure as the other tools on this site, so scanning your domain is safe by default.
llms.txt is an emerging, unofficial convention — no vendor guarantees it will be used, and adoption varies by AI provider. This tool helps you ship a correctly-formatted file quickly; it does not promise a specific outcome in any AI system's answers.