Enter your domain
Use your main hostname. The checker fetches /llms.txt directly from your live site.
Validate your llms.txt so AI assistants can read your site
AI assistants use llms.txt to navigate your site. Check whether yours follows the convention — H1 name, summary, sections, and linked resources — in one step.
Enter a domain. This checker reads its /llms.txt and validates it against the llms.txt convention, then shows a readiness score and what to fix.
llms.txt is a markdown file at /llms.txt that gives AI assistants a concise, structured guide to your most important pages. Instead of guessing your site's shape from raw HTML, an assistant can read your name, a one-line summary, and a short list of linked resources.
The convention is simple, but easy to get subtly wrong — a missing H1, no summary, or a flat list with no sections all make the file less useful. This checker validates each part in one step.
Enter your domain and the checker reads your live /llms.txt, then validates it against the llms.txt convention.
Use your main hostname. The checker fetches /llms.txt directly from your live site.
It checks the H1 name, blockquote summary, H2 sections, and markdown links with descriptions.
Each check is marked pass, improve, or fix, with a plain-English reason — so you know what to change.
These are the parts of the llms.txt convention that make your file useful to AI assistants.
A valid llms.txt helps assistants navigate your site. Run the full AEOMaster audit to see whether AI answers actually find, mention, and cite your pages.
Clear answers about AI mentions, AI citations, ChatGPT visibility, Perplexity citation readiness, and when a full audit is worth running.
It fetches your site's /llms.txt and validates it against the llms.txt convention: a single H1 name, a one-line summary, H2 sections, and markdown links with descriptions. You get a readiness score and a checklist of what to fix.
llms.txt is a proposed standard (llmstxt.org): a markdown file at /llms.txt that gives AI assistants a curated, easy-to-parse map of your most important pages, so they can ground answers in your content instead of guessing.
A well-structured llms.txt makes it easier for AI assistants to find and correctly summarize your key pages. It does not replace crawlable content, but it is a low-effort signal that helps assistants navigate your site.
Start with an H1 that names your site, add a “> summary” blockquote, then group your key links under “## ” sections such as Docs, Guides, or Products — each link as “[Title](url): short description”. The checker flags anything missing.
No. A valid llms.txt only means assistants can navigate your site — whether they actually mention and cite you depends on your content, entity clarity, and third-party evidence. That is what the full AEOMaster audit measures.
Re-check whenever you restructure your site, add major sections, or change your llms.txt. It is a static file, so it can drift out of date without anyone noticing.
This checker validates the structure of your llms.txt. AEOMaster turns that into a full one-time audit of whether AI answers actually mention and cite you — with prioritized fixes.
Prompt-level results across ChatGPT, Claude, Perplexity, Gemini, and Google AI — not just file structure.
The sources AI answers cite, and the pages and citations you are missing.
Every finding ranked by expected impact and effort, so you know what to fix first.
Each issue comes with the why, the steps, and an example you can act on.
Re-run it after you ship fixes to confirm your structure and visibility improved.
AEOMaster turns this structure check into a one-time AI visibility report: prompt-level findings, citation gaps, competitor context, and prioritized fixes you can re-run after each change.
Reading your /llms.txt and validating it against the llms.txt convention before showing your results.
AEOMaster turns this structure check into a full audit of whether AI answers mention and cite you.
Get Started