AI Search & GEO
llms.txt generator
llms.txt is a proposed standard (llmstxt.org): a markdown file at your site root that gives AI models a curated map of your site — what it is, in one line, plus the links that matter most. This generator builds a spec-compliant file from a simple form: fill in your site name, summary, and link sections, then copy or download the result.
Free · no signup
Your llms.txt
# Your site name
Upload it to your site root so it's served at /llms.txt.
How to use the llms.txt generator
-
Name and summarise
The H1 is your site or project name; the blockquote is a one-line summary — the two things every consuming LLM reads first.
-
Add link sections
Group your most useful URLs under H2 sections (Docs, Guides, Pricing, Policies). Each link takes an optional one-line note.
-
Upload to your site root
Serve the file at /llms.txt (next to robots.txt) and keep it updated as your docs move.
What is llms.txt?
llms.txt is a plain-markdown file served at /llms.txt that helps large language models use your site at inference time. Where robots.txt tells crawlers what they may fetch, llms.txt tells models what's worth reading: a name, a one-line summary, optional context, and curated sections of links with short notes.
The format is deliberately simple — an H1 for the name, a blockquote for the summary, H2 sections of markdown link lists — because it's designed to be parsed both by programs and by the models themselves. This generator produces exactly that structure.
Does llms.txt actually help?
Honestly: adoption is real but consumption is uneven. Thousands of sites publish one (Anthropic, Stripe, Cloudflare among them), several dev-tool crawlers and answer engines read them, and it costs you one static file. Major search crawlers haven't committed to it, so treat llms.txt as cheap insurance and a genuinely useful docs index — not a rankings lever.
The stronger play is doing both: publish llms.txt for the agents that read it, and fix the GEO fundamentals (crawler access, structure, schema, answer-shaped copy) that every AI engine uses today.
Frequently asked questions
Where do I put the llms.txt file?
At your site root, so it's reachable at https://yourdomain.com/llms.txt — the same place as robots.txt. On most static hosts that means dropping it in your public/ or static/ folder.
What's the difference between llms.txt and robots.txt?
robots.txt is access control: it tells crawlers which URLs they may fetch. llms.txt is curation: it tells AI models which pages best explain your site, in a format they can read directly. They complement each other — one gates, the other guides.
What should I link in my llms.txt?
The pages you'd want an AI assistant to read before answering questions about you: getting-started docs, pricing, API reference, key product pages, and policies. Skip marketing fluff — the file works best as a dense, honest index.
Is there also an llms-full.txt?
The spec allows a companion llms-full.txt containing full page contents inlined as markdown, for models that want everything in one fetch. Start with llms.txt; generate the full variant later if your docs tooling supports it.