Agentify
On this page
Scanner

How the agent-readiness scan works

We diagnose public, machine-readable website signals. The result is a versioned technical baseline — never a certification, search ranking, or promise of model behavior.

What we check ​

The scan runs 18 checks across discovery, structured content, agent-like HTTP access, signals for your kind of business, and experimental surfaces.

  • #1 robots.txt availability
  • #2 AI crawler policy
  • #3 Content-Signal policy
  • #4 Sitemap
  • #5 Structured data availability
  • #6 Business-specific structured data
  • #7 Markdown content negotiation
  • #8 llms.txt
  • #9 MCP server card
  • #10 UCP profile
  • #11 OAuth discovery metadata
  • #12 Server-rendered content
  • #13 Agent user-agent access
  • #14 Page weight and response time
  • #15 Product feed discovery
  • #16 Platform fingerprint
  • #17 A2A agent card
  • #18 Language alternatives

How scoring works ​

The backend excludes not-applicable checks, removes unavailable weight from the assessed denominator, and stores the resulting score together with coverage and rubric version.

Coverage below 70% produces an incomplete, provisional result. Coverage below 30% produces no public score, and neither does a home page the site answers with a bot challenge or a refusal, whatever the coverage: a 401, 403 or 429 status, a known challenge vendor's page, or an error page saying access is denied. Benchmarks stay hidden until at least thirty scans of the same segment have finished with coverage of 70% or more.

  • Invisible: 0–24
  • Readable: 25–49
  • Callable-ready: 50–69
  • Ahead of the market: 70–100

What each result means ​

  • Pass — the expected public signal was verified.
  • Partial — a signal is present but incomplete.
  • Fail — an accessible surface confirmed a negative fact.
  • Unavailable — we could not reach a verdict; this is not a failure.
  • Not applicable — the check does not apply to this site or segment.

Non-scoring browser observations ​

When enabled, the separate browser-public-v2.0.0 layer passively renders public pages to observe JavaScript-only content, accessibility/form semantics, runtime/network health, metadata consistency, declared agent/API surfaces, and rendering cost. These findings are shown separately and never change the 18-check gtm-v1.0.0 score.

What the scan cannot tell you ​

A regional HTTP measurement can observe latency, output, metadata, and access at scan time. It does not prove worldwide availability, crawler identity enforcement, live stock or appointment correctness, or how any particular model will answer.

“Callable-ready” describes public discovery metadata. It does not mean that Agentify invoked a tool, authenticated a user, completed a booking, or verified checkout.

Checked, observed, and owner-only ​

  • Checked: public crawler policy, sitemap, substantive initial HTML, JSON-LD structure, and the optional llms.txt surface.
  • Observed only: public protocol declarations, passive browser structure, form semantics, and a bounded sample of visible-versus-structured facts.
  • Requires verified ownership: authentication, tool calls, forms, booking, checkout, payments, rate-limit testing, idempotency, receipts, internal logs, SLOs, and kill switches.

What we do not do ​

We do not log in, submit forms, click actions, bypass robots or access controls, scan non-standard ports, perform vulnerability probing, make bookings, execute checkout, or change the target site. The optional passive browser layer executes only the public page JavaScript needed to render it and blocks mutating requests.