llms.txt Generator
Build a valid llms.txt for your site — summary, background, and the links you want a model to read first. Everything runs in your browser; nothing is uploaded.
Your llms.txt
Save this as llms.txt at the root of your domain — it must be reachable at /llms.txt.
# Your Project ## Docs - [Getting started](https://example.com/docs): Install and first run
What llms.txt is for
Search crawlers have all the time in the world; a language model answering a question about your product does not. It has a context window, and it will fill that window with whatever it happens to fetch first — which, on most sites, is a marketing homepage full of navigation and social proof and very little of what the product actually does. llms.txt is a single Markdown file that fixes that: an H1 with your name, a one-line summary in a blockquote, optional background, and then curated sections of links with a short note on each.
The format is deliberately boring. It is Markdown so a model can read it without a parser, it is at a predictable path so nothing has to guess, and it is short so it costs almost nothing to include. The one rule worth respecting is the Optional section — by convention that is the part a model drops first when context is tight, so put the pages you would sacrifice there and nothing else.
What to include
Aim for the ten links that would let a competent stranger explain your product back to you. In practice that is your docs index, a quickstart, an API or pricing reference, one or two representative examples, and your changelog under Optional. Write the notes for a reader who has never heard of you: “Getting started” means nothing on its own, while “Getting started: install the CLI and index your first repo” carries real information at almost no token cost.
Skip anything gated, anything that 404s for logged-out visitors, and anything you would not want quoted back at you. And keep it current — a stale llms.txt is worse than none, because it confidently describes a product you no longer ship.
While you are shipping files
The same instinct applies to your meta tags and your social preview — machines read your site far more often than people do, and each of these is a five-minute job. If your product is live, list it on Launchory so humans can find it too, or browse what other founders have shipped and the developer tools category.
Questions people ask
What is llms.txt?
A plain-Markdown file at the root of your domain (/llms.txt) that tells large language models what your site is, in the order that matters. It is the same idea as robots.txt or sitemap.xml, but written for a model that has one shot at understanding your product rather than for a crawler indexing every page.
Where do I put the file?
At the root of your domain, reachable at https://yourdomain.com/llms.txt, served as text/plain or text/markdown. In Next.js, drop it in /public. In most static hosts, the root of your build output.
Does llms.txt actually do anything yet?
Adoption is early and no provider guarantees they read it. It costs you five minutes and one file, it cannot hurt you, and it is genuinely useful documentation for anything that fetches your site — including your own internal tools. Treat it the way you treated sitemap.xml before it was table stakes.
What should go in the Optional section?
Anything a model can skip when it is short on context — changelogs, archived posts, legal pages. The convention is that "Optional" is explicitly the first thing dropped, so put the pages you would sacrifice first there.
More free founder tools.