nginx.org

scanned 7/25/2026, 8:40:47 PM · cached · refresh in 20h · rubric 2026.07.4

At risk

This is how AI agents (not browsers) experience nginx.org. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.

Discoverability

✉ Email me this report + alert me when it changes ↓

Top fixes

failCanonical URLDiscoverability

No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.

Fix: Add <link rel="canonical" href="…"> pointing at the primary URL of each page.

failMeta descriptionReadability

No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.

Fix: Add `<meta name="description" content="...">` to your primary pages. Agents frequently use it as a summary.

failJSON-LD presentStructured data

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

Fix: Add a <script type="application/ld+json"> describing the page (Organization, Article, Product, FAQPage).

warnllms.txt presentDiscoverability

Found /llms.txt but missing H1 header and markdown links.

Fix: Publish /llms.txt at your domain root. Build a spec-compliant one at /tools/llms-txt-generator.

failLink response headersDiscoverability

No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.

Fix: Emit `Link:` headers for canonical, alternate-language, and describedby relations. Agents that fetch HEAD-only or stream-render rely on these.

failSchema type coverageStructured data

Page looks like FAQPage; missing JSON-LD type(s): FAQPage.

Fix: Align JSON-LD type to page purpose. Product pages without Product markup are skipped by agent shopping flows.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever nginx.org’s agent-readiness score changes. Free, unsubscribe anytime.

Fix it

Generated, ready-to-ship files for the gaps above — copy them or download and drop them into your repo.

Add an llms.txt

Publish this at https://nginx.org/llms.txt

# nginx

> What nginx.org offers, in one or two sentences an AI agent can quote.

## Key pages
- [Home](https://nginx.org/)
- [nginx](https://nginx.org/)

## About
Describe what nginx.org does, who it's for, and the primary action you want an
agent to be able to complete. Keep it factual and current.

What the agent receives

The agent’s-eye view

nginx Join us for the first quarterly NGINX Community Call on July 22nd to connect and discuss NGINX development. english русский news about download security documentation faq books community enterprise community forum (new) x.com blog njs ingress controller gateway fabric nginx nginx (" engine x ") is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy server, and mail proxy server. Originally written by Igor Sysoev and distributed under the 2-clause BSD License . Enterprise distributions, commercial support and training are available from F5, Inc. Docs • Code • Install • Beginner's Guide Latest News 2026-07-15 nginx-1.30.4 stable and nginx-1.31.3 mainline versions have been released, with fixes for buffer overflow vulnerability when using map with regex (CVE-2026-42533), memory disclosure vulnerability when using ngx_http_slice_module (CVE-2026-60005), and use-after-free vulnerability when using ngx_http_ssi_module (CVE-2026-56434). 2026-06-23 njs-1.0.0 version has been released , deprecating the njs engine in favor of QuickJS, aligning exception classes between the engines, and hardening ngx.fetch() request validation. 2026-06-17 nginx-1.30.3 stable and nginx-1.31.2 mainline versions have been released, with fixes for buffer overflow vulnerability in the ngx_http_proxy_v2_module and ngx_http_grpc_module (CVE-2026-42055), and buffer overread vulnerability in the ngx_http_charset_module (CVE-2026-48142). Additionally, nginx-1.31.2 includes a fix for use-after-free vulnerability in the ngx_http_v3_module (CVE-2026-42530). 2026-05-22 nginx-1.30.2 stable and nginx-1.31.1 mainline versions have been released, with a fix for buffer overflow vulnerability in the ngx_http_rewrite_module (CVE-2026-9256). Older news Other NGINX Projects NGINX JavaScript (njs) extends nginx functionality with an ECMAScript-compatible interpreter for HTTP and Stream modules. Docs • Code NGINX Ingress Controller connects Kubernetes apps and services with rock solid request handling, auth, self-service CRDs, and easy debugging. Not to be confused with ingress-nginx, the separate Kubernetes community project. Docs • Code NGINX Gateway Fabric provides L4 and L7 routing capabilities in Kubernetes, implementing the Gateway API using NGINX as the data plane. Docs • Code

Show your score

Embed this badge on your site. It links back to this live scan and updates on every rescan.

<a href="https://agentspeed.com/scan/nginx.org"><img src="https://agentspeed.com/badge/nginx.org" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email, then a heads-up when nginx.org’s agent-readiness actually changes — a check regressing, or the composite dropping.

Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.

Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.

Full breakdown

11 pass2 warn14 fail3 skip

Show only failures

Discoverability

pass

robots.txt present

A robots.txt is reachable at the site root.

100/100

pass

robots.txt allows AI agents

All 8 answer-time access agents allowed.

100/100

fail

Content-Signal directivesemerging

No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.

0/100

warn

llms.txt present

Found /llms.txt but missing H1 header and markdown links.

60/100

pass

Sitemap present

sitemap.xml reachable and referenced from robots.txt.

100/100

fail

Link response headers

No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.

0/100

fail

Canonical URL

No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.

0/100

fail

MCP server cardemerging

No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.

0/100

fail

OAuth authorization metadataemerging

No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.

0/100

fail

OAuth resource metadataemerging

No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.

0/100

fail

API catalog / OpenAPIemerging

No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.

0/100

fail

Web Bot Authemerging

No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.

0/100

Readability

fail

Markdown negotiationemerging

Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.

0/100

pass

Text-to-markup ratio

Visible text is 34.8% of HTML weight (2323/6679 bytes). Healthy.

100/100

skip

Content without JavaScript

Browser pass unavailable; cannot measure JS dependency.

—

warn

Heading hierarchy

Heading issues: 1 skipped level(s).

75/100

pass

Cookie wall blocks content

No common consent-modal markers detected.

100/100

pass

Page title

A concise <title> is present (5 chars).

100/100

fail

Meta description

No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.

0/100

Structured data

fail

JSON-LD present

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

0/100

skip

Structured data validates

No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).

—

fail

Schema type coverage

Page looks like FAQPage; missing JSON-LD type(s): FAQPage.

0/100

Actionability

pass

Paywall / login wall

No paywall or login-wall detected on the landing URL.

100/100

fail

Agent Skills manifestemerging

No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.

0/100

fail

WebMCP actionsemerging

No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.

0/100

pass

Primary action reachable

Primary offering identified ("HTTP web server, reverse proxy, and load balancer") with price/CTA ("Download").

100/100

pass

Reachability

HTTP 200.

100/100

Performance

pass

Time to first byte

TTFB 138ms. Healthy.

100/100

skip

Full render time

Full-render time unavailable (browser pass skipped or failed).

—

pass

Page weight

Initial document is a lean 7 KB.

100/100

Beyond the scan

Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.

Start watching free →See plans