For Next.js
Next.js agent readiness
Next.js gives you a server, a filesystem, and a public/ folder, which means every one of the 14 checks is reachable without a workaround. Most Next.js sites still fail half of them, not because the framework blocks anything, but because nobody added the files.
Native ceiling
Best achievable score without fronting
No Cloudflare fronting needed
Native ceiling is already 100
What agents currently see
A default Next.js deployment (Vercel, self-hosted, or edge) renders server-side HTML for most routes, so content-readability and meta hygiene are usually fine out of the box. What is missing is almost always the machine-facing layer: no /agents.md, no /llms.txt, no MCP server card at /.well-known/mcp.json, no /.well-known/verified.md self-attestation, and no explicit markdown response when a client sends Accept: text/markdown.
App Router projects that lean on client components for the whole page (a single root layout hydrating everything) can also fail content-readability if the meaningful text only appears after JavaScript runs. Static export mode (output: 'export') removes API routes entirely, which quietly kills anything that needs a server response, like content negotiation or an MCP endpoint, unless you move those to an edge function in front of the export.
Your ceiling, and why
100. A Next.js app has a real server (or edge runtime) and a public/ folder, so every check is a file or a route handler away: agents.md and llms.txt as static files, structured data in a layout, a route handler for /.well-known/mcp.json, and content negotiation via a middleware that checks the Accept header and returns a markdown response instead of the page. Nothing about the framework caps the score below hosted-builder territory.
Which delivery model fits
Both self-serve and hands-on work well here. The Agent Ready Kit is a strong fit if you or your team already ship to this repo regularly: every file arrives with exact paths (app/agents.md/route.ts, middleware.ts) and you merge it like any other PR. Done for you is the better call if nobody on the team has bandwidth this sprint, or you want the certification clock started immediately. Cloudflare edge delivery is rarely needed for Next.js specifically, since you already have full code access.
What is typically failing
- agents.md
- llms.txt / llms-full.txt
- MCP server card
- .well-known/verified.md
- Content negotiation (Accept: text/markdown)
- x402 payment signaling
See where you stand
Run a free scan, or start with the self-serve kit if you already know you need it.