A fast, categorized index of links only (llms.txt).
Blocked or private site? Paste the sitemap XML or a URL list
How to use
Enter your site URL
Type your domain and choose Short (llms.txt) or Full content (llms-full.txt). If the site blocks our server, open the paste box, paste your sitemap XML or a URL list and press Generate from pasted list.
Add a name and description
Fill in Site name and Short description. The name becomes the H1 at the top of the file, and the description sits under it as a blockquote, as the llms.txt proposal describes.
Generate and download
Press Generate llms.txt, then Add page titles and descriptions and open the editor to tidy the links. Copy or download the file and upload it so it loads at /llms.txt.
Why llms.txt Generator
- Finds your sitemap through robots.txt, common paths and sitemap index files.
- Adds page titles and descriptions and lets you edit, reorder and regroup every link.
- Builds llms-full.txt with page text when you need the long version.
- Paste mode works for sites that block automated requests.
llms.txt vs robots.txt vs sitemap.xml
All three files sit at the root of your domain, and they are easy to mix up. robots.txt sets crawl rules, sitemap.xml lists every page you want found, and llms.txt picks out the pages that explain your site most clearly to an AI model. None of them replaces the others.
A practical order is to get robots.txt right first, since it decides what any bot may fetch at all, then keep sitemap.xml complete and current, and only then write llms.txt as a short selection from the sitemap. If robots.txt blocks a page, listing it in llms.txt does not make it readable to crawlers that obey the block.
| llms.txt | robots.txt | sitemap.xml | |
|---|---|---|---|
| Purpose | Curated guide for AI tools | Crawl rules for bots | Full list of pages for search engines |
| Format | Markdown | Plain text directives | XML |
| Can block access | No | Yes, for bots that obey it | No |
| Typical size | Tens of links | A few lines | Every indexable URL |
| Status | Proposed format from 2024 | IETF standard, RFC 9309 | Protocol from sitemaps.org |