llms.txt Generator & Validator
Create a resource index, lint pasted Markdown or validate a public llms.txt URL with clear structural findings.
Useful knowledge. A clearer way in.
IN YOUR BROWSER / PRIVATE INPUTGood input. Useful output.
Create a resource index, lint pasted Markdown or validate a public llms.txt URL with clear structural findings.
Try the example, or make it your own.How to use the
llms.txt Generator & Validator
- 01
Choose the task
Select the relevant mode in the llms.txt Generator & Validator workspace. The controls describe the accepted input and output.
- 02
Name and summarize the resource
Enter the real website or documentation name and a short description of what it offers. Avoid turning the summary into a collection of promotional keywords.
- 03
Choose a focused set of links
Enter label | URL | description on each line. Prefer stable documentation, important guides and clear identity pages over a dump of every route.
A small resource index with a predictable shape
The generator produces this simple resource-index format. It does not crawl your website, create Markdown copies of pages or implement every extension in the evolving llms.txt proposal. Labels are cleaned for basic link syntax and URLs are checked as absolute HTTP or HTTPS addresses.
| Part | Generated form | Editorial purpose |
|---|---|---|
| Title | One # heading | Identify the site or resource collection. |
| Summary | A > blockquote | Explain what a reader will find. |
| Resource section | ## Resources | Group the selected links. |
| Resource item | A labeled Markdown link and description | Explain why that destination matters. |
Make a resource list useful without opening every link
A label names the destination; a description tells the reader when to use it. This is more informative than several bare URLs or a repeated instruction to read more.
Name: North Docs
Summary: Guides for installing and maintaining North.
Resource: Installation | https://example.com/docs/install | Start with a new project# North Docs
> Guides for installing and maintaining North.
## Resources
- [Installation](<https://example.com/docs/install>): Start with a new projectWhat llms.txt adds, and what it does not replace
The llms.txt proposal describes a way to provide concise context and resource links for automated use. This generated file is an optional guide, not an access-control mechanism. It does not replace robots.txt, authentication, an XML sitemap or the actual content on your pages.
A file's existence does not prove that a particular AI system retrieved it, indexed the linked resources or cited your site. Keep important information available in the pages themselves. If you provide Markdown versions of documentation, verify that they remain consistent with the published source rather than becoming a second stale copy.
Curate the file like a useful introduction
Choose entry points, not every leaf
A concise getting-started guide can be more helpful than hundreds of unorganized links. Organize a large knowledge base at a level someone can navigate.
Write descriptions with a purpose
Explain whether a resource covers installation, API behavior, limitations or troubleshooting. Distinct descriptions make the list easier to scan.
Use stable, public destinations
Avoid expiring signed URLs and links that require a session unless you deliberately document that limitation. The generator does not test reachability.
Assign maintenance ownership
Update the file when resources move or become obsolete. An outdated guide can point a client toward the wrong documentation even when the file itself is well formatted.
The linter's complete checklist
These rules describe this tool's resource-index lint profile. They are not a universal certification for every version or extension of the llms.txt proposal. A valid prose bullet in a more elaborate document can trigger a profile warning because this linter expects resource links in bullet items.
| Check | What is tested | What a failure suggests |
|---|---|---|
| One top-level title | Exactly one Markdown line beginning # and text. | Add a single site title or remove duplicate H1 headings. |
| Short summary | A nonempty > blockquote line exists. | Add a concise introduction beneath the title. |
| Resource sections | At least one ## heading exists. | Give the resource list a descriptive section. |
| Resource links | At least one labeled Markdown link is found. | Check bracket and parenthesis syntax. |
| Link URL syntax | Each recognized URL parses as absolute HTTP(S). | Replace relative or unsupported URL forms. |
| Resource list syntax | Bullet lines follow the expected resource-link pattern. | Review non-link bullets and malformed list entries. |
A plausible-looking link can still use the wrong URL form
The Markdown brackets are correct in both examples, but the first destination is relative. The linter requires an absolute HTTP or HTTPS URL so the resource has an unambiguous address outside the current page context.
- [Installation](/docs/install): Start here- [Installation](https://example.com/docs/install): Start hereA clean lint result is not proof of AI readiness
Structure looks good means the implemented checks passed on the pasted text. It does not mean the file is hosted at the expected path, returned as plain text, linked from your pages or consumed by an AI provider. It also does not assess the accuracy of the resource descriptions.
The parser looks for a practical subset of Markdown link syntax. It is not a full Markdown conformance engine and does not evaluate every possible reference-style or complex link construction. For predictable output, use the simple inline resource-link pattern shown in the example.
Separate file structure from publication checks
Check the text before the URL
A structural failure belongs in the file. A 404 at /llms.txt belongs in routing or deployment. Treat these as separate problems so the repair is focused.
Keep the guide useful to a human
Distinct labels and honest descriptions matter even when the syntax passes. Read the file without opening the links and see whether it provides orientation.
Review proposal changes intentionally
The proposal can evolve faster than a simple local linter. Compare warnings with the format you intend to support rather than deleting valid content solely to satisfy this profile.
Test links outside the linter
Open the public resource URLs and check redirects or authentication. This tool intentionally performs no network requests for links.
Validate the published text, not just your draft
Choose Validate URL for a public llms.txt address. HTTP and HTTPS redirects are validated at every hop. Private targets, robots restrictions, bot challenges, oversized responses and timeouts produce clear errors instead of a score.
The fetched file uses the same local structural profile as pasted text. Its links are parsed for absolute URL syntax; successful validation does not establish their reachability or provider adoption.
llms.txt Generator & Validator:
questions, answered.
Will an llms.txt file improve my AI citations?
No citation outcome is measured or guaranteed. The file is a structured guide to resources; provider behavior and answer selection are outside this tool's control.
Does this generator create llms-full.txt too?
No. It creates a concise link index named llms.txt. It does not concatenate your site content or create a full documentation export.
Can llms.txt stop a model from training on my site?
No. It is not an access or licensing enforcement mechanism. Review crawler policies and the relevant provider's controls separately.
Is the generated file a complete implementation of every current proposal feature?
No. It implements the simple title, summary and resource-list pattern. The proposal evolves; review its current documentation for optional metadata, discovery links and other features your site may need.
Does this validator check whether resource URLs return 200?
No. It checks whether recognized links contain absolute HTTP or HTTPS URLs. Reachability, redirects and the content at those URLs need a separate check.
Why is a normal bullet paragraph reported as a finding?
This linter expects bullet items to be resource links. It may flag other valid Markdown constructions. Interpret that as a mismatch with this lint profile, not proof that all llms.txt consumers reject the file.
Does passing guarantee compliance with the latest llms.txt proposal?
No. The tool checks the disclosed resource-index structure. Review the current proposal for features and conventions beyond those checks.
Can I validate a public llms.txt URL?
Yes. Validate URL retrieves a bounded public text file with DNS, redirect, robots, size and timeout checks. Resource links are checked syntactically; they are not crawled.
The calculations and checks above describe this tool's implementation. Use these primary references for the underlying formats and publishing guidance.
llms.txt format and proposal ↗ (opens in a new tab)Put llms.txt Generator & Validator to work.
Create a resource index, lint pasted Markdown or validate a public llms.txt URL with clear structural findings.
Use the llms.txt Generator & Validator↑