Does your site have a working llms.txt?
Enter your website. We fetch /llms.txt, check it against the spec and, if it's missing or thin, write you one from your own sitemap.
Try
Free. No signup. We read /llms.txt and your sitemap.
Reading your llms.txt
- Reading your site
- Checking what AI assistants can read
- Checking your llms.txt
- Drafting one from your sitemap
How it works
- 1
Is it really there
We fetch /llms.txt and check it is markdown, not your homepage. Many sites answer every unknown path with an HTML page, and tools then report a file that does not exist.
- 2
Does it follow the spec
An H1 with the site name, a summary, sections with link lists and an Optional section, in the order llmstxt.org sets.
- 3
Do the links work
We test some of the linked pages. A map that points at dead pages costs more trust than no map.
Questions
What is an llms.txt file?
A markdown file at the root of your domain (/llms.txt) that tells AI assistants what your site is and where the useful pages are. It was proposed by Jeremy Howard in September 2024 and is being adopted as a de-facto convention. Think of it as a curated map for models, the way robots.txt is a set of rules for crawlers and a sitemap is an index for search engines.
What does a valid llms.txt need?
Per the spec at llmstxt.org, exactly one thing is required: an H1 with the name of the site. Everything else is optional but useful - a blockquote summary right after it, then H2 sections each holding a markdown list of links in the form "- [Name](URL): note". A section named "Optional" marks links a model can skip when context is tight.
Is llms.txt the same as robots.txt?
No, and they do not replace each other. robots.txt says which crawlers may fetch what - it is permission. llms.txt says what your site is and which pages matter - it is orientation. A site can allow every AI crawler and still be badly understood, which is exactly the gap this file closes.
Do AI assistants actually read it?
Adoption is uneven and no major assistant has committed to it publicly, so treat it as cheap insurance rather than a guarantee. It costs one small file, it cannot hurt your search rankings, and if a model does look for it you are the site that has one. We would rather tell you that plainly than oversell it.
Why does the checker fetch some of my linked pages?
Because a map that points at dead pages is worse than no map. We sample a few of the links in your file and check they resolve. We only read public pages and never submit forms.
The file you generated - can I just publish it?
Read it first. Every link comes from your own sitemap and the name and summary from your own page metadata, so nothing in it is invented. Where we could not find a value we left a marked gap in <<< >>> for you to fill rather than guess. Once it reads right, save it as llms.txt at the root of your domain.
More free tools
Score how ready a single product page is for AI shopping - see how ChatGPT, Perplexity and Google AI read it.
AI Store Readiness CheckerScore your whole store - AI crawler access, structured data, sitemap, llms.txt and more.
Google Merchant Feed CheckerValidate your feed against Google's product spec - attributes, price format, GTIN checksums - before disapproval.
ACP Feed CheckerGrade your feed against the Agentic Commerce Protocol - is your catalog ready to sell inside ChatGPT?
Comparing AI tools for your shop?
Honest side-by-side comparisons, including where the other tool is the better buy.