render.com
This is how AI agents (not browsers) experience render.com. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.
Top fixes
Checks tagged “emerging” are 2026 agent-protocol standards most of the web hasn’t adopted yet — adopting early is an edge, not a defect.
No reachable sitemap.xml. Publish one and reference it in robots.txt.
Fix · Next.js: Add app/sitemap.ts (Next’s sitemap convention) and reference it from robots.txt.
Visible text is 1.4% of HTML weight (5138/378123 bytes). Low. Markup may be crowding out agent-usable text.
Fix: Heavy ad or navigation markup crowds out agent-usable text. Aim for a text-to-DOM ratio above 15%.
1 recommended-field warning(s). First: WebSite recommends "potentialAction" (improves agent comprehension). 1 block(s) skipped — type outside the set we check.
Fix: Validate your JSON-LD with Google Rich Results test. Fix missing required properties.
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
Fix: Expose OAuth metadata at `/.well-known/oauth-authorization-server` per RFC 8414. Required for agents that need to perform user-authorized actions on your site.
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
Fix: Publish OAuth resource metadata at `/.well-known/oauth-protected-resource` per RFC 9728. Required for agents that act on behalf of authenticated users without hand-coded credentials.
Get it in your inbox now — and a heads-up whenever render.com’s agent-readiness score changes. Free, unsubscribe anytime.
Fix it
Generated, ready-to-ship files for the gaps above — copy them or download and drop them into your repo.
This score clears the Silver threshold (80+). Certification turns it into a dated, publicly verifiable attestation — a verification URL, an embeddable badge, and weekly monitoring for a full year. Scores under 70 can’t buy this, which is what makes displaying it mean something.
Get certified — $199/year →What the agent receives
Show your score
Embed this badge on your site. It links back to this live scan and updates on every rescan.
<a href="https://agentspeed.com/scan/render.com"><img src="https://agentspeed.com/badge/render.com" alt="AgentSpeed agent-readiness score" height="56"></a>Track this score
Get this report by email, then a heads-up when render.com’s agent-readiness actually changes — a check regressing, or the composite dropping.
Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.
Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.
This score says whether an AI agent could read render.com. AI traffic analytics says whether one actually came — and which pages turned it away.
Full breakdown
Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.