Get your site AI-ready.
Give AI agents a clean, standards-aligned llms.txt so the pages that matter are easy to find and understand.
Generate one from your existing site, check the file you already have, and keep it accurate as your website changes.
What llms.txt is, and what Studio does.
Transcript
When someone asks ChatGPT, Claude or Perplexity about a business, the assistant often goes and reads the website. But a web page is built for people — navigation, menus, scripts, ads. The useful part is buried, and the agent has to guess what matters.
llms.txt is a small text file at the root of your site. It's a proposal from llmstxt.org — a plain Markdown map: what your site is, and links to the pages that explain it best. Documentation, product, pricing, policies. Not every page — the ones that matter.
Let's be clear about what it doesn't do. It doesn't guarantee rankings, citations or traffic. Some AI systems read it, some don't. What it does is remove the guessing for any agent that chooses to look.
llms.txt Studio builds the file from what your site already publishes — your sitemap, your titles, your descriptions. No AI model invents a summary of your company. It's free, and you don't need an account.
Already have one? Validate it. You get two answers: is it a valid llms.txt under the current spec, and how useful is it — a grade from 0 to 100, with every deduction shown.
Then there's the part that matters after launch. Sites change. Pages move. Links break. And the file just sits there, quietly going stale. Monitor checks it every week. If the grade drops, a link dies, or the file drifts from your site, you get an email with the exact lines that changed — and one click to regenerate. It also shows you when a documented AI crawler fetched your file, with the timestamp.
Generate one now, free, at llmstxt.echorank360.com. Keep it correct with Monitor. That's the whole product: a correct, current file, and evidence when something touches it.
One small file. Three useful jobs.
- Generate
Turn your existing website into a clean, structuredllms.txt. We use your sitemap and your own page content to identify and organize the pages that matter. Same website, same inputs, same output. - Validate
Already have anllms.txt? Check it against 16 format, structure, link, content-type, and crawler-access rules. Every issue includes the rule that triggered it and where we found it. - Monitor
Websites change. Yourllms.txtshould change with them. Monitoring checks that the file is still live, valid, and aligned with your site — and can show you when recognized crawler user-agents fetch your canary URL.
Built from your website. Not invented by AI.
Your llms.txt should describe what is actually on your site. So we don't ask an AI model to rewrite your company, invent summaries, or decide what you meant.
We use:
- your sitemap
- your page titles
- your meta descriptions
- your headings
- your live URLs
If important information is missing from your website, we don't make it up.
Your content stays your content.
See what a real llms.txt looks like.
We generated the file for EchoRank360 using the exact same system. It contains 60 links across Docs, Product, Blog, About, and Optional sections, received an A grade from the validator, and was published without hand-editing.
Live validation of echorank360.com/llms.txt on 2026-09-11: grade A, 100/100, 60 links · report
# Echorank360 > When customers ask ChatGPT, Google AI or Perplexity who to hire, is your business the answer? Measure your AI Visibility Score, track recommendations daily, and get a prioritized roadmap to become the business AI recommends. ## Docs - [Echorank Glossary — search, ranking & AI visibility terms](https://echorank360.com/en/glossary): The Echorank Glossary: definitions and concepts for search, ranking, AI visibility, and digital discovery. - [Echorank User Guide](https://echorank360.com/en/guide): By the end of this guide you will have connected your Google Business Profile, imported your review history, launched your first review campaign, set up… - [AI visibility, from zero to tracked](https://echorank360.com/en/guides/ai-visibility): What ChatGPT, Perplexity and Gemini answer when your market comes up — how to measure it, track it and improve it, step by step. - [Audit your website — what crawlers and AI actually see](https://echorank360.com/en/guides/audit-your-website): Run the free audit, read the itemised checks, and fix in the order that moves the score: crawlability first, structured data second, content last. - [Getting started with Echorank — setup guide](https://echorank360.com/en/guides/getting-started): From an empty account to a working dashboard in about 15 minutes: create your account, connect Google Business Profile, run your first audit and import your… - [Keyword research — from customer language to a tracked list](https://echorank360.com/en/guides/keyword-research): Start from what customers actually say, expand in Keywords Explorer within your plan's search quota, filter by intent, and assign one primary keyword per page. - [Track rankings — a stable basket and a monthly read](https://echorank360.com/en/guides/track-rankings): Pick ten to twenty-five terms, add them to Rank Tracker, read trends over four weeks rather than four days, and connect Search Console for the queries you… - [Learn reputation & AI visibility — the Echorank Knowledge Hub](https://echorank360.com/en/learn): A free ten-chapter course, five deep-dive guides and a glossary: audit your baseline, import your review history, generate and answer reviews, and get……
Know if your llms.txt is actually healthy.
A file existing at /llms.txt doesn't mean it's useful. The validator checks 16 rules covering structure, formatting, accessibility, links, file size, and crawler-related information.
Two verdicts, not one blended number. Spec validity asks whether the file is a valid llms.txt at all: it exists, is served as text, has an H1, its file lists are well formed, and it is not an HTML page. Quality is Studio's set of recommendations, graded 0 to 100.
Start at 100. Problems subtract points according to published rules. A missing file or HTML page served in its place fails immediately. Informational findings — such as blocking an AI crawler in robots.txt — don't lower your score because that may be an intentional choice.
No mystery score. Every deduction is shown.
Checked against llmstxt.org v2 (August 10, 2026)
Weekly checks. Exact diffs. One-click regeneration. Crawler fetch evidence.
$12/month · $99/year per domain
- Aug 24Aspec valid20 links tested, 0 dead
- Aug 31Aspec validno change
- Sep 07Bspec valid1 dead link · file changed
- Sep 14Aspec validregenerated file live
Grade A → B. One dead link (webhooks.md moved) and one new page. The exact lines that changed:
--- example.com/llms.txt @ Aug 31+++ example.com/llms.txt @ Sep 07@@ -2,4 +2,5 @@- [Quick start](https://example.com/docs/quickstart.md): Install and first run- [API reference](https://example.com/docs/api.md): Every endpoint- - [Webhooks](https://example.com/docs/webhooks.md): Events and retries+ - [Webhooks](https://example.com/docs/hooks.md): Events and retries… 1 more lines
Plain-text email, the diff excerpt inside, at most one per domain per day:
llms.txt check for example.com Spec: valid · Quality grade: B GRADE DROPPED: Grade went from A to B W3 L9: Dead link (404): https://example.com/docs/webhooks.md CONTENT CHANGED: The file changed since the last check --- example.com/llms.txt @ Aug 31 +++ example.com/llms.txt @ Sep 07 @@ -2,4 +2,5 @@ - [Quick start](https://example.com/docs/quickstart.md): Install and first run - [API reference](https://example.com/docs/api.md): Every endpoint…
One click runs the same generator against the verified domain (60 pages, 2 requests per second) and opens the result with the publish checklist. You deploy it; nothing is published for you.
Regenerate nowone per domain per hourYou'll know when:
- your
llms.txtdisappears - your validation grade drops
- a link breaks
- the file drifts from your live website
- monitored content changes
- a recognized AI crawler user-agent fetches your canary URL
Maximum one alert per day.
Start monitoring — $12/monthMonitoring can add a small canary link to your llms.txt. If a crawler follows that URL, we record the timestamp and user-agent string.
We currently recognize user-agent strings associated with:
- ChatGPT-UserOpenAI
- Claude-UserAnthropic
- Perplexity-UserPerplexity
- meta-externalfetcherMeta
- Amzn-UserAmazon
- MistralAI-UserMistral
- DuckAssistBotDuckDuckGo
- OAI-SearchBotOpenAI
- Claude-SearchBotAnthropic
- GooglebotGoogle
- PerplexityBotPerplexity
- ApplebotApple
- Amzn-SearchBotAmazon
- GPTBotOpenAI
- ClaudeBotAnthropic
- meta-externalagentMeta
- AmazonbotAmazon
- CCBotCommon Crawl
Every entry is cited to the vendor's own documentation on /help. Robots-only control tokens have no user-agent and never appear in a fetch log.
This gives you evidence that a user-agent identifying itself as one of these crawlers fetched the URL. It does not prove that the company behind that name operated the request, because user-agent strings can be spoofed. And if you see no fetch, that doesn't prove an AI system ignored your llms.txt.
We show the evidence. We don't exaggerate what it means.