nextjs.org

ADA 80/100 (B+) ARS 74% High-Authority AI Source

Next.js by Vercel - The React Framework

AI Domain Authority: ADA 80/100 (High-Authority AI Source)
Raw HTML / Signal: ~67,086 tok (1.6% signal)
/llms.txt Manifest: 3,648 tok (Spec Compliant)
Edge / TTFB: Vercel · 61 ms
AI Domain Authority (ADA) Agent Readiness (ARS) Citation Authority Token Savings (/llms.txt) Network TTFB Provenance & TLS
80/100 (B+) 74% 82/100 (1 citers) -94.6% fewer tokens 61 ms (Vercel) 80/100

AI Domain Authority (ADA 80/100) & Citation Graph

Open Formula & Spec →
1. Machine Citation Authority (58%) 82/100 · TrustRank over /llms.txt, mcp.json & JSON-LD graphs
2. Agent Ingestion / ARS (18%) 74% · Manifest validity, token efficiency, TTFB & bot access
3. Entity & DNS Provenance (14%) 80/100 · X.509 TLS, security headers, SPF/DMARC & TXT proofs
4. Crawler Pulse & Edge (10%) 76/100 · Edge & search-bot reachability
Observed Inbound Machine Citers vercel.com
Outbound Cited Authorities (25) github.com · wikipedia.org · vercel.com · npmjs.com · react.dev · notion.com · svelte.dev · x.com
Compare nextjs.org head-to-head:

Web-to-Token Efficiency & Agent Ingestion Cost

~4 bytes/token UTF-8 heuristic
Ingestion Source Payload Est. Tokens Cost / 1k Reads (Flash $0.35) Cost / 1k Reads (Pro $1.25)
Raw HTML DOM (GET /) 262.1 KB 67,086 $23.4801 $83.8575
Stripped Readable Text 4.1 KB 1,058 $0.3703 $1.3225
/llms.txt Manifest 14.3 KB 3,648 $1.2768 $4.5600
HTML Signal-to-Noise Ratio: 1.6% readable text vs. 98.4% markup/script overhead. Token Optimization Guide →

/llms.txt Spec Linter & Agent Endpoint Probe

Status: Spec Compliant · Spec Rules →
GET /llms.txt HTTP 200 · 14,592 bytes (~3,648 tokens · 136 lines)
Spec Check: # H1 Title Pass ("Next.js")
Spec Check: > Summary Pass ("The React Framework for the Web")
## H2 Sections & Links 5 sections · 63 canonical markdown links
GET /llms-full.txt Not deployed
GET /.well-known/mcp.json Not advertised
JSON-LD Schema Entities SoftwareApplication, WebSite, Organization, ContactPoint, PostalAddress
Live Payload from https://nextjs.org/llms.txt
# Next.js

> The React Framework for the Web

Next.js is a React framework for building full-stack web applications. You use React Components to build user interfaces, and Next.js for additional features and optimizations.

## When to use nextjs.org

Use this site as the source of truth for:

- **Next.js APIs and configuration** — `next.config.js` options, file conventions (`page`, `layout`, `route`, `middleware`), route handlers, `next/*` module APIs, and CLI flags. Prefer these pages over reca

AI Crawler /robots.txt Access Matrix

Open to Search & Training · Bot Directory →
User-Agent Token Purpose / Operator Effective Directive
OAI-SearchBot ChatGPT Search Citations Allow: /
PerplexityBot Perplexity Answer Citations Allow: /
ChatGPT-User Live User Agent Browsing Allow: /
Claude-SearchBot Anthropic Search Grounding Allow: /
GPTBot Foundation Model Training Allow: /
ClaudeBot Foundation Model Training Allow: /
Google-Extended Gemini Training Control Allow: /
Applebot-Extended Apple Intelligence Training Allow: /
Meta-ExternalAgent Llama Training & Indexing Allow: /
CCBot Open Dataset Training Corpus Allow: /

HTTP Response & Handshake Timing

GET https://nextjs.org/
DNS Lookup 3 ms HTML Document 262.1 KB
TCP Connect 3 ms Script Tags 93
TLS Handshake 25 ms Stylesheets 4
Time to First Byte (TTFB) 61 ms Images (with alt) 9 / 17
Total Transfer 63 ms HTTP/3 (Alt-Svc) Not advertised

Edge Network & Application Stack

Header & DOM Signatures
Edge / Reverse Proxy Vercel
Application Framework Next.js
Server Header Vercel
Mail Provider (MX) Google Workspace
Telemetry Signatures Zero Client Trackers
TXT Verifications Google Search Console

TLS Certificate & HTTP Security Policy

Port 443 X.509
Certificate Issuer Let's Encrypt (84 days remaining)
Strict-Transport-Security Present
Content-Security-Policy Present
X-Content-Type-Options Present
X-Frame-Options Present
Referrer-Policy Present
Permissions-Policy Not set
SPF / DMARC Policy SPF: Yes · DMARC: Yes

Authoritative DNS & Document Head

A / AAAA / NS / Canonical
A (IPv4) 64.239.109.65
AAAA (IPv6) None
NS (Nameservers) ns2.vercel-dns.com, ns1.vercel-dns.com
HTML Title (39c) Next.js by Vercel - The React Framework
/sitemap.xml Valid XML Sitemap

Hosted /llms.txt Mirror & Status Badge

Platform Setup Guide →
1-Line <head> Tag (for Shopify, Webflow, Framer, Wix, Squarespace & WordPress):
Sitecube status for nextjs.org
GitHub / Docs Markdown Badge:
HTML Badge:

Technical Synthesis & Agentic Ingestion Analysis: nextjs.org

Automated Engineering Assessment

1. HTML-to-Token Efficiency & LLM Context Window Cost

An unauthenticated HTTPS GET request to https://nextjs.org/ returns an initial HTML payload of 262.1 KB, corresponding to approximately 67,086 UTF-8 tokens when ingested raw by an AI coding agent, retrieval pipeline, or headless browser. After stripping inline <script>, <style>, <svg>, and DOM markup tags, the human-readable text footprint measures 1,058 tokens (4.1 KB)—yielding an HTML Signal-to-Noise Ratio of 1.6%. Because nextjs.org publishes a valid /llms.txt manifest (measuring 3,648 tokens across 136 lines), AI retrieval agents that read /llms.txt instead of scraping the raw DOM reduce token consumption by 94.6%—cutting 1,000-read inference input costs from $83.8575 to $4.5600 at frontier model rates ($1.25/1M tokens), or $1.2768 on Gemini 4 Hydrogen ($0.35/1M).

2. Indexed Structure Inside nextjs.org/llms.txt

Sitecube’s specification linter verified 5 H2 section headings and 63 Markdown links inside https://nextjs.org/llms.txt under the primary heading "Next.js". Documented sections include: When to use nextjs.org</code>, <code>Documentation</code>, <code>Support Policy</code>, <code>Learn Next.js</code>, <code>Blog (Showing Last 2 Years). Key canonical endpoints referenced in the manifest include About Vercel (https://vercel.com/about), /openapi.json (https://nextjs.org/openapi.json), /docs/llms-full.txt (https://nextjs.org/docs/llms-full.txt), /docs/llms.txt (https://nextjs.org/docs/llms.txt), /.well-known/ai-catalog.json (https://nextjs.org/.well-known/ai-catalog.json).

3. Edge Delivery, TLS Handshake & Security Header Assessment

Traffic for nextjs.org resolves to 64.239.109.65 via Vercel running Next.js, achieving a measured Time to First Byte (TTFB) of 61 ms (DNS lookup: 3 ms, TCP connect: 3 ms, TLS handshake: 25 ms). The port 443 TLS certificate is issued by Let's Encrypt with 84 days remaining before expiration (valid through 2027-02-10). Outbound email authentication via SPF is present and DMARC (_dmarc.nextjs.org) is enforced.

Comparable Hosts in Sitecube ADA & /llms.txt Registry

Full ADA Index (36 hosts) →
Host ADA (1–100) ARS /llms.txt HTML Tokens Signal % Crawler Posture TTFB
github.com ADA 91 74% 7,165 tok 131,240 0.9% Open to Search & Training 27 ms
cloudflare.com ADA 88 96% 4,294 tok 333,631 0.1% Open to Search & Training 264 ms
vercel.com ADA 85 80% 3,722 tok 149,590 0.8% Open to Search & Training 66 ms
render.com ADA 83 90% 13,304 tok 190,754 1.1% Open to Search & Training 306 ms
shopify.com ADA 82 80% 3,161 tok 172,976 0.3% Open to Search & Training 106 ms
trendyflash.com ADA 81 87% 3,416 tok 12,412 14.7% Open to Search & Training 24 ms
nextjs.org ADA 80 74% 3,648 tok 67,086 1.6% Open to Search & Training 61 ms
supabase.com ADA 80 88% 879 tok 337,794 0.6% Open to Search & Training 58 ms
webflow.com ADA 80 72% 3,324 tok 138,361 2.6% Open to Search & Training 1022 ms
atlassian.com ADA 80 74% 6,652 tok 540,503 17.5% Open to Search & Training 2119 ms
redis.io ADA 79 80% 11,721 tok 427,454 2.5% Open to Search & Training 86 ms
neon.tech ADA 79 86% 7,418 tok 110,759 1.4% Open to Search & Training 236 ms