llms.txt Generator
Enter your website and get an llms.txt file built from your sitemap: a clear summary, pages grouped into sections, and a short description for each link. Edit it with a live preview and validator, then copy or download it.
- Built from your sitemap
- Live preview and validator
- Copy or download
Check how ready the page is with the AI Search Visibility Checker, or see who can read it with the AI Crawler Tester.
What goes in an llms.txt file
A short Markdown file at /llms.txt that points AI tools to your most useful pages.
A title
One H1 with your site or business name. It is the only required part.
A summary
A short blockquote that says who you are and what you do, in plain words a model can reuse.
Sections of links
H2 sections, each a list of links with a short note about what the page covers.
Optional notes
A few lines of context before the sections: location, audience, how you want to be described.
An Optional section
Links a tool may skip when it is short of room, such as policies and secondary pages.
Full addresses
Models fetch links on their own, so each link should be a full https address.
How pages are grouped
The tool sorts your URLs by folder, and you can change any of it.
| Folder | Section | Notes |
|---|---|---|
| / and top-level pages | Key pages | Home, pricing, contact and similar pages. |
| /services, /products, /courses | Services, Products, Courses | Grouped by what they are. |
| /blog, /news, /guides | Blog, Guides and resources | Capped at 20 ticked links per section by default. |
| /privacy, /terms, /cookie | Optional | Useful, but a model can skip them. |
How to create and publish llms.txt
Four steps, about five minutes.
Enter your site
The tool reads your sitemap and groups the pages. No sitemap? Paste a list of URLs instead.
Edit the draft
Tick the pages that matter, tidy the titles and notes, and fix anything the validator flags.
Download the file
Copy it or download llms.txt. Keep the summary honest and the list short.
Upload it to your root
Publish it at yoursite.com/llms.txt, then open that address to confirm it loads as plain text.
What llms.txt is, and what it isn't
A helpful extra, not a ranking factor.
Not a guarantee
No major AI company has promised to use llms.txt. It is a cheap, harmless way to help tools that do read it.
Not a replacement for SEO
It does not replace a sitemap, good content or structured data. It sits beside them.
Keep it accurate
Describe the business as it is. A summary a model repeats should be one you would be happy to see quoted.
Short beats long
A focused list of your best pages is more useful than a copy of the sitemap.
Refresh occasionally
When you add a major page or retire an old one, update the file and the notes.
Public by design
Only list pages you want found. Anything in llms.txt is public, like robots.txt.
What llms.txt is and what a generator builds for you
llms.txt is a proposed convention, published at llmstxt.org, for giving language models a short guide to a website. It is a Markdown file served from your site, with a required # title, an optional > summary, optional notes, and ## sections that hold lists of links, each with a short note about the page. A section named Optional holds secondary links a tool may skip when it has little room.
It is a proposal, not a standard that search engines or AI companies have adopted. Google's page on AI features in Search says there are no additional requirements to appear in AI Overviews or AI Mode, and that you do not need to create new machine-readable files or AI text files. No major AI company has promised to use llms.txt, so treat it as an optional extra, not a ranking factor.
The slow part of writing one is collecting titles and one-line descriptions for dozens of pages. This generator reads your sitemap, groups the URLs into sections, pulls each page's title and description as a first draft, and lets you edit everything and check the format before you publish. The final wording stays under your control.
When it is worth creating an llms.txt file
It costs little to publish, so the question is whether you have a clear set of pages worth pointing tools to.
A documentation or help site
Technical docs are the setting the proposal was written for. An index of key guides, each with a one-line note, is a sensible aid for assistants that read it.
A service business with core pages
List your main services, pricing, contact and a few strong guides, with an honest summary of who you serve and where. It is a short, quotable description of the business.
A shop with clear categories
Point to your main categories, shipping and returns policies and buying guides. Keep the list short; it is not a copy of the product catalogue.
After a redesign or restructure
When URLs change, rebuild the file from the new sitemap so it does not point tools at pages that redirect or no longer exist.
To tidy up how you describe yourself
Writing the summary forces you to state what the business does in two plain sentences. That text is useful in your About page and structured data too.
To experiment safely
Because the file is public and harmless, it is a low-risk test. Just do not expect a rise in rankings or citations, and do not stop doing the work that matters.
llms.txt mistakes and how to avoid them
The file is small, so the mistakes are mostly about expectations and editorial choices.
Expecting rankings or citations
What goes wrong: Treating llms.txt as an SEO lever sets you up for disappointment. It is a proposed convention, and Google says you do not need AI text files to appear in its AI features.
The fix: Publish it as a helpful extra for tools that read it. Keep investing in crawlable, accurate content, structured data and trust signals.
Pasting the whole sitemap
What goes wrong: A list of hundreds of URLs with no notes dilutes the file. The point of llms.txt is a curated guide, not a duplicate of the sitemap.
The fix: Pick your best pages, aiming for roughly 10 to 40, and put policies and secondary pages under the Optional section.
Using relative links
What goes wrong: A tool that fetches the file on its own has no page context. A link such as /about may not resolve.
The fix: Use full https addresses for every link, and make sure each one is the canonical, working URL.
A vague or promotional summary
What goes wrong: The summary is the first thing a reader sees. 'Leading provider of innovative solutions' says nothing a model could reuse.
The fix: State plainly what you do, for whom and where, in one or two sentences you would be happy to see quoted.
Listing pages you do not want public
What goes wrong: llms.txt is public, like robots.txt. Anything in it can be read by anyone, including links to unlisted or sensitive pages.
The fix: Only list pages that are already public and meant to be found. Never use the file to hide or protect anything.
Never updating it
What goes wrong: A file written once drifts out of date. Retired pages and missing new ones make it less trustworthy over time.
The fix: Refresh it when you add or remove a major page, and run a checker occasionally to catch dead links and wrong redirects.
llms.txt terms explained
- llms.txt
- A proposed Markdown file, normally at the root of a site, that gives language models a short summary and a curated list of links. It is not an adopted web standard.
- H1 title
- The single
#heading with the name of the site or project. In the proposal it is the only required part of the file. - Blockquote summary
- A short
>quote under the title that holds the key facts a reader needs before the links, such as who you are and what you do. - File list
- A Markdown list under an
##heading. Each item is a link in Markdown link form, optionally followed by a colon and a short note. - Optional section
- A section named
Optional. By convention it holds secondary links that a tool can skip when it needs a shorter context. - Markdown page version
- A clean
.mdcopy of a page. The proposal suggests serving one at the same address with.mdadded, so tools can read the content without the page's layout. - AI crawler
- An automated bot run by an AI company. Whether it can fetch your files depends on robots.txt and your firewall, not on llms.txt.
- Model context
- The limited amount of text a language model can read at once. It is the reason the file is meant to be short and the
Optionalsection exists.
Related tools, guides and services
llms.txt is one small piece of AI readiness. These cover the pieces that carry more weight.
llms.txt Checker
Test that the file loads as plain text, follows the format and links to working pages.
ToolAI Crawler Tester
Check which AI crawlers robots.txt and your firewall let through.
ToolAI Search Visibility Checker
Score how ready a page is to be found and quoted by AI search.
ToolXML Sitemap Generator
Create the sitemap this generator reads when it builds your file.
GuideFuture of SEO in Nepal
Includes how AI search, crawler controls and llms.txt fit into a practical plan.
ServiceAI SEO service
Get help making your brand findable and citable in AI search, beyond a single file.
Built by
Madhav Kushwaha
A good llms.txt is a short, honest guide to a site, and the tedious part is collecting titles and descriptions for dozens of pages. I built this generator to do that part from your sitemap, keep you in control of the final wording, and check the file against the format, so what you publish is clean. I use the same file on my own site.
llms.txt Generator: Frequently Asked Questions
More free SEO tools
Make your site easy for AI tools to find and read.