LLMs.txt Generator

llms.txt is a markdown file, usually at the site root, that points assistants at the pages you want them to read. The title is an H1, the summary is a blockquote, and each group of links is an H2 followed by markdown links. Notes sit under the summary as plain paragraphs.

Project name is one of the values LLMs.txt Generator puts on screen. The H1 of the file. It is required. An empty name does not produce a file. Use the public name of the site or project.

Notes answers a narrower question than the headline number. Plain paragraphs under the summary. They are optional. They are not H2 sections.

The Download line is worth a full stop. The browser saves llms.txt. Nothing is published for you. Upload the file to the site root after you download it.

If you remember one sequence from LLMs.txt Generator, remember the fields in the order they change a decision. Project name matters because The H1 of the file. In practice, It is required. An empty name does not produce a file. The mistake to avoid is this: Use the public name of the site or project. Summary matters because A blockquote under the title. In practice, One paragraph is the intended length. The mistake to avoid is this: Do not paste the whole homepage. Notes matters because Plain paragraphs under the summary. In practice, They are optional. The mistake to avoid is this: They are not H2 sections. Link row matters because A markdown link inside a section. In practice, Name and absolute URL are required for the row to be useful. A blank description drops the colon. The mistake to avoid is this: Relative URLs are the wrong shape for this file. Download matters because The browser saves llms.txt. In practice, Nothing is published for you. The mistake to avoid is this: Upload the file to the site root after you download it. After that, the checks are simple. The project name is filled. The summary is one paragraph. Every kept link is http or https. Blank descriptions did not leave a stray colon. The file will be uploaded to /llms.txt by you, not by this page.

Keep LLMs.txt Generator as this step only. When the job moves on, the LLMs.txt Checker + Validator is the next page: LLMs.txt Checker reads llms.txt markdown you paste and returns a pass, warning, or fail for the title, summary, sections, and links. The Sitemap to LLMs.txt covers a different piece of the same work: Sitemap to LLMs.txt turns pasted sitemap XML or a list of URLs into an llms.txt file.

The file starts with an H1 title, then a blockquote summary, then optional note paragraphs, then H2 sections of markdown links. Each link has a name and an absolute http or https URL. A description is added only when you type one, as a colon and the description after the link. An empty row is skipped.

Read Summary on its own before you mix it with the other rows. A blockquote under the title. One paragraph is the intended length. Do not paste the whole homepage.

Treat Link row as a label with a specific job. A markdown link inside a section. Name and absolute URL are required for the row to be useful. A blank description drops the colon. Relative URLs are the wrong shape for this file.

Publish the file at the site root so a person or an agent can request /llms.txt. The generator does not upload it. Keep the summary to one paragraph. The file is a guide to pages worth reading. It does not replace the sitemap or the page content.

The worked example for LLMs.txt Generator, read as one scene, is this. Project name Example, summary A sample project, notes Extra context for editors, section Docs, link Guide at https://example.com/guide with description How to start, and a second link About at https://example.com/about with a blank description. The file starts with # Example, a blockquote of the summary, the note paragraph, ## Docs, then a described link and a link with no colon. An empty link row is absent from the download. A relative URL such as /guide is not the form this file wants. Use https.