- [ Home ](/) / - Generator Form or sitemap · Live preview # Generate your `llms.txt` Paste your site URL to draft an llms.txt from its sitemap, or build one by hand. Review its links and descriptions, then check the result before using it. Last updated: September 5, 2026 ## Generator Generate from your site URL (reads sitemap.xml) Import mode Curated draft, recommended Full inventory, advanced Generate from sitemap Curated mode deterministically selects up to 30 useful candidates. Full inventory is available for advanced review, but a sitemap dump is not a finished llms.txt. Site or project name (H1) Summary (blockquote) Body (optional context, no headings) ### Sections + Add section ### Preview Copy Download ## Tips Note llms.txt v2 discovery A file may now describe a whole origin or only a subpath such as /docs/llms.txt . For pages with clean Markdown versions, expose them with rel="alternate" type="text/markdown" and point back to the applicable file with rel="describedby" . - Keep the summary factual: one or two sentences, no marketing claims. - Group items by product surface (Product, Pricing, Developers), not by content type. - One short note per item after the colon, disambiguation, not selling. - Use absolute URLs (`https://yourdomain.com/...`). - You can group supplementary resources in an `Optional` section. The v2 proposal does not require special handling for it. Note Validate after generating Once you have a draft, paste it into the validator to confirm it matches the spec. ## Next steps A generated file is a starting point, not a finished one. Run the result through the [validator](/validator/), then cut it back against [the best-practice rules](/best-practices/): a sitemap lists every page, and an llms.txt should list the few worth reading. [How to create llms.txt](/how-to-create/) covers deployment stack by stack, and [real-world examples](/examples/) show how established sites structure theirs.