llms.txt v2 · inspect, validate, and build

Create a concise agent-readable map without calling it an AI ranking control

Inspect a public root or scoped llms.txt file, validate the proposal’s Markdown order, resolve every file-list link, check referenced responses, or generate a clean UTF-8 file from your own editorial choices.

PROPOSALV2FILE LIMIT512 KBLINK CHECKS50 MAX
CHECK OR PASTE

Inspect a root or path-scoped llms.txt file

A scope such as /docs/ resolves to /docs/llms.txt. Entering an exact llms.txt URL checks that file directly.

The parser accepts an optional BOM, requires one H1 as the first content, allows an optional blockquote and non-heading preamble, then reads H2 file-list sections.

TXT

Ready for a public file or pasted source.

No adoption score, AI visibility estimate, citation promise, or generated site description appears before you provide evidence.

UTF-8 GENERATOR

Build the file from editorially chosen resources

The generator writes the v2 order exactly and never invents descriptions, priority, or page selections.

FILE LISTS

Each row uses title, URL, and optional description in tab-separated columns.

Empty file-list sections are omitted. Up to 8 sections and 200 links can be generated.

Implementation notes

Keep discovery, permission, and content quality separate

Curate a small map

Link to stable, useful, preferably Markdown-friendly resources. A sitemap remains the complete search-discovery inventory.

Declare relations where useful

The v2 proposal recommends standard alternate Markdown and describedby link relations in HTML or HTTP headers.

Retain real controls

Use robots.txt and provider-specific controls for crawler access or training preferences. llms.txt provides context; it grants and denies nothing.