Loading...
Loading...
Create llms.txt files to guide AI crawlers on your site
llms.txt is an emerging standard — a simple Markdown file placed at the root of your website that gives large language models a clean, curated map of your most important pages. You can think of it as a sitemap written for AI rather than for traditional search crawlers. When ChatGPT, Claude, Perplexity, Google AI Overviews, or any other model wants to understand what your site is about, an llms.txt file hands them a short, human-readable summary instead of forcing them to guess from cluttered HTML, navigation menus, ads, and scripts.
The idea is simple but powerful. Modern AI assistants are increasingly the layer between your content and your audience. People ask a question, the model answers, and the model decides which sources to read and cite. If your most valuable pages are buried, slow, or wrapped in heavy JavaScript, an AI model may skip them. An llms.txt file removes that friction by spelling out — in plain text — exactly what you publish, which pages matter, and how the model should treat your content.
This free generator builds a valid llms.txt for your site in seconds, and it can also analyze an existing file to score it and flag gaps. You enter your site name, URL, a short description, an optional contact email and license, your most important pages, and which AI crawlers you want to allow or block. The tool returns a ready-to-publish llms.txt plus a matching robots.txt section so AI engines get an accurate, consistent picture of who you are and what you offer.
An llms.txt file is plain Markdown, which means it is readable by both humans and machines. At the top sits an H1 heading with your site or brand name, followed by an optional blockquote that gives a one or two sentence summary of what your site does. This summary is the single most important line in the file — it is the first thing a model reads, so it should be specific, jargon-free, and accurate.
Below the summary you add details and one or more sections. Each section uses an H2 heading such as Docs, Products, Guides, Blog, or About, and under each heading you list links as Markdown bullet points. Every link follows the pattern of a page title, the URL, and a short colon-separated description. That description tells the model what the page covers so it can decide whether the page answers a given question.
Optional metadata rounds out the file: a contact email so AI vendors or partners can reach you, a content license such as CC-BY-4.0 or All Rights Reserved that states how your text may be reused, and crawler policies that name specific AI bots you allow or block. The generator on this page produces all of these parts for you, and the built-in analyzer checks an existing file for the same pieces — sections, contact info, license, important pages, and crawler policies — then returns a score out of 100 with concrete suggestions.
Large language models work best with clean, structured, unambiguous text. A web page is full of noise: headers, footers, cookie banners, related-post widgets, and tracking scripts. When a model has to extract meaning from all of that, it can misread your topic or miss the page entirely. An llms.txt file is the opposite — it is pure signal. By handing the model a tidy list of your best URLs with plain-language descriptions, you raise the odds that your pages are read, understood, and quoted accurately.
Citation is where this pays off. Generative engines increasingly name their sources, and being the cited source drives qualified traffic and authority. When your llms.txt clearly maps a question to a specific page — for example, a pricing page, a how-to guide, or a definitive glossary entry — you make it easy for the model to pick your page as the answer. Good descriptions act like anchor text for AI: they connect intent to content.
llms.txt also future-proofs your site for Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO). As AI search grows, the sites that are easiest to parse will win share of voice. Pairing this file with strong on-page structure, fast load times, and schema markup gives you the cleanest possible footprint for both classic search engines and the new generation of AI answer engines.
llms.txt and robots.txt are complementary, not interchangeable. robots.txt is an access-control file: it tells crawlers which paths they may or may not fetch, and AI vendors have added named user-agents such as GPTBot, ClaudeBot, PerplexityBot, and Google-Extended that you can allow or disallow there. robots.txt answers the question can you crawl this. It does not describe your content or rank its importance.
llms.txt answers a different question — what should you read and how should you understand it. Instead of blocking or allowing paths, it curates and summarizes your best content for AI models. A page can be fully crawlable in robots.txt yet still benefit from a clear entry in llms.txt, because the llms.txt entry adds context the raw HTML lacks.
Used together they form a complete policy. robots.txt sets the boundaries of access, and llms.txt sets the priorities and meaning within those boundaries. That is why this generator outputs both a llms.txt file and a ready-to-paste robots.txt AI section in one step — so your access rules and your content map always agree and never send AI crawlers mixed signals.
Host llms.txt at the root of your domain so it is served at https://yourdomain.com/llms.txt, exactly like robots.txt. AI crawlers look for it at that fixed location, so a file buried in a subfolder will not be found. If you run a static site, drop the file in your public or root output directory. On most frameworks — including Next.js, which powers DarnItSEO — you place it in the public folder so it is served verbatim.
Serve the file as plain text or Markdown with a 200 status code, and make sure it is not blocked by your own robots.txt rules or behind authentication. After publishing, open the URL in a browser to confirm it loads, then paste the same URL into this tool's Analyzer tab to score it and catch any missing sections. Re-run the analyzer whenever you add major content so your llms.txt stays current.
Keep the file lean. It is a map, not a mirror of your whole site. List your highest-value, most evergreen pages — documentation, flagship guides, product and pricing pages, and key reference content — rather than every URL you publish. A focused file with great descriptions outperforms a bloated one every time, because it makes the model's job of choosing your page effortless.
An llms.txt file is one piece of a wider strategy for staying visible in AI search. DarnItSEO offers a connected set of free tools that work well next to this generator. Run the AI Readiness checker to score how well your site is set up for AEO, GEO, and LLMO. Use the Schema Generator to add structured data that reinforces the same facts your llms.txt describes, since rich results and AI answers both lean on clean structured signals.
From there, the Analyze tool gives you a full SEO audit of any page, the SERP Preview tool shows how your titles and descriptions render in results, and the Visibility tool tracks where you appear. Tightening on-page basics with these tools makes your llms.txt entries more trustworthy, because the pages they point to are genuinely well-optimized.
The workflow is straightforward: generate and publish your llms.txt here, add matching schema, fix on-page issues flagged by the audit, then re-check with the Analyzer. Repeating that loop keeps your site readable for both Google and the AI assistants your audience now uses to find answers — and it costs nothing to start.
Add your site name, domain, a short description, an optional contact email and content license.
Add the key pages you want AI to know about and toggle which AI crawlers are allowed or blocked.
We produce a valid, well-structured llms.txt plus a matching robots.txt AI section you can copy.
Upload it to yourdomain.com/llms.txt so AI crawlers can find it, then re-check it in the Analyzer tab.
A Markdown file at /llms.txt that lists and summarizes your most important pages for AI models — a sitemap designed for large language models rather than search crawlers.
At the root of your domain, served at https://yourdomain.com/llms.txt, just like robots.txt. AI crawlers look for it at that exact location.
No. robots.txt controls which paths crawlers may access, while llms.txt curates and summarizes your best content for AI models. They complement each other, which is why this tool generates both.
Adoption is still emerging across vendors, but the file is low-effort and forward-looking. It cleanly documents your key pages for any tool that reads it and prepares your site for AI search.
An H1 with your site name, a one-line summary, sections grouping your key pages by topic, link entries with titles and short descriptions, and optional metadata like a contact email, content license, and crawler policies.
The Analyzer checks for five things — defined sections, contact info, a license, important pages, and crawler policies — and returns a score out of 100 with specific suggestions for anything missing.
Yes. In the generator you can allow or block named bots such as GPTBot, ClaudeBot, and PerplexityBot, and the tool outputs a matching robots.txt section so your access rules stay consistent.
It can. Clear page descriptions act like anchor text for AI, connecting a question to the right page on your site, which makes it easier for a model to select and cite your content.
Refresh it whenever you publish major new content or restructure your site, then re-run it through the Analyzer to confirm it still scores well and lists your current best pages.
Yes, the generator and analyzer are completely free with no signup required.