About this tool
Create a reviewable llms.txt draft using the ordered Markdown structure proposed by llmstxt.org, with explicit resource titles, URLs, descriptions, and optional context.
LLMs.txt Generator creates the ordered Markdown profile described by the llmstxt.org community proposal: an H1 title, blockquote summary, optional non-heading context, and H2 sections containing titled resource links with optional descriptions. A generated Optional section retains the proposal's special shorter-context meaning.
- Generates an H1 title, blockquote summary, optional pre-section context, primary H2 link list, and special Optional section in proposal order.
- Parses Title | URL | Description rows and validates bounded text, headings, HTTP(S) URLs, credentials, duplicates, and reserved section semantics.
- Escapes Markdown link titles and destinations, then exports exact TXT and versioned JSON evidence only when input is valid.
- States that llms.txt is a community proposal and does not guarantee discovery, retrieval, indexing, ranking, citation, licensing, or crawler behavior.
How to use LLMs.txt Generator
Enter the project title, concise summary, optional context, and primary section heading. Add one resource per line as Title | HTTP(S) URL | Optional description, place secondary resources in the Optional list, resolve field errors, review warnings, and download the exact TXT or JSON evidence only after checking every link.
When this tool is useful
- After pruning low-value pages from a tool directory or content hub.
- When publishing a curated context entry point for documentation or product resources.
- When reviewing an existing llms.txt file against the proposal's link-list structure.
Practical tips
- List representative high-value pages, not every URL on the site.
- Give each resource a distinct title and a brief factual description instead of listing bare URLs.
- Use the Optional section only for resources that can be skipped when a shorter context is needed.
- Do not describe publication as guaranteed AI search discovery, ranking, or crawler control.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
Build an llms.txt file for a tool site
Example input
Title: Utiloom Summary: Focused browser-based workbenches... Primary resources: Tool directory | https://www.utiloom.com/tools | Browse the public catalog.
Expected output
# Utiloom > Focused browser-based workbenches... ## Primary resources - [Tool directory](https://www.utiloom.com/tools): Browse the public catalog.
The generated file follows the proposal's H1, blockquote, H2, and described Markdown link structure.
Catch weak discovery files
Example input
Primary resource: Unsafe | javascript:alert(1) Optional resource repeats the same normalized URL
Expected output
Field errors suppress the generated output, copy action, and TXT or JSON downloads.
The validator rejects malformed rows, non-HTTP(S) URLs, credentials, duplicate URLs, and reserved heading conflicts.
Validation checklist
- Confirm every linked URL is accurate, accessible to its intended audience, and useful as context.
- Confirm the file contains one H1 followed by its blockquote before any H2 resource sections.
- Review whether Optional resources can genuinely be skipped for a shorter context.
- Test the deployed response path and media type separately because this generator does not fetch or publish files.