Static pre-check · Fri, 07 Aug 2026 06:49:51 GMT
sublimetext.com
AI agents struggle to discover and crawl the site due to missing robots.txt, sitemap.xml, and llms.txt files that facilitate automated indexing.
Watch a real agent use your site →
A live Claude Code run against sublimetext.com, streamed step by step.
Test this with real agents →
An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.
Discovery 13.2/22.2
robots.txt existsdetailsFAIL
robots.txt not served (HTTP 404)
Fix: Serve a /robots.txt. Without it, agent crawlers have to guess what they may fetch.
sitemap.xml exists and parsesdetailsFAIL
sitemap.xml not served (HTTP 404)
Fix: Publish /sitemap.xml listing your public pages, and reference it from robots.txt with a `Sitemap:` line.
API reference linked from the homepagedetailsWARN
no link to an API reference in the homepage HTML
Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.
Canonical URL declareddetailsWARN
no <link rel="canonical">
Fix: Add <link rel="canonical"> to the homepage so agents and crawlers converge on one URL for this page.
Documentation linked from the homepagedetailsPASS
2 docs link(s), e.g. /docs/linux_repositories.html
Homepage has a meta descriptiondetailsPASS
157 characters
Homepage has a descriptive titledetailsPASS
'Sublime Text - Text Editing, Done RightPlayPause' (48 chars)
Open Graph tags presentdetailsPASS
og:title and og:description present
Brand findable in agent searchdetailsN/A
search-based checks are deferred — excluded from the score
Listed in an MCP registrydetailsN/A
registry lookup not implemented in v1 — excluded from the score rather than guessed
robots.txt allows agent crawlersdetailsN/A
no robots.txt to evaluate — nothing is blocked by rules that don't exist
robots.txt points at the sitemapdetailsN/A
no robots.txt
Accessibility 27.1/33.3
llms.txt is publisheddetailsFAIL
/llms.txt not served (HTTP 404)
Fix: Publish /llms.txt: a plain-markdown index that tells an agent what this product is and where the authoritative docs live. It is the cheapest high-leverage file you can add.
Structured data (JSON-LD) on the homepagedetailsWARN
no JSON-LD blocks on the homepage
Fix: Add a JSON-LD block (schema.org Organization or SoftwareApplication) so agents get your name, description and links as data rather than prose.
llms-full.txt is publisheddetailsWARN
/llms-full.txt not served
Fix: Optional but cheap: publish /llms-full.txt with your docs inlined as one markdown file, so an agent can read everything in a single fetch.
Serves markdown when asked for itdetailsWARN
Accept: text/markdown → text/html; charset=utf-8
Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.
Docs are readable without JavaScriptdetailsPASS
1130 characters of text at /docs
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://www.sublimetext.com/
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
Homepage has readable text without JavaScriptdetailsPASS
3687 characters of text in the served HTML
Content-to-markup ratio is reasonabledetailsPASS
ratio 0.1186 (3687 chars of 31099)
No long redirect chain on the homepagedetailsPASS
1 redirect(s)
Links in llms.txt resolvedetailsN/A
no llms.txt
llms.txt is structured markdowndetailsN/A
no llms.txt to parse
Usability 25.7/44.4
agents.md is publisheddetailsWARN
/agents.md not served (HTTP 404)
Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.
Errors are machine-readabledetailsWARN
404 returns HTML, not a machine-readable body
Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.
OpenAPI document publisheddetailsWARN
/openapi.json not served (HTTP 404)
Fix: If you have an HTTP API, publish its OpenAPI document at a predictable path (/openapi.json). It is the difference between an agent reading your contract and an agent guessing it. If you have no HTTP API, ignore this.
.well-known/mcp.json advertises an MCP serverdetailsWARN
/.well-known/mcp.json not served (HTTP 404)
Fix: If you run an MCP server, advertise it at /.well-known/mcp.json so agents discover it without being told its URL.
A documentation endpoint respondsdetailsPASS
/docs → HTTP 200
The /api root behaves predictablydetailsN/A
/api → HTTP 404 (no API at the conventional root)
MCP server completes the initialize handshakedetailsN/A
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
MCP tool parameters are typed and describeddetailsN/A
no listed MCP tools to inspect
Every MCP tool has a descriptiondetailsN/A
no listed MCP tools to inspect
MCP server lists toolsdetailsN/A
no MCP endpoint to probe
OpenAPI declares its auth schemedetailsN/A
no parseable OpenAPI document
OpenAPI operations are describeddetailsN/A
no parseable OpenAPI document
OpenAPI documents error responsesdetailsN/A
no parseable OpenAPI document
OpenAPI document is structurally validdetailsN/A
no parseable OpenAPI document
Payments not applicable — excluded from the score
Serves a 402 payment challengedetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Declares AP2 / ACP supportdetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Publishes x402 payment metadatadetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Badge
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](/score/sublimetext.com)<a href="/score/sublimetext.com"><img src="/api/badge/sublimetext.com" alt="agent readiness score" /></a>