Static pre-check · Fri, 07 Aug 2026 06:50:44 GMT
render.com
AI agents struggle with missing sitemap and MCP server initialization, limiting autonomous navigation and integration capabilities despite good overall usability.
Watch a real agent use your site →
A live Claude Code run against render.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 19/22.2
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 homepagedetailsPASS
2 API link(s), e.g. /docs/api
Canonical URL declareddetailsPASS
https://render.com
Documentation linked from the homepagedetailsPASS
5 docs link(s), e.g. /docs/scaling
Homepage has a meta descriptiondetailsPASS
140 characters
Homepage has a descriptive titledetailsPASS
'Render | The cloud for builders' (31 chars)
Open Graph tags presentdetailsPASS
og:title and og:description present
robots.txt allows agent crawlersdetailsPASS
all 6 agent crawlers may fetch /
robots.txt existsdetailsPASS
HTTP 200, 939 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
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
Accessibility 32.1/33.3
Content-to-markup ratio is reasonabledetailsWARN
ratio 0.0135 — 5083 readable chars in 376747 bytes of HTML
Fix: Most of what you serve is markup and inline script rather than content. Reduce inline payloads or server-render more text so the signal-to-noise ratio favours readers.
Docs are readable without JavaScriptdetailsPASS
5002 characters of text at /docs
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://render.com/
Structured data (JSON-LD) on the homepagedetailsPASS
3 valid block(s) (Organization, WebSite, SoftwareApplication)
llms-full.txt is publisheddetailsPASS
HTTP 200, 957329 bytes
llms.txt is publisheddetailsPASS
HTTP 200, 43765 bytes
Links in llms.txt resolvedetailsPASS
5 sampled link(s) all resolve
llms.txt is structured markdowndetailsPASS
has headings and markdown links
Serves markdown when asked for itdetailsPASS
Accept: text/markdown → text/markdown; charset=utf-8
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
Homepage has readable text without JavaScriptdetailsPASS
5083 characters of text in the served HTML
No long redirect chain on the homepagedetailsPASS
0 redirect(s)
Usability 29.2/44.4
MCP server completes the initialize handshakedetailsFAIL
handshake failed: HTTP 406
Fix: Make https://render.com/mcp answer a streamable-HTTP `initialize` request. Check that POST is allowed, that `Accept: application/json, text/event-stream` is honoured, and that the response is a JSON-RPC envelope.
OpenAPI declares its auth schemedetailsFAIL
no securitySchemes declared
Fix: Declare your auth in `components.securitySchemes` and reference it from operations. Without it an agent cannot tell whether a 401 means "log in" or "you are not allowed".
The /api root behaves predictablydetailsWARN
/api → HTTP 200 text/html; charset=utf-8
Fix: Serve JSON from API paths, with an accurate content-type.
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 documents error responsesdetailsWARN
1 error response(s) documented, none with a schema
Fix: Give your 4xx/5xx responses a response body schema with a stable machine-readable error code. An agent needs to branch on the code, not parse your prose.
agents.md is publisheddetailsPASS
HTTP 200, 6259 bytes
A documentation endpoint respondsdetailsPASS
/docs → HTTP 200
OpenAPI operations are describeddetailsPASS
14/14 operations described (100%)
OpenAPI document publisheddetailsPASS
HTTP 200, 4944 bytes of JSON
OpenAPI document is structurally validdetailsPASS
OpenAPI 3.1.0, 14 path(s)
.well-known/mcp.json advertises an MCP serverdetailsPASS
HTTP 200, valid 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
handshake did not complete, so tools/list was not reached
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/render.com)<a href="/score/render.com"><img src="/api/badge/render.com" alt="agent readiness score" /></a>