15 points
DOM and layout stability
Initial structure, hydrated DOM and visual rendering remain coherent enough to prevent action errors.
Reference model
The Agentic Readiness Score turns a technical intuition into an observable grid: can an agent find the right resource, understand the interface, choose an action and execute it without critical ambiguity?
Scoring model
The score does not predict SEO ranking. It measures the operational ability of a site to be understood, navigated and operated by agents.
15 points
Initial structure, hydrated DOM and visual rendering remain coherent enough to prevent action errors.
15 points
What is visible, what is coded and what is exposed in the accessibility tree express the same intent.
15 points
Links, buttons, fields and states use native elements and explicit programmatic names.
15 points
Roles, labels, relationships, states and form errors let an agent understand available actions.
10 points
A critical action produces a predictable, readable result attached to the right context.
10 points
Critical actions and content do not depend on late, fragile or divergent client-side state.
10 points
Primary, secondary and dangerous actions are distinguishable without creating false interaction signals.
5 points
Key resources are available through sitemaps, internal links, structured data and readable machine surfaces.
5 points
Complex transactional journeys are evaluated for future exposure as structured tools.
Lighthouse vs Pagup Score
Lighthouse Agentic Browsing makes selected signals visible. The Pagup Score places them inside a broader grid: journeys, proof, governance, editorial coherence and real action.
Technical signal
Accessibility, stability, programmatic names, surfaces such as llms.txt and WebMCP readiness can signal an agentic construction level.
Journey risk
An agent must find the right service, understand context, choose a CTA, fill a form and interpret confirmation without critical ambiguity.
Governance
The result should prioritize remediation and prevent regressions, not produce a decorative grade or a ranking promise.
Related reading
Read the Lighthouse Agentic Browsing audit article and the Lighthouse vs Pagup Score matrix to separate tool audit, public score and journey verification.
Reading the result
The result should prioritize remediation, not create a cosmetic grade. A useful bad score is better than an unverified good one.
0-39
The site may be visually correct, but agents may misinterpret or mis-execute critical journeys.
40-59
Some signals are present, but the interface still relies too much on human context, JavaScript or fragile inference.
60-79
The main journeys are readable and actionable, but governance and testing still need to reduce regressions.
80-100
The site exposes a stable, semantic, coherent and testable structure for humans, search engines and AI agents.
Self-diagnostic
Only check what you can technically verify. This estimate does not replace an audit: it helps determine whether the risk should be handled now.
Technical sources
The grid aligns with a documented shift: agents read pages through multiple channels and need to act on stable interfaces.
Google describes screenshots, raw HTML and the accessibility tree as major reading paths for agents.
Read the web.dev documentationLighthouse now documents audits related to agentic browsing: layout stability, accessibility for agents, llms.txt and WebMCP.
Read the Chrome documentationNext step
The agentic readiness audit checks real journeys, not only declared intentions.