Documentation Tools
llms.txt Generator
Create a curated list of public documentation links in the proposed llms.txt format.
Worked example and publication checksLive generator
Generate llms.txt
llms.txt is ready.
From input to publication
Worked example: a documentation entry point
A fictional project has an installation guide and an API reference. Its llms.txt should help a reader find those documents, not repeat an entire sitemap or promise visibility in an AI answer.
Example inputs
- Website name
- Project Board
- Website URL
- https://example.com/
- Description
- Documentation for Project Board.
- Important pages, one per line
- https://example.com/docs/install.md https://example.com/docs/api.md
Expected llms.txt
# Project Board
> Documentation for Project Board.
## Website
- [Homepage](https://example.com/)
## Important pages
- [/docs/install.md](https://example.com/docs/install.md)
- [/docs/api.md](https://example.com/docs/api.md)Publish documents before listing them
The .md URLs in this example stand for actual public Markdown documents. Adding .md to an HTML URL does not create such a file. Open each destination without an authenticated session and confirm that it returns the intended document, not a sign-in page or an HTML error.
For a small business without Markdown documentation, start with the useful public pages that really exist. Do not invent URLs to make the file look more complete. The page labels in this generator come from the URL path; you can replace them with descriptive names in the downloaded or copied text.
Choose links by the question they answer
The installation guide answers how to begin; the API reference answers how to integrate. A pricing or support page can be added when it resolves a likely follow-up question. Session URLs, account settings and temporary search results do not help a public documentation entry point.
The file is served at /llms.txt in this example. Use a plain-text or Markdown response, check that HTTPS works, and test the final URL after deployment. A cache may otherwise continue serving an earlier revision.
Test meaning as well as formatting
A Markdown link has a label in square brackets and its destination in parentheses. Check that both links in the example survive copying. Then ask a reader to locate the installation instructions using only this file. If the relevant document is hard to find, improve the selection or labels rather than adding more URLs.
This is an evolving community proposal, not a robots access rule or a guaranteed ranking signal. Keep normal navigation, robots.txt and the sitemap maintained independently.
Verification checklist
- Compare the complete generated file with the example.
- Check both destinations and /llms.txt after publication.
- Remove any private paths or access tokens before sharing the file.
- When a guide moves, update the link and keep a redirect for existing readers.
Example and source review: .
What this tool is for
llms.txt is a community proposal for a Markdown directory of useful public pages. A tool that supports the proposal can use that directory as an entry point to documentation. Publishing the file does not establish that a particular AI provider will read it or improve your visibility.
Use this generator when you want to curate a small set of documentation links. It formats the website name, description and URLs you supply; it does not crawl those URLs, create Markdown versions of pages or test provider support. Your normal navigation, sitemap and robots.txt still have separate jobs.
How to use it
- Enter the website name and a short description of what the site offers.
- Add one important public URL per line, such as your documentation, pricing, support, or product pages.
- Generate the draft and remove anything that is outdated, private, duplicated, or not helpful for external users.
- Upload the final text file as /llms.txt on the same domain and link to it from technical documentation where useful.
Other use cases
Small software product
List the homepage, pricing page, documentation index, API reference, changelog, and support page. Leave out thin landing pages and campaign pages that do not explain the product better than the main pages.
Agency or service business
List the public service, process and contact pages that answer useful questions about the business. The list is a directory for readers and compatible tools, not evidence that an AI provider will use it.
Knowledge base
Point to the best category pages and canonical guides instead of adding every article. A short curated list is easier to maintain and usually more useful than a complete URL dump.
Important notes
- Keep the file honest and descriptive. Do not claim official support by AI providers unless you can verify it.
- Prefer stable canonical URLs. Temporary campaign pages, search result pages, and duplicated filtered pages usually do not belong in the file.
- Review the file after major website changes. A stale llms.txt can create more confusion than having no file at all.
Limitations
- Publishing llms.txt does not guarantee that any AI system will read, index, rank, or cite your content.
- The file is public. Do not include private URLs, internal notes, customer data, tokens, staging paths, or confidential documentation.
- The generator creates a draft. The final selection of URLs still needs editorial review.
Sources and review context
This page is maintained by Martin Trixner and was last reviewed on September 9, 2026. The tool output is based on public documentation and should still be tested against the target platform before production use.
FAQ
What is an llms.txt file?
An llms.txt file is a proposed way to provide AI systems with important pages, descriptions, and documentation areas in a structured format.
Where should the file be placed?
It is commonly placed in the root directory of the domain, for example at /llms.txt.
Is llms.txt the same as robots.txt?
No. robots.txt gives crawler access instructions, while llms.txt describes useful public content for AI systems and tools.
Should every page be listed?
No. The file is more useful when it highlights canonical, high-value pages instead of repeating the full sitemap.
Can I include private documentation?
No. The file is public and should only reference content that is safe for external users and crawlers.
How often should llms.txt be updated?
Review it after major navigation, product, documentation, or policy changes so stale links do not remain in the file.