nodejs.org llms.txt
In short
nodejs.org serves a 15 KB llms.txt with 1 H2 section and 70 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 15 KB, 77 lines
# Node.js Documentation
> Node.js is an open-source, cross-platform JavaScript runtime environment that executes JavaScript code outside a web browser. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient for building scalable network applications.
Below are the sections of the API documentation. Look out especially towards the links that point towards guidance/introduction to the structure of this documentation.
## API Documentations
- [C++ addons](https://nodejs.org/docs/latest/api/addons.md): _Addons_ are dynamically-linked shared objects that can be loaded via the `require()` function as ordinary Node.js modules. Addons provide a foreign function interface between JavaScript and native code.
- [Assert](https://nodejs.org/docs/latest/api/assert.md): The `node:assert` module provides a set of assertion functions for verifying invariants.
- [Asynchronous context tracking](https://nodejs.org/docs/latest/api/async_context.md):
- [Async hooks](https://nodejs.org/docs/latest/api/async_hooks.md): We strongly discourage the use of the `async_hooks` API. Other APIs that can cover most of its use cases include:
- [Benchmark runner](https://nodejs.org/docs/latest/api/bench.md): The `node:bench` module supports defining and running JavaScript benchmarks in the current process, and running one benchmark file in a fresh child process. The module is only available when Node.js is started with the `--experimental-bench` flag and can only be imported with the `node:` scheme:
- [Buffer](https://nodejs.org/docs/latest/api/buffer.md): `Buffer` objects are used to represent a fixed-length sequence of bytes. Many Node.js APIs support `Buffer`s.
- [Child process](https://nodejs.org/docs/latest/api/child_process.md): The `node:child_process` module provides the ability to spawn subprocesses in a manner that is similar, but not identical, to `popen(3)`. This capability is primarily provided by the `child_process.spawn()` function:
- [Command-line API](https://nodejs.org/docs/latest/api/cli.md): Node.js comes with a variety of CLI options. These options expose built-in debugging, multiple ways to execute scripts, and other helpful runtime options.
- [Cluster](https://nodejs.org/docs/latest/api/cluster.md): Clusters of Node.js processes can be used to run multiple instances of Node.js that can distribute workloads among their application threads. When process isolation is not needed, use the `worker_threads` module instead, which allows running multiple application threads within a single Node.js instance.
- [Console](https://nodejs.org/docs/latest/api/console.md): The `node:console` module provides a simple debugging console that is similar to the JavaScript console mechanism provided by web browsers.
- [Crypto](https://nodejs.org/docs/latest/api/crypto.md): The `node:crypto` module provides cryptographic functionality that includes a set of wrappers for OpenSSL's hash, message authentication code (MAC), cipher, decipher, sign, verify, and key encapsulation mechanism (KEM) functions.
- [Debugger](https://nodejs.org/docs/latest/api/debugger.md): Node.js includes a command-line debugging utility. The Node.js debugger client is not a full-featured debugger, but simple stepping and inspection are possible.
- [Deprecated APIs](https://nodejs.org/docs/latest/api/deprecations.md): Node.js APIs might be deprecated for any of the following reasons:
- [UDP/datagram sockets](https://nodejs.org/docs/latest/api/dgram.md): The `node:dgram` module provides an implementation of UDP datagram sockets.
- [Diagnostics Channel](https://nodejs.org/docs/latest/api/diagnostics_channel.md): The `node:diagnostics_channel` module provides an API to create named channels to report arbitrary message data for diagnostics purposes.
- [DNS](https://nodejs.org/docs/latest/api/dns.md): The `node:dns` module enables name resolution. For example, use it to look up IP addresses of host names.
- [About this documentation](https://nodejs.org/docs/latest/api/documentation.md): Welcome to the official API reference documentation for Node.js!
- [Domain](https://nodejs.org/docs/latest/api/domain.md): **This module is pending deprecation.** Once a replacement API has been finalized, this module will be fully deprecated. Most developers should **not** have cause to use this module. Users who absolutely must have the functionality that domains provide may rely on it for the time being but should expect to have to migrate to a different solution in the future.
- [DTLS](https://nodejs.org/docs/latest/api/dtls.md): The `node:dtls` module provides an implementation of the Datagram Transport Layer Security (DTLS) protocol over UDP. DTLS provides TLS-equivalent security guarantees for datagram-based communication, including confidentiality, integrity, and authentication.
- [C++ embedder API](https://nodejs.org/docs/latest/api/embedding.md): Node.js provides a number of C++ APIs that can be used to execute JavaScript in a Node.js environment from other C++ software.
- [Performance measurement APIs](https://nodejs.org/docs/latest/api/perf_hooks.md): This module provides an implementation of a subset of the W3C Web Performance APIs as well as additional APIs for Node.js-specific performance measurements.
- [Permissions](https://nodejs.org/docs/latest/api/permissions.md): Permissions can be used to control what system resources the Node.js process has access to or what actions the process can take with those resources.
First 29 of 77 lines.
Parse graded A, 6 of 6
file: https://nodejs.org/llms.txt
Node.js Documentation
Node.js is an open-source, cross-platform JavaScript runtime environment that executes JavaScript code outside a web browser. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient for building scalable network applications.
1 section, 70 links, no Optional section.
Ora's cached score: 61, grade C, scanned 5 November 2026.
The parse
nodejs.org lists 70 links: 70 point at nodejs.org or a relative path, 0 point elsewhere. The hosts it links most: nodejs.org (70).
| H2 section | Links |
|---|---|
| API Documentations | 70 |
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.
| Check | Result | Detail |
|---|---|---|
| Starts with an H1 naming the site or project | Pass | H1: Node.js Documentation |
| Has a blockquote summary under the H1 | Pass | Blockquote summary found. |
| Has at least one H2 section that lists links | Pass | 1 H2 section, 1 with links. |
| At least 80 percent of links point at the same site | Pass | 70 of 70 links stay on nodejs.org (100 percent). |
| Under 100 KB | Pass | 15010 bytes as served. |
| Plain markdown, no HTML | Pass | No HTML document markers in the body. |
Ora's cached score
Ora's cached report for nodejs.org gives it 61 of 100, grade C, scanned on 5 November 2026. Its Access layer, which holds the read-layer checks below, scored 34 of 56 check points. Read from GET ora.ai/api/score/nodejs.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 nodejs.org has every layer.
| Ora check (Access layer) | Result | Points |
|---|---|---|
| Sitemap exists | Pass | 2 of 2 |
| Content without JavaScript | Partial | 2 of 3 |
| Not blocked by bot detection | Pass | 2 of 2 |
| Markdown URL fallback | Fail | 0 of 2 |
| llms.txt exists | Pass | 1 of 1 |
| llms.txt formatting | Pass | 2 of 2 |
| JSON-LD structured data | Fail | 0 of 4 |
| Metadata completeness | Partial | 1 of 2 |
| llms.txt links resolve | Pass | 2 of 2 |
| Markdown alternate link | Fail | 0 of 1 |
| Redirect hygiene | Pass | 1 of 1 |
| Page token budget | Pass | 1 of 1 |
| Code fence validity | Pass | 1 of 1 |
| Content behind auth | Pass | 2 of 2 |
| OpenAPI spec published | Fail | 0 of 7 |
| Markdown agent docs | Fail | 0 of 1 |
| Markdown negotiation with Vary | Fail | 0 of 1 |
| Markdown for agent user agents | Fail | 0 of 1 |
| Agent crawler reachability | Pass | 2 of 2 |
Linking and the companion file
The home page of nodejs.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 15 KB the file is larger than 71 percent of the 2,529 plain-text llms.txt files in this edition, and its 70 links put it ahead of 71 percent of them on link count. The home page declares no generator. Size bucket: 10 to 50 KB. Tranco rank 2,264. Category: Top 10,000, no category.
Live file: https://nodejs.org/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
- nodejs.org llms.txt https://nodejs.org/llms.txt, read 4 November 2026
- llms.txt proposal (llmstxt.org) https://llmstxt.org/, read 4 November 2026
- Tranco list 746WX (crawl universe) https://tranco-list.eu/list/746WX, read 4 November 2026
- Ora: AgentReady launch post (the 86 percent finding) https://ora.ai/blog/agentready-launch, read 4 November 2026
- 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