agentspeed.

nextjs.org

scanned 7/20/2026, 7:17:31 PM · fresh · rubric 2026.07.1
Built with Next.js
↻ Rescan
robots.txt present: passrobots.txt allows AI agents: passContent-Signal directives: failllms.txt present: passSitemap present: passLink response headers: warnCanonical URL: failMCP server card: failOAuth authorization metadata: failOAuth resource metadata: failAPI catalog / OpenAPI: failWeb Bot Auth: failMarkdown negotiation: failText-to-markup ratio: failContent without JavaScript: skipHeading hierarchy: passCookie wall blocks content: passPage title: passMeta description: passJSON-LD present: failStructured data validates: skipSchema type coverage: passPaywall / login wall: passAgent Skills manifest: failWebMCP actions: failPrimary action reachable: passReachability: passTime to first byte: passFull render time: skipPage weight: pass68/ 100 · D
Needs work

This is how AI agents (not browsers) experience nextjs.org. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.

✉ Email me this report + alert me when it changes ↓

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.

failCanonical URLDiscoverability

No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.

Fix · Next.js: Set alternates.canonical in the Metadata API (generateMetadata) for each route.

failJSON-LD presentStructured data

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.

failText-to-markup ratioReadability

Visible text is 2.4% of HTML weight (7155/292120 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%.

warnLink response headersDiscoverability

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.

failContent-Signal directivesemergingDiscoverability

No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.

Fix: Add `Content-Signal:` directives to your robots.txt. This is the emerging standard (Cloudflare-driven) for declaring fine-grained AI usage policy beyond a binary allow/disallow.

failMCP server cardemergingDiscoverability

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.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever nextjs.org’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.

Add JSON-LD structured data
Paste inside <head>. Use Article/Product instead of Organization on those page types.
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Next.js by Vercel - The React Framework",
  "url": "https://nextjs.org/",
  "description": "Next.js by Vercel is the full-stack React framework for the web."
}
</script>

What the agent receives

The agent’s-eye view
Next.js by Vercel - The React Framework Skip to content Search documentation... ⌘K Search... ⌘K Showcase Docs Blog Templates Enterprise Search documentation... ⌘K Search... ⌘K Deploy Learn The React Framework for the Web Used by some of the world&#x27;s largest companies, Next.js enables you to create high-quality web applications with the power of React components. Get Started Learn Next.js ▲ ~ npx create-next-app@latest What&#x27;s in Next.js? Everything you need to build great products on the web. Data Fetching Make your React component async and await your data. Next.js supports both server and client data fetching. Server Actions Run server code by calling a function. Skip the API. Then, easily revalidate cached data and update your UI in one network roundtrip. Advanced Routing &amp; Nested Layouts Create routes using the file system, including support for more advanced routing patterns and UI layouts. CSS Support Style your application with your favorite tools, including support for CSS Modules, Tailwind CSS, and popular community libraries. Route Handlers Build API endpoints to securely connect with third-party services for handling auth or listening for webhooks. Proxy Take control of the incoming request. Use code to define routing and access rules for authentication, experimentation, and internationalization. React Server Components Add components without sending additional client-side JavaScript. Built on the latest React features. Client and Server Rendering Flexible rendering and caching options, including Incremental Static Regeneration (ISR), on a per-page level. React Server Components Add components without sending additional client-side JavaScript. Built on the latest React features. Data Fetching Make your React component async and await your data. Next.js supports both server and client data fetching. Server Actions Run server code by calling a function. Skip the API. Then, easily revalidate cached data and update your UI in one network roundtrip. Advanced Routing &amp; Nested Layouts Create routes using the file system, including support for more advanced routing patterns and UI layouts. CSS Support Style your application with your favorite tools, including support for CSS Modules, Tailwind CSS, and popular community libraries. Route Handlers Build API endpoints to securely connect with third-party services for handling auth or listening for webhooks. Proxy Take control of the incoming request. Use code to define routing and access rules for authentication, experimentation, and internationalization. Client and Server Rendering Flexible rendering and caching options, including Incremental Static Regeneration (ISR), on a per-page level. React Server Components Add components without sending additional client-side JavaScript. Built on the latest React features. Data Fetching Make your React component async and await your data. Next.js supports both server and client data fetching. Server Actions Run server code by calling a function. Skip the API. Then, easily revalidate cached data and update your UI in one network roundtrip. Advanced Routing &amp; Nested Layouts Create routes using the file system, including support for more advanced routing patterns and UI layouts. CSS Support Style your application with your favorite tools, including support for CSS Modules, Tailwind CSS, and popular community libraries. Route Handlers Build API endpoints to securely connect with third-party services for handling auth or listening for webhooks. Proxy Take control of the incoming request. Use code to define routing and access rules for authentication, experimentation, and internationalization. Client and Server Rendering Flexible rendering and caching options, including Incremental Static Regeneration (ISR), on a per-page level. Next.js 16 The power of full-stack to the frontend. Read the release notes. Built on a foundation of fast, production-grade tooling Powered By React The library for web and native user interfaces. Next.js is built on the latest React features, including Server Components and Actions. Turbopack An incremental bundler optimized for JavaScript and TypeScript, written in Rust , and built into Next.js. Speedy Web Compiler An extensible Rust based platform for the next generation of fast developer tools, and can be used for both compilation and minification. Get started in seconds Deploy Next.js to Vercel Starter Ecommerce Blog AI Portfolio SaaS Multi-tenant Apps Realtime Apps Documentation Virtual Event Web3 Vercel is a frontend cloud from the creators of Next.js, making it easy to get started with Next.js quickly. Jumpstart your Next.js development with pre-built solutions from Vercel and our community. Deploy a Template on Vercel Next.js Boilerplate A Next.js starter from create-next-app. Image Gallery Starter An image gallery built on Next.js and Cloudinary. Next.js Commerce An all-in-one starter kit for high-performance ecommerce sites. The framework of choice when it matters Audible Sonos Dice Notion Today ProductHunt Nike Washington Post Sonos Audible Nike Notion ProductHunt Washington Post For performance , efficiency and developer experience . Next.js is trusted by some of the biggest names on the web. View the Next.js Showcase Customer Testimonials “ With Next.js, we now consistently average 0.09 or lower for Cumulative Layout Shift, placing our site in the top tier for user experience and Core Web Vitals. ” Senior Software Engineer , Frontend “ Our UI for Frame.io responds to user input within 100ms and all animations run at a consistent 60fps with Next.js. ” Charlton Roberts , Product Engineering “ Next.js has been a game-changer for our agency work and team collaboration. Its powerful features have allowed us to build high-performance websites quickly and efficiently like never before. ” Daniel Lopes , Frontend Developer Resources Docs Support Policy Learn Showcase Blog Team Analytics Next.js Conf Previews Evals More Next.js Commerce Contact Sales Community GitHub Releases Telemetry Governance Ecosystem Working Group About Vercel Next.js + Vercel Open Source Software GitHub Bluesky X Legal Privacy Policy Cookie Preferences Subscribe to our newsletter Stay updated on new releases and features, guides, and case studies. Subscribe © 2026 Vercel, Inc. Original 1440px 375px Built-in Optimizations Automatic Image, Font, and Script Optimizations for improved UX and Core Web Vitals. Dynamic HTML Streaming Instantly stream UI from the server, integrated with the App Router and React Suspense. Next.js 16 The power of full-stack to the frontend. Read the release notes. Built-in Optimizations Automatic Image, Font, and Script Optimizations for improved UX and Core Web Vitals. Dynamic HTML Streaming Instantly stream UI from the server, integrated with the App Router and React Suspense. Next.js 16 The power of full-stack to the frontend. Read the release notes. Built-in Optimizations Automatic Image, Font, and Script Optimizations for improved UX and Core Web Vitals. Dynamic HTML Streaming Instantly stream UI from the server, integrated with the App Router and React Suspense.

Show your score

Embed this badge on your site. It links back to this live scan and updates on every rescan.

AgentSpeed score for nextjs.org
<a href="https://agentspeed.com/scan/nextjs.org"><img src="https://agentspeed.com/badge/nextjs.org" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email and a heads-up when nextjs.org’s agent-readiness changes.

Full breakdown

14 pass1 warn12 fail3 skip
Discoverability
pass
robots.txt present
A robots.txt is reachable at the site root.
100/100
pass
robots.txt allows AI agents
All 9 known agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
pass
llms.txt present
Found /llms.txt (8394 bytes), H1 + at least one link present.
100/100
pass
Sitemap present
sitemap.xml reachable and referenced from robots.txt.
100/100
warn
Link response headers
A Link: header is present but carries none of canonical/alternate/describedby — the relations agents consume.
60/100
fail
Canonical URL
No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.
0/100
fail
MCP server cardemerging
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
0/100
fail
OAuth authorization metadataemerging
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
0/100
fail
OAuth resource metadataemerging
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
0/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
Readability
fail
Markdown negotiationemerging
Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.
0/100
fail
Text-to-markup ratio
Visible text is 2.4% of HTML weight (7155/292120 bytes). Low. Markup may be crowding out agent-usable text.
18/100
skip
Content without JavaScript
Browser pass unavailable; cannot measure JS dependency.
pass
Heading hierarchy
Hierarchy is well-formed (1 H1, no skipped levels, 14 headings total).
100/100
pass
Cookie wall blocks content
No common consent-modal markers detected.
100/100
pass
Page title
A concise <title> is present (39 chars).
100/100
pass
Meta description
A well-sized meta description is present (64 chars).
100/100
Structured data
fail
JSON-LD present
No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
0/100
skip
Structured data validates
No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).
pass
Schema type coverage
Page intent unclear; no specific schema.org type expected.
100/100
Actionability
pass
Paywall / login wall
No paywall or login-wall detected on the landing URL.
100/100
fail
Agent Skills manifestemerging
No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.
0/100
fail
WebMCP actionsemerging
No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.
0/100
pass
Primary action reachable
Primary offering identified ("React framework for web applications") with price/CTA ("Get Started").
100/100
pass
Reachability
HTTP 200.
100/100
Performance
pass
Time to first byte
TTFB 168ms. Healthy.
100/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
pass
Page weight
Initial document is a lean 285 KB.
100/100
Beyond the scan

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.

Start watching free →See plans