Is nextjs.org AI agent ready? B · 73/100

Name: AI Readiness Report: nextjs.org
Item: nextjs.org
Rating: 73
Author: AIScan.site

Re-test this site

nextjs.org

Framework unknown

https://nextjs.org/

Grade B · Level 4InteractiveGood — solid foundations, with room to polish.

Why we think this is Custom / Unknown (1 signals)

· hosted on Vercel

5 checks need fixing

2 failed · 3 partial out of 11 that apply to your site.

See top fixes

Fix automatically with AIScan

5 open checks (2 failing) can be handed to an AI agent: D3, C3, B2, E3, E5. Pick one route — each returns the full, check-by-check instructions.

Option A — Agent Skill (any runtime)

npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://nextjs.org/”.

Option B — Claude Code (CLAUDE.md)

curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client

https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://nextjs.org/" }.

Option D — REST API

curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fnextjs.org%2F'

Returns every check with its complete fix guide.

Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://nextjs.org/. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

01Fail
Explicit AI bot rules
+5 pts if fixed
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
See full details
02Fail
Structured HTML (title, meta, JSON-LD, single H1)
+4 pts if fixed
Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
See full details
03Partial
Link header for discovery
+2 pts if fixed
Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
See full details

Hand-off prompt for your coding agent5 issues

# Agent-readiness remediation brief

Site: https://nextjs.org/
Platform: unknown (0% confidence)
AIScan score: 73/100 — Level 4 (Interactive)
Rubric: v2026.08.2

## Failing checks (sorted by weight)
- **[B2] Explicit AI bot rules** — FAIL
  - Evidence: 0 known AI agent(s) addressed in robots.txt
  - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — FAIL
  - Evidence: h1: 0, title: false, meta description: false, JSON-LD: false
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[E3] Heading hierarchy & server-rendered text** — PARTIAL
  - Evidence: 485 words of server-rendered text, 0 <h2>, 0 <h3>
  - Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
- **[D3] Link header for discovery** — PARTIAL
  - Evidence: Link: <https://nextjs.org/>; rel="canonical"
  - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
- **[E5] Content feed (RSS / Atom / JSON Feed)** — PARTIAL
  - Evidence: RSS feed at https://nextjs.org/feed.xml (found by convention, not declared in <head>)
  - Fix: Publish an RSS, Atom, or JSON Feed of new content and declare it in <head> with <link rel="alternate" type="application/rss+xml">. Feeds give agents a cheap, dated changelog of your site that a sitemap doesn't.

## General guidance
- Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards.
- Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`.
- Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot).
- Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first.
- Re-scan at aiscan.site after deploying.

How this score is calculated

Every check earns points against a weight. We divide the points you earned by the points that actually apply to a site like yours — so checks that don't apply never drag you down.

Essential

20 / 31 pts

Baseline every site should meet.

Recommended

17 / 20 pts

Strong signals most sites benefit from.

Bonus earned

0 signals

Emerging standards. Can only add points.

Not counted (7): B1, B3, P1, P2, P3, P4, E2 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.

Discoverability

Can agents find your pages? robots, sitemaps, llms.txt.

Content

Can agents read your content cleanly? Markdown, structured data.

221

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C3
What we found
h1: 0, title: false, meta description: false, JSON-LD: false
Measured against
schema.org vocabulary JSON-LD 1.1 HTML Living Standard — the `title` element
How to fix it
Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
Single H1
Each page should have exactly one <h1> describing the page topic.
Title + meta description
Set a unique <title> (≤60 chars) and <meta name="description"> (≤160 chars) per page.
Add JSON-LD
Embed schema.org structured data so agents can extract entities reliably.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "name": "Example Co", "url": "https://example.com", "logo": "https://example.com/logo.png" } </script>
Fix in ChatGPT Fix in Claude

Bot Access

Are AI crawlers explicitly allowed or blocked?

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found
0 known AI agent(s) addressed in robots.txt
Measured against
RFC 9309 — Robots Exclusion Protocol Google-Extended documentation
How to fix it
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
Add explicit User-agent blocks
Don't rely on User-agent: * alone. Address each major AI crawler so your policy is unambiguous.
Recommended block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
Fix in ChatGPT Fix in Claude

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of nextjs.org on AIScan.site.

HTML

<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fnextjs.org%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (73/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=73&grade=B&host=nextjs.org" alt="AIScan.site Grade B — 73/100" width="240" height="64" loading="lazy" />
</a>

Markdown

[![AIScan.site Grade B — 73/100](https://aiscan.site/api/public/badge.svg?score=73&grade=B&host=nextjs.org)](https://aiscan.site/?u=https%3A%2F%2Fnextjs.org%2F)

Create a free account to track this site over time

Save scan history
See score trends
Re-scan anytime

Dig deeper

Scan any site from Telegram

Send a URL to @AISiteScanBot and get an instant AI-readiness score + top fixes.

Open in Telegram

Automate your AI-readiness

Plug AIScan into your agent stack or chat with it on the go.

Use the MCP server

One line in Claude Code or Cursor to scan any site from your agent.

Chat with the Telegram bot

Scan sites and get fixes right from @AISiteScanBot.

Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

Re-test this site Scan your site

Or browse the community feed to see what others have scanned.

Is nextjs.org AI agent ready? B · 73/100

nextjs.org

Fix automatically with AIScan

Quick Wins

Explicit AI bot rules

Structured HTML (title, meta, JSON-LD, single H1)

Link header for discovery

How this score is calculated

Discoverability

robots.txt present & sane

XML sitemap

Link header for discovery

Correct 404 handling

HTTPS & canonical host

Content

Markdown content negotiation

/llms.txt

Structured HTML (title, meta, JSON-LD, single H1)

Single H1

Title + meta description

Add JSON-LD

Heading hierarchy & server-rendered text

Content feed (RSS / Atom / JSON Feed)

Bot Access

Content Signals in robots.txt

Explicit AI bot rules

Add explicit User-agent blocks

Recommended block

Web Bot Auth key directory

Embed your AIScan badge

Create a free account to track this site over time

Dig deeper

Automate your AI-readiness

Scan your own site

Is nextjs.org AI agent ready? B · 73/100

nextjs.org

Fix automatically with AIScan

Quick Wins

Explicit AI bot rules

Structured HTML (title, meta, JSON-LD, single H1)

Link header for discovery

How this score is calculated

robots.txt present & sane

XML sitemap

Link header for discovery

Correct 404 handling

HTTPS & canonical host

Markdown content negotiation

/llms.txt

Structured HTML (title, meta, JSON-LD, single H1)

Single H1

Title + meta description

Add JSON-LD

Heading hierarchy & server-rendered text

Content feed (RSS / Atom / JSON Feed)

Content Signals in robots.txt

Explicit AI bot rules

Add explicit User-agent blocks

Recommended block

Web Bot Auth key directory

Share as a social image

Embed your AIScan badge

Create a free account to track this site over time

Dig deeper

Automate your AI-readiness

Scan your own site