Why this matrix exists
The Lighthouse Agentic Browsing category makes some important signals visible. But it does not cover the full agentic readiness of a site.
The matrix prevents two errors:
- treating Lighthouse as a complete certification;
- ignoring Lighthouse because it is not an SEO ranking factor.
The right use sits between both. Lighthouse flags technical risks. The Pagup Score connects those risks to journeys, proof and governance.
Synthetic comparison
| Dimension | Lighthouse Agentic Browsing | Pagup Score |
|---|---|---|
| Machine surface | Checks selected points such as llms.txt or WebMCP |
Verifies alignment between machine files, pages, sitemap and policies |
| Accessibility | Observes programmatic signals | Connects accessibility to real agent tasks |
| Stability | Measures selected layout risks | Analyzes stability in critical journeys |
| Interface | Checks isolated elements | Verifies CTAs, forms, modals, errors and confirmations in context |
| Content | Weakly covered | Checks offer clarity, proof, limits and internal links |
| Governance | Barely covered | Checks maintenance rules and regression prevention |
Practical decision
When Lighthouse fails, the issue should be fixed or justified.
When Lighthouse passes, the site should still be tested through real scenarios: diagnostic request, service choice, proof reading, form completion, post-confirmation return.
The matrix therefore turns a technical result into an action plan. It protects against overclaim while using the right signal: machine readability is becoming measurable in standard web tooling.