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.
On this page
What we check
The rubric contains exactly 18 canonical checks across discovery, structured content, agent-like HTTP access, segment signals, and informational experimental surfaces.
#1robots — nominal weight 5#2ai policy — nominal weight 8#3content signal — nominal weight 4#4sitemap — nominal weight 6#5json ld presence — nominal weight 10#6vertical json ld — nominal weight 12#7markdown negotiation — nominal weight 8#8llms txt — nominal weight 2#9mcp server card — nominal weight 6#10ucp profile — nominal weight 6#11oauth discovery — nominal weight 4#12raw html ssr — nominal weight 10#13agent ua accessibility — nominal weight 8#14page weight latency — nominal weight 4#15store feed signals — nominal weight 4#16platform fingerprint — nominal weight 0#17a2a agent card — nominal weight 1#18hreflang locales — nominal weight 2
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. The browser never recomputes these values.
Coverage below 70% produces an incomplete, provisional result. Coverage below 30% produces no public score. Benchmarks stay hidden until the documented sample gate is reached.
- Invisible: 0–24
- Readable: 25–49
- Callable-ready: 50–69
- Ahead of the market: 70–100
The five result states
- 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-v1.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.
Limitations
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.