llms.txt generator and validator

It is a plain text file at yoursite.com/llms.txt, written in Markdown, that tells AI tools which pages on your site matter and what each one is about. The idea comes from llmstxt.org. Think of it as a short, curated map, the opposite of a sitemap that lists everything.

What goes in it. One H1 line with the site name. A blockquote with one or two sentences on what the site is. Then H2 sections, each holding a list of links in the form - [Page name](https://url): what it covers. A section called Optional is a normal place for secondary links; before the spec's August 2026 revision it also told tools which links they were allowed to skip, but that mechanical meaning is gone now, so treat it as a naming convention, not an instruction.

Does it get you cited today? Honestly, not yet on its own. As of now, none of the big answer engines have said they read it when deciding what to cite. What it does do is give any tool or agent that fetches your site a clean, correct summary instead of guessing from your nav. It costs ten minutes and it is where things are heading, so it is worth having, as long as it is accurate. A file full of dead links is worse than none.

The checks the validator runs. The file exists and is served as text. The first line is an H1. There is a blockquote summary. Sections are H2 only. Every list item is in the link form. Links are absolute. Most links have a description. A sample of the links actually respond. The file is not huge.

The spec updated in August 2026. The proposal's author added a real discoverability mechanism: a page can point at its own markdown version and at the llms.txt file that covers it using standard HTML link relations, rel="alternate" type="text/markdown" and rel="describedby", either as <link> tags or an HTTP Link: header. The markdown URL form was also loosened (a plain extension swap, page.md, is allowed now alongside the original page.html.md), and a file in a subpath explicitly covers just that subpath, with the most specific file applying, which is what lets something like a GitHub Pages project site participate without controlling the whole domain. Source: the spec's own changelog.

Shopify started shipping a default agents.md file to every store on May 28, 2026, and /llms.txt and /llms-full.txt both point at that same content unless a merchant has replaced them. Check yours first at yourstore.com/llms.txt before generating a new one here.

The default is generic. It is built to help an agent transact on the store, not to describe what makes it worth citing, and it often points an agent back to Shopify's own Shop app rather than the store itself. Customizing it means adding a template file in the theme code editor: llms.txt.liquid or llms-full.txt.liquid to change one of those paths on its own, or agents.md.liquid to change the shared default all three fall back to. No app is needed for any of this. The validator above still works on a Shopify store either way, since it just fetches whatever is actually being served. The full breakdown covers the fallback order and what each file is for.

Webflow has no default file the way Shopify does, but it does have an official path that does not need custom code: Site settings, then SEO, then LLMs.txt. Upload a UTF-8 file under 100 KB and publish. It goes live at yourdomain.com/llms.txt on the connected custom domain only, not on the webflow.io staging domain, so check the real domain after publishing, not the preview.

Webflow's own help center is candid about where this stands: the format is "not yet widely adopted" and its "effects on AI-driven search are unclear." That matches what this site's own numbers already show. Use the free checker first to confirm crawler access and a readable homepage, the two things that actually decide whether AI answers can cite you. An llms.txt uploaded through Webflow's own field is a fine, low-effort addition once those are settled, not a substitute for them.

WordPress core has no built-in llms.txt feature, unlike Shopify's default file or Webflow's upload field above. Whether your site already has one depends on your plugins, not the platform itself. If you run Yoast SEO, it added a free toggle for this in mid-2025, no Premium needed: Yoast SEO, then Settings, then Site Features, then AI tools, then LLMS.txt. Turning it on auto-generates the file and keeps it current, but it is not available on WordPress multisite, and if your host restricts filesystem write permissions, Yoast tells you the generation failed rather than fail silently and serve nothing.

If you are not running Yoast, dedicated plugins exist too, for example Website LLMs.txt, with over 40,000 active installs per its own WordPress.org listing. Either path writes the file to your site's root the normal way any plugin-managed file gets there. If you would rather skip a plugin entirely, llms.txt is just a plain text file that has to be reachable at yoursite.com/llms.txt, so uploading one directly through your host's file manager or SFTP works the same as it would on any other web server.

Whichever way you add it, the validator above still works the same: it checks what is actually being served, not what a plugin's settings screen claims, since those are two different things to confirm.