The checks
All 113 checks by layer, with their standard and its status.
Agent-Ready Check runs 113 checks in 13 layers. Standards and their status were read on 2026-11-02. Severity: 3 essential, 2 important, 1 nice to have. JSON: https://isainative.dev/api/checks
Perception (14 checks)
How agents see the page: semantic HTML, accessibility tree, server vs rendered. Layer weight 3; book chapters 2,3.
perception.html-lang: <html lang> declares the page language. Severity 1; HTML Living Standard, Living Standard.perception.title: Page has a descriptive <title>. Severity 2; HTML Living Standard, Living Standard.perception.landmarks: Landmarks: one <main>, plus header/nav/footer. Severity 2; WAI-ARIA, W3C Recommendation.perception.headings: Heading outline: one <h1>, no skipped levels. Severity 2; HTML Living Standard, Living Standard.perception.form-labels: Every form control has an accessible name. Severity 3; WCAG, W3C Recommendation.perception.control-names: Buttons and links have accessible names. Severity 3; WCAG, W3C Recommendation.perception.click-divs: No click-only <div>/<span> controls. Severity 3; WAI-ARIA, W3C Recommendation.perception.img-alt: Images have alt text. Severity 1; WCAG, W3C Recommendation.perception.native-forms: Key forms are real <form>s with a submit button and action. Severity 2; HTML Living Standard, Living Standard.perception.server-html: Server HTML carries the content (not an empty JS shell). Severity 3; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter); heuristic.perception.rendered-parity: Rendered page and server HTML say the same thing. Severity 2; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter); needs a browser, heuristic.perception.axe-agent-rules: The 33 agent-relevant axe rules pass. Severity 3; Lighthouse agent-accessibility-tree (33 axe rules), Tool audit (rules from axe-core / WCAG); Lighthouseagent-accessibility-tree, needs a browser.perception.a11y-tree: Interactive elements appear in the accessibility tree with names and roles. Severity 3; WAI-ARIA, W3C Recommendation; needs a browser, heuristic.perception.focusable-controls: Custom controls are keyboard-focusable. Severity 1; WCAG, W3C Recommendation; needs a browser.
Crawler access (15 checks)
robots.txt groups per AI crawler, content signals, sitemaps, bot challenges. Layer weight 2; book chapters 4.
crawl.robots-txt: robots.txt is published. Severity 3; Robots Exclusion Protocol, RFC (Standards Track); isitagentreadyrobotsTxt.crawl.robots-syntax: robots.txt parses cleanly. Severity 2; Robots Exclusion Protocol, RFC (Standards Track).crawl.ai-bot-rules: robots.txt has rules for AI crawlers. Severity 2; Robots Exclusion Protocol, RFC (Standards Track); isitagentreadyrobotsTxtAiRules.crawl.ai-crawler-matrix: AI crawler policy per bot (training / search / user). Severity 2; Robots Exclusion Protocol, RFC (Standards Track); heuristic.crawl.content-signal: Content-Signal preferences are declared. Severity 2; Content Signals Policy, Vendor proposal; isitagentreadycontentSignals.crawl.content-signal-valid: Content-Signal values are well-formed. Severity 1; Content Signals Policy, Vendor proposal.crawl.aipref-usage: AI preferences (Content-Usage, IETF aipref) if present are valid. Severity 1; AI Preferences vocabulary + attachment, IETF WG draft.crawl.robots-meta: Homepage is not noindex/none for everyone. Severity 3; X-Robots-Tag / meta robots, De-facto convention.crawl.bot-challenge: Agents get the page, not a challenge. Severity 3; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter); heuristic.crawl.sitemap: A sitemap is published. Severity 2; Sitemaps protocol, Convention backed by the major search engines; isitagentreadysitemap.crawl.sitemap-valid: Sitemap is valid XML with <loc> URLs on this site. Severity 2; Sitemaps protocol, Convention backed by the major search engines.crawl.sitemap-lastmod: Sitemap carries honest lastmod dates. Severity 1; Sitemaps protocol, Convention backed by the major search engines.crawl.sitemap-in-robots: robots.txt names the sitemap. Severity 1; Robots Exclusion Protocol, RFC (Standards Track).crawl.tdmrep: TDM reservation (TDMRep) if used is valid. Severity 1; TDM Reservation Protocol, W3C CG report.crawl.rsl: RSL licence pointer if used resolves. Severity 1; RSL (Really Simple Licensing), Published specification.
Structured data (10 checks)
JSON-LD validity against schema.org and parity with visible content. Layer weight 2; book chapters 5.
structured.jsonld-present: Page has JSON-LD structured data. Severity 2; JSON-LD, W3C Recommendation.structured.jsonld-syntax: JSON-LD blocks parse as JSON. Severity 3; JSON-LD, W3C Recommendation.structured.jsonld-context: JSON-LD uses the schema.org context. Severity 1; JSON-LD, W3C Recommendation.structured.schema-types: @type values exist in schema.org. Severity 2; schema.org, Community vocabulary.structured.schema-properties: Properties exist in schema.org. Severity 1; schema.org, Community vocabulary.structured.key-properties: Key properties are filled for the main types. Severity 2; schema.org, Community vocabulary.structured.visible-parity: Structured data matches visible content. Severity 3; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter); heuristic.structured.identity: Homepage identifies the organisation (Organization/WebSite). Severity 1; schema.org, Community vocabulary.structured.canonical: Canonical URL is declared and consistent. Severity 1; HTML Living Standard, Living Standard.structured.meta-description: Meta description and Open Graph basics. Severity 1; Open Graph protocol, De-facto convention.
Agent-readable content (11 checks)
Markdown negotiation, llms.txt, Link headers, feeds. Layer weight 2; book chapters 6.
content.markdown-negotiation: Markdown via Accept: text/markdown. Severity 3; Markdown for Agents (Accept: text/markdown), Vendor convention on RFC 9110 negotiation; isitagentreadymarkdownNegotiation.content.markdown-vary: Negotiated responses send Vary: Accept. Severity 2; HTTP Semantics (content negotiation, Vary), RFC (Standards Track).content.markdown-quality: The Markdown is real Markdown with the page content. Severity 2; text/markdown media type, RFC (Informational); heuristic.content.markdown-alternate: Pages link their Markdown twin. Severity 1; llms.txt, Proposal.content.llms-txt: llms.txt is published. Severity 2; llms.txt, Proposal.content.llms-txt-format: llms.txt follows the format (H1, summary, link lists). Severity 2; llms.txt, Proposal; Lighthousellms-txt.content.llms-txt-links: llms.txt links resolve. Severity 2; llms.txt, Proposal.content.llms-full: llms-full.txt (optional). Severity 1; llms-full.txt, Convention (not in llms.txt v2).content.link-headers: Link headers point agents to resources. Severity 2; Web Linking, RFC (Standards Track); isitagentreadylinkHeaders.content.feeds: Feeds are discoverable (RSS/Atom/JSON Feed). Severity 1; RSS 2.0 / Atom (RFC 4287) / JSON Feed, RFC + conventions.content.caching: Responses support conditional requests. Severity 1; HTTP Semantics (content negotiation, Vary), RFC (Standards Track).
APIs (9 checks)
api-catalog, OpenAPI quality, problem+json, rate-limit headers. Layer weight 1.5; book chapters 7,10,13.
api.catalog: API catalog at /.well-known/api-catalog. Severity 2; api-catalog, RFC (Standards Track); isitagentreadyapiCatalog.api.catalog-valid: API catalog entries are complete. Severity 2; api-catalog, RFC (Standards Track).api.openapi: OpenAPI description is discoverable. Severity 2; OpenAPI Specification, Dated spec.api.openapi-valid: OpenAPI document is valid. Severity 2; OpenAPI Specification, Dated spec.api.openapi-agent-quality: Operations are described for agents. Severity 2; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter); heuristic.api.problem-json: Errors use problem+json (RFC 9457). Severity 1; Problem Details for HTTP APIs, RFC (Standards Track).api.ratelimit: Rate limits are announced in headers. Severity 1; RateLimit header fields, IETF WG draft.api.deprecation: Deprecation/Sunset headers are well-formed (if used). Severity 1; Deprecation header (+ Sunset RFC 8594), RFC (Standards Track).api.actionable-interface: Key actions have a machine interface. Severity 2; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter).
MCP (7 checks)
Server card, live initialize/tools/list probe, schemas, Origin validation. Layer weight 1; book chapters 8,10,11.
mcp.server-card: MCP server card is published. Severity 2; MCP Server Cards, Contested (SEP page "Final", extension repo "Experimental"); isitagentreadymcpServerCard.mcp.server-card-valid: Server card is complete and points to a live endpoint. Severity 2; MCP Server Cards, Contested (SEP page "Final", extension repo "Experimental").mcp.endpoint: MCP endpoint answers initialize. Severity 3; Model Context Protocol, Dated spec.mcp.protocol-version: Server speaks a current MCP protocol version. Severity 1; Model Context Protocol, Dated spec.mcp.tools-list: tools/list returns tools (public endpoints). Severity 2; Model Context Protocol, Dated spec.mcp.tool-schemas: Tool inputSchemas are valid JSON Schema objects with descriptions. Severity 2; Model Context Protocol, Dated spec.mcp.origin-validation: Endpoint rejects foreign Origin headers. Severity 2; Model Context Protocol, Dated spec.
WebMCP (8 checks)
Declarative and imperative tools found in a real browser. Layer weight 1; book chapters 9,10.
webmcp.tools: Page exposes WebMCP tools. Severity 2; WebMCP, W3C CG draft, Chrome origin trial; isitagentreadywebMcp, Lighthousewebmcp-registered-tools.webmcp.form-coverage: Forms declare toolname and tooldescription. Severity 2; Lighthouse WebMCP audits, Tool audit over a W3C CG draft; Lighthousewebmcp-form-coverage.webmcp.schema-validity: Declarative tool attributes and field names are valid. Severity 2; Lighthouse WebMCP audits, Tool audit over a W3C CG draft; Lighthousewebmcp-schema-validity.webmcp.tool-schemas: Imperative tools have valid input schemas. Severity 2; WebMCP, W3C CG draft, Chrome origin trial; needs a browser.webmcp.tool-count: Tool count stays manageable (<= 40). Severity 1; Lighthouse WebMCP audits, Tool audit over a W3C CG draft; needs a browser.webmcp.descriptions: Tool descriptions tell an agent when to use them. Severity 1; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter); heuristic.webmcp.annotations: Tools carry readOnlyHint / untrustedContentHint annotations. Severity 1; WebMCP, W3C CG draft, Chrome origin trial; needs a browser.webmcp.origin-trial: WebMCP origin-trial token (for Chrome) if WebMCP is used. Severity 1; WebMCP, W3C CG draft, Chrome origin trial.
Discovery (9 checks)
ARD, Agent Skills, A2A, DNS-AID, well-known hygiene. Layer weight 1; book chapters 11.
discovery.ard: ARD manifest is discoverable. Severity 2; Agentic Resource Discovery (ARD), Proposal; isitagentreadyard, Lighthouseard-schema.discovery.ard-valid: ARD manifest is valid. Severity 2; Agentic Resource Discovery (ARD), Proposal.discovery.agent-skills: Agent Skills index is published. Severity 2; Agent Skills Discovery, Vendor proposal; isitagentreadyagentSkills.discovery.agent-skills-valid: Skill entries are complete and digests match. Severity 2; Agent Skills Discovery, Vendor proposal.discovery.a2a-card: A2A Agent Card (opt-in). Severity 1; A2A (Agent2Agent) Agent Card, Dated spec; isitagentreadya2aAgentCard.discovery.dns-aid: DNS-AID records under _agents. Severity 1; DNS for AI Discovery (DNS-AID), Individual draft; isitagentreadydnsAid.discovery.poppy: Personal Agent Protocol manifest (informational). Severity 1; Personal Agent Protocol (poppy.json), Proposal; isitagentreadypersonalAgentProtocol.discovery.soft-404: Unknown paths return 404 (no soft-404s). Severity 2; Well-Known URIs, RFC (Standards Track).discovery.wellknown-types: Well-known JSON files are served as JSON. Severity 1; Well-Known URIs, RFC (Standards Track).
Commerce (9 checks)
UCP, ACP, x402, MPP, AP2, product data (scored only on shops). Layer weight 1; book chapters 12.
commerce.detected: Commerce signals detected. Severity 1; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter).commerce.product-data: Products/offers have price, currency and availability. Severity 2; schema.org, Community vocabulary.commerce.ucp: UCP business profile. Severity 2; Universal Commerce Protocol, Dated spec (Lodging: draft); isitagentreadyucp.commerce.ucp-valid: UCP profile lists capabilities and reachable endpoints. Severity 1; Universal Commerce Protocol, Dated spec (Lodging: draft).commerce.acp: ACP discovery document. Severity 1; Agentic Commerce Protocol, Beta (discovery path is the scanner's convention); isitagentreadyacp.commerce.x402: x402 payment-required responses. Severity 1; x402, Dated spec; isitagentreadyx402.commerce.mpp: MPP payment info in OpenAPI. Severity 1; Machine Payments Protocol, Vendor-led open protocol; isitagentreadympp.commerce.ap2: AP2 extension in the A2A card. Severity 1; Agent Payments Protocol (AP2), Extension of A2A and UCP; isitagentreadyap2.commerce.vrp: Vacation Rental Protocol offers (informational). Severity 1; Vacation Rental Protocol, Single-maintainer draft.
Identity & auth (6 checks)
OAuth AS/PRM metadata, PKCE, CIMD, auth.md, Web Bot Auth. Layer weight 1; book chapters 14,15.
identity.oauth-discovery: OAuth/OIDC authorization server metadata. Severity 2; OAuth 2.0 Authorization Server Metadata / OIDC Discovery, RFC (Standards Track); isitagentreadyoauthDiscovery.identity.protected-resource: OAuth Protected Resource Metadata. Severity 2; OAuth 2.0 Protected Resource Metadata, RFC (Standards Track); isitagentreadyoauthProtectedResource.identity.pkce-s256: Authorization server supports PKCE S256. Severity 2; OAuth 2.1 (PKCE S256), IETF WG draft (normative in MCP).identity.client-registration: Agent clients can register (CIMD preferred over DCR). Severity 1; Client ID Metadata Document, IETF WG draft (required path in MCP 2026-07-28).identity.auth-md: auth.md agent registration. Severity 1; auth.md, Vendor proposal; isitagentreadyauthMd.identity.web-bot-auth: Web Bot Auth key directory (for sites that send bots). Severity 1; Web Bot Auth (HTTP Message Signatures directory), IETF WG draft; isitagentreadywebBotAuth.
Security (6 checks)
Hidden prompt injection, tool annotations, HTTPS, headers. Layer weight 2; book chapters 16.
security.hidden-injection: No hidden prompt-injection text. Severity 3; OWASP Top 10 for LLM Applications (LLM01 prompt injection), Community guidance.security.injection-in-machine-files: Machine-readable files carry no instructions to agents. Severity 2; OWASP Top 10 for LLM Applications (LLM01 prompt injection), Community guidance.security.tool-annotations: Destructive tools are marked as such. Severity 2; Model Context Protocol, Dated spec.security.https: HTTPS with HSTS. Severity 2; HTTP Strict Transport Security, RFC (Standards Track).security.headers: Baseline security headers. Severity 1; Content Security Policy Level 3, W3C WD (CSP2 Rec).security.security-txt: security.txt contact. Severity 1; security.txt, RFC (Informational).
Privacy & consent (4 checks)
Policy links, consent overlays, GPC, human confirmation. Layer weight 1; book chapters 17.
privacy.policy-link: Privacy policy and terms are linked machine-readably. Severity 1; IANA link relations (privacy-policy, terms-of-service), RFC (Informational) + IANA registry.privacy.consent-overlay: Consent banner does not block content for agents. Severity 2; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter); needs a browser, heuristic.privacy.gpc: Global Privacy Control support declared. Severity 1; Global Privacy Control, W3C Working Draft.privacy.human-confirmation: Risky tools ask a human to confirm. Severity 1; WebMCP, W3C CG draft, Chrome origin trial; heuristic.
Performance & stability (5 checks)
CLS, TTFB, compression, redirects, page weight. Layer weight 1; book chapters 3,19.
performance.cls: Layout is stable (CLS). Severity 2; Cumulative Layout Shift, Metric (W3C draft API); Lighthousecumulative-layout-shift, needs a browser.performance.ttfb: Server responds quickly (TTFB). Severity 1; Web Vitals (TTFB guidance), Guidance.performance.compression: Text responses are compressed. Severity 1; HTTP content coding (gzip, br, zstd), RFC (Standards Track).performance.redirects: Few redirects to the homepage. Severity 1; HTTP Semantics (content negotiation, Vary), RFC (Standards Track).performance.page-weight: HTML is a reasonable size. Severity 1; The Agent-Ready Web (book guidance), Book recommendation (opinion, sourced per chapter).