llms.txt Generator

An llms.txt file is a markdown map of your site for AI agents: a name, a one-line summary, and sections of links with short descriptions. Writing it by hand for a site with a few hundred pages is tedious, so this tool reads your sitemap, or takes the pages you type in, and drafts it for you. Nothing is stored. The output is yours to edit and publish. At Layer3Labs, we ship one on this site and on the properties we run. Once the file is live, our free AI visibility checker confirms it loads and shows how ready the rest of your website is for AI search, and the free llms.txt checker tests the file against the format line by line.

Generate Your llms.txt

How to Use the llms.txt Generator in Four Steps

You make an llms.txt file by choosing a site preset, adding your key pages, describing your site, then checking and downloading the file.

1. Pick a preset. Select the preset that matches your site, such as Software / SaaS, Online store or Agency / services firm, to load its sections and path-sorting rules.
2. Add your pages. Import up to 60 pages from a sitemap, paste a list of URLs, or fill in rows manually with your page titles and descriptions.
3. Describe your site. Type the site name for the H1, a one- or two-sentence summary, and any key facts.
4. Check it, then download. Fix anything the live checks flag, such as placeholder copy or empty starter rows, then save llms.txt and upload it to your server root so it resolves at yourdomain.com/llms.txt.

Read our platform installation guide for host-specific upload instructions, and verify the live file using the llms.txt checker.

What the Generator Builds

The generator writes a plain-text markdown file in the llms.txt format, laid out with the sections of the preset you pick.

The output follows the llms.txt format that Jeremy Howard published on September 3, 2024 and revised as v2 in August 2026. Under the proposal, the file sits at the root path /llms.txt and should be small enough to fit in context, with detail behind the links. The proposal names no required HTTP (Hypertext Transfer Protocol) content type, and sites commonly serve the file as text/plain or text/markdown. An H1 heading containing the site or project name is the only required part of the document.

• H1 site name: The name of your website or project, rendered as the single required top-level H1 heading at the start of the file.
• Blockquote summary: A concise summary of your platform or business, positioned immediately beneath the H1 heading inside markdown blockquote syntax.
• Key facts: One fact per line, placed under the blockquote as detail text. The generator strips any heading you type there, because the format allows no headings in that part of the file.
• H2 sections: Category headings holding markdown links written in the standard - [name](url) format, and an optional note after each link. Imported pages use their own meta description as the note, and you can type or edit any note.
• Optional section: Every preset adds an H2 named Optional last, for secondary pages such as privacy policies, terms and careers. The llms.txt proposal treats it as a convention: an agent can skip those links when it needs a shorter context.

llms.txt Best Practices

A good llms.txt file sits at the root path, follows the H1, summary and link-list layout, and gives every link a full URL and a short note.

• Publish at the root path. The file sits at the root path /llms.txt, though a site section can have its own.
• Keep the file small enough to fit in context. The proposal states the file should be small enough to fit in context, with detail behind the links.
• Follow the llms.txt layout. Start with a single H1 containing your project name, followed directly by a blockquote with a short summary.
• Omit headings from the key-facts section. Place background details in paragraphs or lists without headings, because the format allows no headings there.
• Use full URLs for every entry. Write each link as a full URL, such as https://example.com/pricing, so it still works when an agent reads the file away from your site. Enter your site URL and the generator turns /pricing into a full link.
• Add descriptive notes to link rows. Add a few words after each link in the form - [name](url): notes, so an agent can pick the right page without opening every link.
• Place secondary pages under an Optional section. An H2 section named Optional tells an agent which links to skip when working within shorter context limits.
• Serve the file as clean plain text. The proposal names no HTTP content type, but sites commonly serve it as text/plain or text/markdown.
• Update when site sections expand. The generator creates a plain-text file, and the file does not update itself.

The common llms.txt mistakes section of our explainer lists the errors to avoid, and the llms.txt checker tests your live file against the same rules.

How to Install It

Copy the output into a file named llms.txt and put it where your site serves static files: the public/ folder on Astro or Next.js, the web root on a plain host, or the static-files location your platform exposes. Load yourdomain.com/llms.txt in a browser. It should return the plain text with a 200 status. Keep it “small enough to fit in context” and put detail “behind the links,” as the spec puts it. Regenerate it when you add a section. You do not need to touch it for every post.

Does llms.txt Work?

It is a proposal, published by Jeremy Howard in September 2024. The spec page makes no claim about ranking or citations, so treat it as a low-cost map for agents rather than a ranking lever. It costs a few minutes and removes the guesswork for any agent trying to understand your site, which is why we publish one on this site and the properties we operate. The llms.txt explainer walks through what the major engines have said and what belongs in the file.