https://llmstxt.org/llms.txt
Score history · 30 checks
Findings
-
H1 title present
Title: "llms.txt"
-
Blockquote summary present
-
1 section(s) with links
-
3 Markdown (.md) link(s)
Linking Markdown versions helps models parse content cleanly.
-
All links reachable
Links
- 200 https://llmstxt.org/index.md
- 200 https://llmstxt.org/intro.html.md
- 200 https://llmstxt.org/ed-commonmark.md
AI discoverability optional · doesn’t affect score
Beyond llms.txt, these companion files help AI tools and search engines understand your site. We only check genuinely adopted ones.
-
✓
robots.txt standard /robots.txt
1 Sitemap directive.
-
✓
sitemap.xml standard /sitemap.xml
Valid XML sitemap.
-
—
RSS / Atom feed standard /rss.xml
Suggestion: A feed (RSS/Atom) at a common path helps AI tools track fresh content. (May exist via <link rel=alternate>.)
-
—
ads.txt standard /ads.txt
Only needed if the site serves programmatic ads (IAB authorized sellers).
-
—
security.txt standard /.well-known/security.txt
Suggestion: Add /.well-known/security.txt (RFC 9116) with a Contact and Expires field.
-
—
ai.txt informational /ai.txt
Not a formal standard; an opt-in AI-training/usage directive honored only by some actors.
-
—
A2A agent card emerging /.well-known/agent-card.json
Optional: only relevant if the site exposes an AI agent (Google A2A protocol).
-
—
llms.json emerging /llms.json
Optional structured (JSON) manifest some sites add for agents.
-
—
Markdown content negotiation emerging homepage
Suggestion: Optionally serve a Markdown rendering of pages when Accept: text/markdown is requested, so AI agents get clean content.
-
—
Content Signals emerging /robots.txt
Suggestion: Optionally add a Content-Signal directive to robots.txt to declare permitted AI uses (e.g. search=yes, ai-train=no).
-
—
MCP server card informational /.well-known/mcp.json
Optional & emerging. Looks for /.well-known/mcp.json; there is no ratified MCP discovery well-known yet, so absence isn't proof of nothing.
-
—
API Catalog emerging /.well-known/api-catalog
Suggestion: If you expose APIs, publish /.well-known/api-catalog (RFC 9727) so agents can discover them.
-
—
OAuth discovery emerging /.well-known/oauth-protected-resource
Suggestion: If agents need authenticated access, add OAuth discovery (/.well-known/oauth-protected-resource, RFC 9728).
-
—
Structured data (JSON-LD) standard homepage
Suggestion: Add schema.org JSON-LD (Organization, WebSite) — this is how AI/knowledge graphs identify a site.
-
✓
Open Graph tags standard homepage
Open Graph tags present (controls link previews in AI/social).
-
✓
Twitter Card standard homepage
Twitter Card metadata present.
-
—
Canonical URL standard homepage
Suggestion: Add a <link rel="canonical"> to consolidate duplicate URLs.
-
—
FAQPage schema standard homepage
Suggestion: If you have Q&A content, add FAQPage JSON-LD so AI answer engines can cite it directly.
-
—
AI file discovery hints emerging homepage
Suggestion: Add <link rel="alternate" href="/llms.txt"> (and llms-full.txt) in <head> so crawlers discover your AI files.
-
—
WebMCP browser tools informational homepage
Optional & experimental. Detects only declarative <form toolname> markup; imperative navigator.modelContext (JS) tools aren't visible to a server-side check.
For brand/identity data, use schema.org Organization JSON-LD embedded in your pages — that’s what knowledge graphs actually read. Files like brand.txt, identity.json or llms.json are vendor inventions with no shared spec, so we don’t check them.
Shareable link: https://llms-txt-validator.dev/r/4ucjz3ebzepa
Embed your score
Add this badge to your README or site. It updates automatically when the site is re-checked.
Markdown
[](https://llms-txt-validator.dev/report?url=llmstxt.org)
HTML
<a href="https://llms-txt-validator.dev/report?url=llmstxt.org"><img src="https://llms-txt-validator.dev/badge/llmstxt.org.svg" alt="llms.txt score"></a>