neon.com
This is how AI agents (not browsers) experience neon.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 JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
Fix · Next.js: Emit JSON-LD from a Server Component or the Metadata API: a <script type="application/ld+json"> with Organization / Article / Product for the page.
Visible text is 1.3% of HTML weight (5265/417487 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%.
Page looks like FAQPage; missing JSON-LD type(s): FAQPage.
Fix: Align JSON-LD type to page purpose. Product pages without Product markup are skipped by agent shopping flows.
A Link: header is present but carries none of canonical/alternate/describedby — the relations agents consume.
Fix: Emit `Link:` headers for canonical, alternate-language, and describedby relations. Agents that fetch HEAD-only or stream-render rely on these.
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
Fix: Publish an MCP Server Card describing the tools your site exposes. Agents discover capabilities via `/.well-known/mcp/server-card.json`. See modelcontextprotocol.io for the schema.
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.
Get it in your inbox now — and a heads-up whenever neon.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.
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/neon.com"><img src="https://agentspeed.com/badge/neon.com" alt="AgentSpeed agent-readiness score" height="56"></a>Track this score
Get this report by email, then a heads-up when neon.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 neon.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.