Free llms.txt Generator: What llms.txt Is and How to Create One

A developer built a free, no-account llms.txt generator that reads a site's sitemap and produces a spec-style /llms.txt file in seconds, plus an optional llms-full.txt containing short excerpts of every page. The tool follows the llms.txt proposal introduced by Answer.AI's Jeremy Howard in September 2024 and updated to v2 in August 2026, which defines a Markdown index with an H1 name, a blockquote summary and H2 sections of links, including an optional section agents can skip. The developer notes the file does not directly improve Google rankings, since Google says no special machine-readable files are needed for AI Overviews, but can help agents that choose to fetch it.

Cross-posted from my blog. The original, with any updates, lives on fabwaseem.com https://www.fabwaseem.com/blog/llms-txt-generator . An llms.txt generator builds the /llms.txt file that tells AI agents and chat assistants what your site is and which pages matter. I built a free one that reads your sitemap and writes a spec-style file in a few seconds, with no account: open the free llms.txt generator https://tools.fabwaseem.com/t/llms-txt-generator . It also writes an optional llms-full.txt with a short excerpt of every page. This guide explains what llms.txt is, what it does and does not do for SEO, the exact format from the official proposal, how to use the generator step by step, how to serve the file from Next.js, and how to check that it works. llms.txt is a Markdown file at the root of a website /llms.txt that gives large language models a short, curated map of the site. It starts with an H1 name and a one-line summary, then lists the important pages as Markdown links with notes. Agents read it to find the right page without parsing the whole site. The format was proposed by Jeremy Howard of Answer.AI on September 3, 2024, and the llms.txt proposal https://llmstxt.org/ was updated to v2 in August 2026. The proposal lives in an open GitHub repository https://github.com/AnswerDotAI/llms-txt . Definition: llms.txt is a Markdown index for AI agents, placed at /llms.txt or at a subpath such as /docs/llms.txt , that summarizes a site and links to its most useful pages. llms-full.txt is a common companion file that includes the content itself, or excerpts of it, in one document. TL;DR /llms.txt with an H1, a blockquote summary and H2 sections of links. Optional section marks links an agent can skip. llms.txt is used to give AI agents a fast, clean starting point. A coding agent can read a library's llms.txt to find the right API page. A chat assistant browsing your site can read it to learn who you are and where your pricing, docs or blog live. It saves tokens because the agent skips navigation, ads and scripts. The proposal says the files are used most heavily for software documentation, and that the AI labs publish their own: OpenAI developers.openai.com/llms.txt https://developers.openai.com/llms.txt , Anthropic docs.anthropic.com/llms.txt https://docs.anthropic.com/llms.txt and Google's Gemini API docs ai.google.dev/gemini-api/docs/llms.txt https://ai.google.dev/gemini-api/docs/llms.txt . It also lists platforms that generate the file automatically, including Mintlify, GitBook, Yoast SEO, AIOSEO and Wix. Typical uses: | Site type | What llms.txt points to | |---|---| | Developer docs | Quick start, API reference, SDK guides, changelog | | SaaS product | Product overview, pricing, features, docs, support policy | | Personal or portfolio site | About, projects, CV, contact, best articles | | Blog or publication | Pillar articles, topic hubs, author page | | Store | Category pages, shipping and returns policy, size guides | llms.txt does not directly improve Google rankings. Google's guidance on AI features and your website https://developers.google.com/search/docs/appearance/ai-features says there are no extra requirements for AI Overviews or AI Mode and that you do not need new machine-readable files or AI text files to appear in them. Its value is for agents that choose to read it. So be honest about the trade-off. llms.txt costs a few minutes to publish and can help any assistant or coding agent that fetches it. It will not replace the basics that every AI answer engine still depends on: crawlable pages, a sitemap, clear titles, structured data that matches the page, and content that answers the question in its first lines. If you want to check those basics, run your site through the free AI SEO checker https://tools.fabwaseem.com/t/ai-seo-checker ; it also checks for llms.txt. The format, from the official proposal, is Markdown sections in a fixed order: an optional byte-order mark, an H1 with the site or project name the only required part , a blockquote summary, optional paragraphs or lists with no headings, then zero or more H2 sections that each contain a list of name url links with optional : notes . Here is the shape: Site name One-sentence summary with the key facts an agent needs. Optional notes about how to read the links below. Docs - Quick start https://example.com/docs/start.md : Install and first request - API reference https://example.com/docs/api.md : Every endpoint and parameter Optional - Changelog https://example.com/changelog Rules worth remembering: | Element | Required? | Rule | |---|---|---| | H1 Name | Yes | The only required section | | Blockquote summary | No | Short summary with key facts | | Free text | No | Paragraphs or lists, no headings | | H2 file lists | No | Markdown list of name url : notes | | Optional | No | By convention, links an agent can skip | | Location | Yes | /llms.txt at the root or any subpath | The proposal also suggests offering a clean Markdown version of important pages at the same URL with .md added, and linking them with rel="alternate" type="text/markdown" . That is optional, and many sites start with the index alone. robots.txt says which crawlers may fetch which paths. sitemap.xml lists every indexable URL for search engines. llms.txt is a short, curated Markdown guide for AI agents with notes about each link. llms-full.txt is a larger companion that holds page content or excerpts in one file, so an agent can read everything in a single request. | File | Purpose | Audience | Format | Size | |---|---|---|---|---| | robots.txt | Allow or block crawling RFC 9309 https://www.rfc-editor.org/rfc/rfc9309.html | All crawlers | Plain text directives | Tiny | | sitemap.xml | List every indexable URL sitemaps.org https://www.sitemaps.org/protocol.html | Search engines | XML | Can be large | | llms.txt | Curated map with notes | AI agents and assistants | Markdown | Small, fits in context | | llms-full.txt | Content or excerpts in one file | AI agents | Markdown | Larger | The proposal makes the same point: a sitemap often lacks LLM-readable versions, leaves out helpful external links, and is usually too big to fit in a model's context window. llms.txt is the short version. Enter your homepage URL in the free llms.txt generator https://tools.fabwaseem.com/t/llms-txt-generator . It reads Sitemap: lines in your robots.txt, then your sitemap falling back to homepage links , visits up to 30 pages, groups them into sections and writes llms.txt plus llms-full.txt. Review the preview, edit it, then copy or download it. Step by step: https://example.com , and run it. The tool reads robots.txt for Sitemap: entries, then the sitemap. If there is no sitemap, it uses links from your homepage. /blog/ or /articles/ under /docs/ -style API paths under /pricing and /features under /about and /careers under llms.txt , and llms-full.txt if you want it. The full file adds a short excerpt up to about 800 characters of each page. https://yourdomain.com/llms.txt and confirm it loads as plain text. What the tool does and does not do, so you know the limits: | Behavior | Detail | |---|---| | Pages read | Up to 30 pages per run, up to 300 sitemap URLs considered | | Sources | robots.txt Sitemap: lines, sitemap index up to 4 child sitemaps , homepage links | | Safety | Public http/https only; private, loopback and link-local addresses refused after DNS | | Limits | 8-second timeout per request, size caps per file, a few runs per visitor every 10 minutes | | Output | Editable llms.txt and llms-full.txt, copy and download | | Account | None, free | In the Next.js App Router, either put a static llms.txt file in the public/ folder, or create a route handler at app/llms.txt/route.ts that returns the text with a text/plain content type. The route handler is better when your pages come from a CMS, because the file stays in sync with your content. Static option: save the generated file as public/llms.txt . Next.js serves it at /llms.txt . Dynamic option: js // app/llms.txt/route.ts import { getPublishedPosts } from "@/lib/posts" export const revalidate = 3600 export async function GET { const posts = await getPublishedPosts const lines = " Example Studio", "", " Example Studio builds Next.js apps and publishes guides on self-hosting and AI search.", "", " Main", "", "- Home https://example.com/ : Services and contact", "- Projects https://example.com/projects : Case studies", "", " Blog", "", ...posts.map p = - ${p.title} https://example.com/blog/${p.slug} : ${p.excerpt} , return new Response lines.join "\n" , { headers: { "Content-Type": "text/plain; charset=utf-8" }, } } This site does exactly that: fabwaseem.com/llms.txt https://www.fabwaseem.com/llms.txt is built from published posts and projects. For the rest of the setup metadata, sitemap and JSON-LD , see my guide to Next.js SEO for AI search https://www.fabwaseem.com/blog/nextjs-seo-ai-search . Open https://yourdomain.com/llms.txt in a browser and confirm it returns HTTP 200 with a text/plain or text/markdown content type, starts with an H1, and has absolute https links that all load. Then give only that URL to an AI assistant and ask it questions about your site to see whether it finds the right pages. A quick checklist: curl -I https://yourdomain.com/llms.txt returns 200 . Your name . The AI SEO checker https://tools.fabwaseem.com/t/ai-seo-checker runs the H1 and link checks for you as part of a full report. Put the pages that answer the questions people actually ask about you: what you do, pricing or services, docs or guides, key articles, and how to contact you. Use a one-sentence factual summary, short notes per link, and an Optional section for legal pages and archives. Leave out thin pages, tag archives, search pages and anything behind a login. Good and bad examples: | Do | Avoid | |---|---| | Acme is a time-tracking app for agencies, from $9 per user per month. | The best, most innovative solution for everyone. | | - Pricing https://acme.com/pricing : Plans, limits and the free tier | - Click here https://acme.com/p?id=7 | | 10 to 40 curated links | Every URL from the sitemap | | Absolute https URLs | Relative links or staging domains | | Legal pages under Optional | Legal pages at the top | The most common mistakes are serving the file as HTML instead of plain text, missing the H1, using relative links, dumping the entire sitemap, and writing a marketing tagline instead of a factual summary. Each one makes the file harder for an agent to parse or less useful once parsed. Yes. The generator at tools.fabwaseem.com/t/llms-txt-generator https://tools.fabwaseem.com/t/llms-txt-generator is free, needs no account and adds no watermark or branding to the file. There is a small per-visitor rate limit so the tool stays fast for everyone. Put it at the root of your domain so it loads at https://yourdomain.com/llms.txt . The proposal also allows subpaths, such as /docs/llms.txt for documentation only, and agents should use the most specific file that covers a page. Google's documentation for AI Overviews and AI Mode says you do not need new machine-readable files or AI text files to appear in those features. Treat llms.txt as a help for agents and assistants that read it, not as a Google ranking signal. llms-full.txt is a companion file that puts page content, or excerpts of it, into one Markdown document so an agent can read everything in one request. The generator writes one with a short excerpt per page. Keep llms.txt as the short index. Update it whenever you add or remove important pages. If your site uses a CMS, generate the file from your content with a route handler so it never goes stale. Otherwise, rerun the generator after major releases. No. robots.txt controls which crawlers may fetch which paths. llms.txt does not grant or block anything. It is a Markdown guide that tells agents what your site contains and which pages matter. public/ or a route handler that builds it from your content. Paste your homepage into the free llms.txt generator https://tools.fabwaseem.com/t/llms-txt-generator , edit the summary, and publish the file today. Then run the page through the AI SEO checker https://tools.fabwaseem.com/t/ai-seo-checker to see what else AI answer engines need from your site. More free tools are on the tools page https://tools.fabwaseem.com , and you can see what I build on my projects page https://www.fabwaseem.com/projects . Originally published on fabwaseem.com https://www.fabwaseem.com/blog/llms-txt-generator .