Agent Ready HTML

nextjs.org llms.txt

In short

nextjs.org serves a 50 KB llms.txt with 7 H2 sections and 305 links, graded A on the llmstxt.org structure (6 of 6 checks). It passes every check. The home page does not link it, so an agent that does not guess paths will not find it. No llms-full.txt was found. Read 4 November 2026.

llms.txt 50 KB, 340 lines

# Next.js Documentation

> Reference and guides for Next.js 16.4.5 […] the React framework for building full-stack web applications. Sections cover Getting Started, App Router, Architecture, and Community Resources.

@doc-version: 16.4.5
@doc-version-notes: Some features may have extended or refined behavior in minor or patch releases


## [Getting Started](https://nextjs.org/docs/app/getting-started)

Learn how to create full-stack web applications with the Next.js App Router.

- [Installation](https://nextjs.org/docs/app/getting-started/installation): Learn how to create a new Next.js application with the `create-next-app` CLI, and set up TypeScript, ESLint, and Module Path Aliases.
- [Project Structure](https://nextjs.org/docs/app/getting-started/project-structure): Learn the folder and file conventions in Next.js, and how to organize your project.
- [Layouts and Pages](https://nextjs.org/docs/app/getting-started/layouts-and-pages): Learn how to create your first pages and layouts, and link between them with the Link component.
- [Linking and Navigating](https://nextjs.org/docs/app/getting-started/linking-and-navigating): Learn how the built-in navigation optimizations work, including prefetching, prerendering, and client-side navigation, and how to optimize navigation for dynamic routes and slow networks.
- [Server and Client Components](https://nextjs.org/docs/app/getting-started/server-and-client-components): Learn how you can use React Server and Client Components to render parts of your application on the server or the client.
- [Fetching Data](https://nextjs.org/docs/app/getting-started/fetching-data): Learn how to fetch data and stream content that depends on data.
- [Mutating Data](https://nextjs.org/docs/app/getting-started/mutating-data): Learn how to mutate data using Server Functions and Server Actions in Next.js.
- [Caching](https://nextjs.org/docs/app/getting-started/caching): Learn how to cache data and UI in Next.js
- [Revalidating](https://nextjs.org/docs/app/getting-started/revalidating): Learn how to revalidate cached data using time-based and on-demand strategies.
- [Error Handling](https://nextjs.org/docs/app/getting-started/error-handling): Learn how to display expected errors and handle uncaught exceptions.
- [CSS](https://nextjs.org/docs/app/getting-started/css): Learn about the different ways to add CSS to your application, including Tailwind CSS, CSS Modules, Global CSS, and more.
- [Image Optimization](https://nextjs.org/docs/app/getting-started/images): Learn how to optimize images in Next.js
- [Font Optimization](https://nextjs.org/docs/app/getting-started/fonts): Learn how to optimize fonts in Next.js
- [Metadata and OG images](https://nextjs.org/docs/app/getting-started/metadata-and-og-images): Learn how to add metadata to your pages and create dynamic OG images.
- [Route Handlers](https://nextjs.org/docs/app/getting-started/route-handlers): Create custom request handlers with Next.js Route Handlers using the Web Request and Response APIs.
- [Proxy](https://nextjs.org/docs/app/getting-started/proxy): Use Next.js Proxy to rewrite, redirect, modify headers, or respond directly before a request completes.
- [Deploying](https://nextjs.org/docs/app/getting-started/deploying): Learn how to deploy your Next.js application.
- [Upgrading](https://nextjs.org/docs/app/getting-started/upgrading): Learn how to upgrade your Next.js application to the latest version or canary.

## [Guides](https://nextjs.org/docs/app/guides)

Learn how to implement common patterns and real-world use cases using Next.js

- [Adopting Partial Prefetching](https://nextjs.org/docs/app/guides/adopting-partial-prefetching): Learn how to enable Partial Prefetching and what changes for `<Link>`.
- [AI Coding Agents](https://nextjs.org/docs/app/guides/ai-agents): Learn how Next.js helps AI coding agents use current framework guidance, inspect applications, verify changes, and report issues.
- [Analytics](https://nextjs.org/docs/app/guides/analytics): Measure and track page performance using Next.js Speed Insights
- [Authentication](https://nextjs.org/docs/app/guides/authentication): Learn how to implement authentication in your Next.js application.
- [Authentication with Cache Components](https://nextjs.org/docs/app/guides/authentication-with-cache-components): Learn how to read the user session, show authenticated UI without slowing down the page, and cache data derived from the session when Cache Components is enabled.
- [Backend for Frontend](https://nextjs.org/docs/app/guides/backend-for-frontend): Learn how to use Next.js as a backend framework
- [Building](https://nextjs.org/docs/app/guides/building): Learn what happens when you run next build and how to read the build output.
- [Caching (Previous Model)](https://nextjs.org/docs/app/guides/caching-without-cache-components): Learn how to cache and revalidate data using fetch options, unstable_cache, and route segment configs for projects not using Cache Components.
- [CDN Caching](https://nextjs.org/docs/app/guides/cdn-caching): Learn how CDN caching works with Next.js, including what works today, cache variability, and the direction toward pathname-based cache keying.
- [CI Build Caching](https://nextjs.org/docs/app/guides/ci-build-caching): Learn how to configure CI to cache Next.js builds

First 45 of 340 lines. 2 spans shown as […] because the words or characters in them are rejected by this site's own style rules; the live file has them.

Parse graded A, 6 of 6

file: https://nextjs.org/docs/llms.txt

Next.js Documentation

Reference and guides for Next.js 16.4.5 […] the React framework for building full-stack web applications. Sections cover Getting Started, App Router, Architecture, and Community Resources.

7 sections, 305 links, an Optional section.

Ora's cached score: 79, grade B, scanned 2 November 2026.

The parse

nextjs.org lists 305 links: 299 point at nextjs.org or a relative path, 0 point elsewhere. The hosts it links most: nextjs.org (299).

H2 sectionLinks
[Getting Started](https://nextjs.org/docs/app/getting-started)18
[Guides](https://nextjs.org/docs/app/guides)80
[API Reference](https://nextjs.org/docs/app/api-reference)194
[Glossary](https://nextjs.org/docs/app/glossary)0
[Architecture](https://nextjs.org/docs/architecture)4
[Community](https://nextjs.org/docs/community)2
Optional1

Grade against the llmstxt.org structure

The file passes all six checks. The grade is the count of passed checks: six is A, five is B, four is C, three is D, fewer is F. It measures structure only. Whether any agent reads the file is a separate question, covered on the llms.txt reference.

CheckResultDetail
Starts with an H1 naming the site or projectPassH1: Next.js Documentation
Has a blockquote summary under the H1PassBlockquote summary found.
Has at least one H2 section that lists linksPass7 H2 sections, 6 with links.
At least 80 percent of links point at the same sitePass299 of 299 links stay on nextjs.org (100 percent).
Under 100 KBPass51255 bytes as served.
Plain markdown, no HTMLPassNo HTML document markers in the body.

Ora's cached score

Ora's cached report for nextjs.org gives it 79 of 100, grade B, scanned on 2 November 2026. Its Access layer, which holds the read-layer checks below, scored 53 of 58 check points. Read from GET ora.ai/api/score/nextjs.org on 5 November 2026. The score is Ora's, not this site's, and the structure grade above is a different measure: it grades the llms.txt file against the llmstxt.org proposal, while Ora's score covers the whole site. Ora's report for nextjs.org has every layer.

Read-layer checks in Ora's cached report for nextjs.org, 5 November 2026
Ora check (Access layer)ResultPoints
Sitemap existsPass2 of 2
Content without JavaScriptPartial2 of 3
Not blocked by bot detectionPass2 of 2
Markdown URL fallbackFail0 of 2
llms.txt existsPass1 of 1
llms.txt formattingPass2 of 2
JSON-LD structured dataPass4 of 4
Metadata completenessPass2 of 2
llms.txt links resolvePass2 of 2
Markdown alternate linkPass1 of 1
Redirect hygienePass1 of 1
Page token budgetPass1 of 1
Code fence validityPass1 of 1
Content behind authPass2 of 2
OpenAPI spec publishedPass7 of 7
Markdown agent docsPass1 of 1
Markdown negotiation with VaryPass1 of 1
Markdown for agent user agentsFail0 of 1
Agent crawler reachabilityPass2 of 2

Linking and the companion file

The home page of nextjs.org does not link the file in its HTML. Ora's lab found (2026-10-19) that 86 percent of llms.txt fetches by agents arrived through a link, so an unlinked file is mostly a file nobody opens. No llms-full.txt was found at the same root.

How it compares

At 50 KB the file is larger than 91 percent of the 2,529 plain-text llms.txt files in this edition, and its 305 links put it ahead of 93 percent of them on link count. The home page declares no generator. Size bucket: 50 to 100 KB. Curated example. Category: Framework.

Why it is in the index: Framework docs index scoped to the /docs subpath. Owner as listed: Next.js.

Live file: https://nextjs.org/docs/llms.txt. Read 4 November 2026. If the file has since changed or gone, the live URL is the authority; this page records what the crawl read on that date.

Sources

  1. nextjs.org llms.txt https://nextjs.org/docs/llms.txt, read 4 November 2026
  2. llms.txt proposal (llmstxt.org) https://llmstxt.org/, read 4 November 2026
  3. Tranco list 746WX (crawl universe) https://tranco-list.eu/list/746WX, read 4 November 2026
  4. Ora: AgentReady launch post (the 86 percent finding) https://ora.ai/blog/agentready-launch, read 4 November 2026
  5. Ora llms.txt (GET /api/score/{domain} looks up a cached score) https://ora.ai/llms.txt, read 5 November 2026

Last reviewed 5 November 2026