Create an llms.txt file: a short Markdown guide at the top of your site that tells AI assistants such as ChatGPT, Claude and Perplexity what your site is and which pages matter. Start from your sitemap, have page titles filled in, edit and download. Or check an existing llms.txt against the format.
Fill in a name, a summary and some links, or start from your sitemap.
llms.txt is a plain Markdown file at the top of a website, at example.com/llms.txt, that gives AI assistants a short, curated guide to the site: what it is, the key facts, and links to the pages that matter most, each with a one-line note. It was proposed in 2024 at llmstxt.org as a companion to robots.txt and sitemaps, written for language models rather than crawlers. This tool builds the file for you, starting from your sitemap if you like, and checks existing files against the format.
Tip: Write the summary and notes as you would brief a new colleague: plain facts, no slogans. An assistant quoting your llms.txt should give an accurate answer about what you do.
Be realistic. llms.txt is a proposal, not a standard, and as of late 2026 the major AI search products haven't said they use it for ranking or citing. Google has said it doesn't support it in Search. What it does reliably is help when someone, or an agent, points an assistant at your site: coding assistants and agents read llms.txt files, many developer documentation sites publish them, and a clear file gives any model that fetches it a fast, accurate summary instead of a guess from your navigation.
It takes about half an hour to make and costs nothing to host, so for documentation, software, e-commerce and services sites it's a sensible low-effort addition. It doesn't replace good pages, a sitemap, structured data or robots.txt rules about AI crawlers.
Load pages reads robots.txt for Sitemap: lines (or tries /sitemap.xml), follows a sitemap index to a few of its sitemaps, and takes up to 150 pages, skipping images, files and addresses with query strings. Pages are grouped by their first folder: /docs/ pages under Docs, /blog/ under Blog, and top-level pages under Main pages. The home page's title and description are used for the name and summary if those are empty.
That's a starting point, not a finished file. An llms.txt is most useful when it's short: the 20 to 50 pages that explain your product, prices, policies and key guides. Delete the rest or move them to Optional. Fill in page titles opens each page once and uses its title and meta description; rewrite the notes so they describe content rather than market it.
It confirms the file starts with a single # heading, has a > summary, uses ## sections with list items in the - [Title](URL): note form, and has no deeper headings, which the format doesn't use. It flags list items that aren't links, relative links, duplicates, empty sections, very long files and a file that isn't at the top of the site. If the address returns an HTML page instead of the file, which happens when a site sends its home page for unknown addresses, it tells you that too. Edit this file loads a checked file into the generator so you can fix it.
Regenerate the file when you add products, change prices or retire pages; stale facts are worse than none.
Serve it as text/plain or text/markdown, not as an HTML page, and don't block it in robots.txt.
Documentation sites often add .md versions of pages and link those, which are cleaner for models to read.
Some sites also publish llms-full.txt with the full text of key pages in one file.
Put opening hours, regions, prices and contact details in the summary or details, where they're found quickly.
Describe what you do and don't do. Assistants may repeat it to people deciding whether to buy.
In the top folder of your site, so it opens at https://your-domain/llms.txt, like robots.txt.
No. robots.txt tells crawlers what they may fetch; llms.txt gives AI tools a summary and a reading list. To block or allow AI crawlers, use robots.txt.
No, it's a community proposal from llmstxt.org. Support varies by tool.
Short: a name, a summary and a few dozen links is typical. Long lists belong in your sitemap.
Yes. Upload it to the site's root folder on WordPress, or use a plugin; on platforms without file access, some SEO apps can serve it.
No. The file is built in your browser. Sitemaps and pages are fetched once by our server for the import and aren't kept.
Updated