AgenticReadiness test site
A deployable target for the AgenticReadiness Lumar custom metric. Every signal it detects is exposed as a correctly- and an incorrectly-implemented page, for end-to-end verification of a real crawl.
correct.* (all valid), broken.* (all present-but-wrong) and authbroken.*
(valid except a broken MCP OAuth chain) hosts, plus the alt1…alt9 scenario hosts, which serve the
alternative failure shapes no single artifact can hold at once. Locally, add
?mode=…, ?scenario=… or ?era=…. This host’s configuration is
published at /__agentic-scenarios.json.
Composition pages
Every per-URL technology on one URL. Isolated fixtures prove each checker works; only these show whether they interfere — whether a page’s Product JSON-LD confuses the editorial-metadata reader, or one malformed block suppresses the technologies around it.
- Kitchen sink — all valid
Canonical, Link header, SSR, Markdown twin, JSON-LD, schema:Action, Product, editorial metadata and WebMCP together, every one of them correct. The negative control.
- Kitchen sink — mixed validity
The same technologies, some right and some wrong, competing for one parser.
Discoverability
Can an agent find and enumerate the site — canonical URLs, Link headers, and the sitemap.
-
page-parsed
Canonical URL
A single, absolute, in-<head> <link rel="canonical"> (and/or Link header) pointing at the preferred URL.
-
page-parsed
Link header (RFC 8288)
A well-formed Link: response header — angle-bracketed URI, a usable rel, resolvable target.
-
site-wide file
XML sitemap
A sitemaps.org sitemap discovered via robots.txt Sitemap: or /sitemap.xml — well-formed, namespaced, absolute <loc>s.
Content
Is the content legible to a no-JS agent — server rendering, a Markdown twin, JSON-LD, declared language and encoding.
-
page-parsed
Server-side rendering
The meaningful content is present in the raw HTTP response, not only after JavaScript runs.
-
page-parsed
Markdown twin
A <link rel="alternate" type="text/markdown"> advertising a low-token Markdown copy of the page.
-
page-parsed
JSON-LD structured data
Parseable schema.org JSON-LD with an @context, an @type, ISO-8601 dates, and any Google-required props.
-
page-parsed
Language & encoding
A valid BCP 47 <html lang> and an early UTF-8 <meta charset> so agents read the text correctly.
Access
Does the site tell agents the rules — robots.txt, per-bot rules, Content-Signal, ai.txt, and TDMRep.
-
site-wide file
robots.txt
A well-formed robots.txt: directives inside User-agent groups, known keys, proper key: value syntax.
-
site-wide file
Per-bot AI rules
Correctly-spelled, non-contradictory groups for named AI bots (GPTBot, ClaudeBot, …) in robots.txt.
-
site-wide file
Content-Signal
Cloudflare/AIPREF Content-Signal directives in robots.txt with valid yes/no values inside a group.
-
site-wide file
ai.txt
A Geodocs ai.txt with parseable Key: value directives, absolute Source-url, valid attribution flags.
-
site-wide file
TDMRep
A W3C TDMRep /.well-known/tdmrep.json: an array of rules with location and a numeric tdm-reservation.
Capabilities
Can an agent act — WebMCP tools, schema:Action, an MCP server card, OpenAPI, NLWeb, and MCP authorization.
-
page-parsed
WebMCP
In-page tools (declarative <form toolname> or imperative registerTool) with names, descriptions, schemas.
-
page-parsed
schema:Action
A schema.org potentialAction (e.g. SearchAction) with a target EntryPoint and query-input.
-
site-wide file
MCP server card
A /.well-known/mcp.json advertising a connectable remote MCP endpoint (absolute URL + transport).
-
site-wide file
OpenAPI
A machine-readable OpenAPI 3.x document with callable, uniquely-identified, typed operations.
-
live probe
NLWeb
A natural-language query API: a REST /ask endpoint and an MCP /mcp endpoint advertising an ask tool.
-
live probe
MCP authorization
A protected MCP endpoint's OAuth discovery chain: 401 → protected-resource metadata → authorization-server metadata (PKCE).
Commerce
Can an agent transact — Product/Offer schema and a Universal Commerce Protocol manifest.
-
page-parsed
Product / Offer schema
schema.org Product with a complete Offer: numeric price, ISO-4217 currency, availability enum.
-
site-wide file
Universal Commerce Protocol
A /.well-known/ucp manifest with a dated version, connectable transports, and reverse-domain capabilities.
Trust
Can an agent trust the source — editorial provenance, Web Bot Auth keys, and a signed A2A agent card.
-
page-parsed
Editorial metadata
schema.org Article provenance: a resolvable author and publisher and valid ISO-8601 dates.
-
site-wide file
Web Bot Auth
A JWKS at /.well-known/http-message-signatures-directory publishing usable public verification keys.
-
site-wide file
A2A agent card
An /.well-known/agent-card.json with the required fields, a coherent endpoint, and a valid signature (if signed).