FREE TOOL

Free llms.txt generator

Give it your site’s name, a short summary and the pages that matter, or paste your sitemap, and it writes an llms.txt in the llmstxt.org format for you to copy or download. There’s no charge and no sign-up, and the file is built in your browser, so nothing you type is sent anywhere.

It comes from Deacon, an AI support agent that answers the people on your site from your own docs and shows you where they get stuck. Deacon has a free plan.

Finishes any link you write as a path, such as /pricing.

Open your sitemap.xml in your browser and copy all of it, or paste one address a line. Each folder becomes a section below.

Write each link as a title, its address and a note, split by a bar ( | ), or give just the address. A Markdown list pasted in works too. Name a section Optional for links an agent can skip, and it goes last.

6 links in 3 sections, ready to copy.

Save it as llms.txt at the root of your site, so it opens at yoursite.com/llms.txt. Nothing you type leaves your browser.

How to make an llms.txt with this generator

  1. Type your site or product’s name. It becomes the file’s heading, and it’s the one part the format can’t do without.
  2. Write a summary of a sentence or two, saying what the product does, who it’s for, and anything an agent would get wrong unless told. Notes that don’t fit go under More details, such as which page to trust for prices.
  3. Add your links in sections, such as Docs, API and Product. To start from your sitemap or a list of addresses, paste it into the box above the sections and press Sort into sections. Then cut the pages an agent has no use for, and fix any title made from an address.
  4. Put links an agent can do without, such as your changelog or blog posts, in a section called Optional. It goes last in the file.
  5. Copy the file or download it, and upload it to your site’s root so it opens at yoursite.com/llms.txt.

Choosing the pages is the real work, and it’s the same choice you’d make for a support chatbot. Our guide to setting up an AI chatbot for documentation says which pages to keep and which to leave out, such as release notes and docs for old versions.

What goes in an llms.txt file

An llms.txt is a Markdown file that gives AI agents a short guide to your site. The format comes from the llms.txt proposal by Jeremy Howard, and we read its second version on 15 October 2026. It sets out these parts, in this order.

  • A heading with the site or project’s name, after a single #. It’s the only part the format requires.
  • A short summary on a line starting with >, holding what an agent needs to make sense of the rest.
  • Any notes you like, as paragraphs or lists, but with no headings.
  • Sections under ## headings, each a list of links written as [name](address), with an optional colon and a note after each one.
  • By convention, a section called Optional, for links an agent can skip when it needs a shorter read.

The proposal also suggests a clean Markdown copy of each page an agent might need, at the page’s own address ending in .md, and pointing your llms.txt at those copies. If your docs platform makes them, use their addresses in your links. The file itself should stay short, with the detail behind the links.

Who reads llms.txt, and who doesn’t

Google Search doesn’t. Its guide to optimising for its generative AI features says you don’t need machine-readable files such as llms.txt to appear in Google Search, its AI features included. An llms.txt will neither help nor harm your visibility or rankings in Google Search, it says, as Google Search ignores it.

Chrome’s Lighthouse, also from Google, looks for the file among its agentic browsing audits. It flags a page when a server error stops it fetching the file, and marks a site with no llms.txt as not applicable, since the file is optional for now.

The readers it was written for are agents. The proposal says llms.txt files are used most for software documentation, where coding agents follow them to the API references and tutorials they need. So write yours for a developer whose agent is building with your product. If you have an API, an SDK or setup steps, the file earns its keep. If your site is a few marketing pages, keep it short.

Ours is at heydeacon.com/llms.txt. It tells a coding agent where to read our install guide and our guide to sending goals, then lists every page in our resources and every feature page. For anything about Deacon itself, it sends the agent to our plain facts for AI assistants, which say what Deacon does and doesn’t do in full sentences.

Your customers won’t read your llms.txt

An llms.txt helps an agent find its way round your docs. The people using your product ask in their own words instead, on your pricing page or halfway through setup, and they won’t open the file. Deacon answers them. It’s an AI support agent for founders who handle support themselves, and it replies in a chat on your site in seconds, from the same pages you’d list in your llms.txt. When those pages don’t cover a question, it says it doesn’t know rather than guess.

  • Deacon points you at what to build next. Topics gather what people ask into groups, show how many people are behind each one, and label a group a feature ask or a bug report when more of its questions are that kind than any other.
  • You see what was asked on each page. Analytics › Website lists your most visited pages with the questions asked on each and how many went unanswered, and the Unanswered filter in Conversations gathers what your docs didn’t cover.
  • Those gaps become your to-do list. A question your docs missed gets an Answer this button, and what you write becomes a source Deacon answers from.
  • It suits sites made with AI app builders. You add it with one script tag, and Install has its own steps for Lovable, Bolt, Replit and Base44.

Deacon starts from your home page and up to four main pages, such as pricing and help, and you can add any other page by its address. How Deacon answers from your docs goes through it step by step, and every feature is on the free plan.

Questions about llms.txt

A form that writes an llms.txt file for you, laid out the way the llmstxt.org proposal sets out. This one builds the file from what you type or paste, so you choose every page and write every note, and nothing is guessed from your site.

Write a Markdown file that opens with your site’s name after a #, then a short summary on a line starting with >, then sections under ## headings that list links to your key pages. Save it as llms.txt and upload it to the root of your site. The generator above does the formatting, so the only work left is choosing the pages.

No. Google’s guide to its generative AI features says Google Search ignores llms.txt files, and that making one will neither help nor harm your visibility or rankings in Google Search. It also says you don’t need one to appear in Google Search, its AI features included.

AI agents working for someone. The proposal says the files are used most for software documentation, where coding agents follow them to API references and tutorials, and that an agent reads the file when it needs to know something while helping a person, then follows the links it needs.

At the root of your site, so it opens at yoursite.com/llms.txt, the way robots.txt and sitemap.xml do. A file at a deeper path, such as /docs/llms.txt, covers only the pages under that path. Check your platform first. Wix says it writes and keeps up an llms.txt for your site, and on WordPress the Yoast SEO and AIOSEO plugins can write one.

robots.txt tells automated tools which parts of a site they may visit, and sitemap.xml lists every page you want search engines to index. An llms.txt is a short, chosen guide with notes, read when an agent needs it. It doesn’t allow or block anything, and it can link to pages on other sites, which a sitemap doesn’t.

No. It never fetches a site, which is how nothing you type leaves your browser. Open your sitemap instead, often at yoursite.com/sitemap.xml, copy the whole page and paste it into the box above the sections. A sitemap that only lists other sitemaps needs each of those pasted in turn.

Yes. There’s no sign-up and no limit on how many files you make. It keeps nothing either, so your file is gone when you reload the page. Copy or download it first.

Try Deacon for free

Your llms.txt points agents at your docs. Deacon answers your customers from the same docs, and shows you what they asked.

READ NEXT