Free llms.txt Tool
Free llms.txt Generator
Fill in a form and get a clean, copy-ready llms.txt that follows the current llms.txt proposal. Everything runs in your browser — nothing is uploaded.
llms.txt preview
# Enter a site or project name to generate your llms.txt The site/project name is the only required field.
Issues
- Enter a site or project name. It becomes the H1 and is the only required part of an llms.txt file.
Next step
Save this as llms.txt at your site root (/llms.txt), then validate it with the Free llms.txt Checker.
This tool only formats the text you enter — it does not fetch anything. llms.txt is an optional proposal (see llmstxt.org); it is not a web standard, not a replacement for robots.txt or sitemap.xml, and publishing one does not guarantee AI crawling, indexing, citation, ranking, or recommendation.
What is an llms.txt file?
llms.txt is a proposed convention — described at llmstxt.org — for a Markdown file that gives AI and LLM tools a short, curated map of a site’s most important content. Rather than making a model crawl and guess, you hand it a tidy list: the site name, an optional one-line summary, and links to the pages that best explain what you do.
It is optional. It is not a web standard, it is not required by search engines or AI systems, and it does not replace robots.txt or sitemap.xml. Publishing one is not a guarantee of AI crawling, indexing, citation, ranking, or recommendation.
How to create an llms.txt file
You can write it by hand in any text editor, or use the generator above. Either way the steps are the same:
1Name the site or project
This becomes the H1 (`# Name`). It is the only required part of an llms.txt file — everything else is optional.
2Add a one-line summary (optional)
A short `>` blockquote sentence describing what the site is and who it is for.
3Add a little context (optional)
One or two plain paragraphs. No headings here — the spec keeps this area free of `#` headings.
4Group key pages into sections
Each `## Section` holds a Markdown list of `- [Link title](https://full-url)` items, with an optional `: short note` after each link.
5Use the Optional section for secondary links
Links an AI tool can safely skip when it needs a shorter context go under `## Optional`.
6Save and validate
Copy the output, save it as llms.txt at your site root, and check it with the Free llms.txt Checker.
llms.txt format explained
The proposal defines an order for the file’s parts. Only the first is required:
- H1 project name — `# Name` — the single required element. A file that is only this line is still valid.
- Blockquote summary — Optional `>` line right after the H1 with a short description.
- Additional context — Optional Markdown paragraphs or lists (no headings) for extra background.
- H2 sections — Zero or more `## Section` headings, each grouping related links.
- Markdown link list — Under each section: `- [name](url)` is the required part; `: notes` after it is optional.
- Optional section — A conventional `## Optional` section for secondary resources an agent may skip.
A complete example (one valid shape among many — not the only correct layout):
# Example Company > Example Company builds developer tools for shipping software faster. This file points AI tools to the pages that best explain the product. ## Documentation - [Getting Started](https://example.com/docs/getting-started.md): Set up in five minutes - [API Reference](https://example.com/docs/api.md) ## Optional - [Blog](https://example.com/blog): Release notes and articles
Where should llms.txt be placed?
The usual place is the site root: https://example.com/llms.txt. The current proposal also allows an llms.txt at a subpath — for example /docs/llms.txt — to cover the URLs beneath that path. Where more than one file could apply, agents should use the most specific one. Serve the file as plain text and keep it publicly readable.
llms.txt vs robots.txt
robots.txt is an access-control signal: it tells crawlers which paths they may or may not fetch. llms.txt does the opposite job — it points interested tools toward your best content. They solve different problems, and an llms.txt does not change or replace your robots.txt rules. To review which crawlers your robots.txt allows, use the AI Crawler Robots.txt Checker.
llms.txt vs sitemap.xml
sitemap.xml is a complete, machine-readable list of every URL you want search engines to crawl. llms.txt is a short, curated, human-written summary of just your most important pages, in Markdown, aimed at AI tools. Keep publishing a sitemap; llms.txt is an addition, not a replacement.
Does llms.txt improve AI visibility?
There is no guarantee that it does. An llms.txt can make your key content easier for a tool to find and read if that tool chooses to use the file — but that is not the same as a ranking, citation, or recommendation benefit, and support varies by provider and changes over time. Treat any claim that publishing an llms.txt will get you ranked, cited, or recommended by a specific AI product with scepticism. It is a low-cost, optional courtesy, not a growth hack.
For the signals that more directly affect whether AI systems can reach and understand your site, see the ChatGPT Website Visibility Checker and Why ChatGPT Isn’t Recommending Your Website.
Frequently asked questions
What is an llms.txt file?
llms.txt is a proposed convention (documented at llmstxt.org) for a Markdown file that gives AI and LLM tools a short, curated map of a site's most important content: the site name, an optional summary, and links to key pages. It is optional and is not a web standard.
Is llms.txt required?
No. It is an optional proposal, not required by any search engine or AI system. A site without an llms.txt is not broken. Within the file, the only element the proposal calls required is the H1 project or site name.
Does llms.txt improve AI visibility, rankings, or citations?
There is no guarantee that it does. Publishing an llms.txt does not make an AI system crawl, index, cite, rank, or recommend a site. It can make your key content easier to locate and read if a tool chooses to use the file, which is a different thing from a ranking or citation benefit.
Where should the llms.txt file be placed?
Most commonly at the site root, as /llms.txt. The current proposal also allows an llms.txt at a subpath (for example /docs/llms.txt) to cover the URLs beneath that path; where more than one file applies, agents should use the most specific one. Serve it as plain text.
How is llms.txt different from robots.txt?
robots.txt tells crawlers which paths they may or may not fetch — it is an access-control signal. llms.txt does the opposite job: it points interested tools toward your best content. They are complementary, and llms.txt does not replace robots.txt.
How is llms.txt different from sitemap.xml?
sitemap.xml is a machine-readable list of all URLs you want search engines to crawl. llms.txt is a short, human-curated Markdown summary of your most important pages for AI tools. Keep publishing a sitemap; llms.txt is not a substitute.
What should I put in an llms.txt file?
Your site or project name, a short summary, and links to the pages that best explain what you do — documentation, key guides, product or API references, an about page. Link to clean Markdown (.md) versions where you have them, and keep the list curated rather than exhaustive.
Can llms.txt contain private information?
No. The file is publicly accessible, so anything in it is public. Do not include internal-only URLs, staging or admin links, credentials, or anything you would not publish on a normal page. This generator runs entirely in your browser and does not send your input anywhere.