Siteline FAQ
Questions you should be able to answer before trusting a score.
This page explains what the scanner is measuring, where its limits are, and what to do when a public score is not enough.
What does Siteline measure?
Siteline measures a public web page and a few obvious public routes across four pillars: Signal, Navigate, Absorb, and Perform.
Signal asks whether agents can detect and reach the site. Navigate asks whether they can orient and find the right public paths. Absorb asks whether they can take in meaningful content from the initial response. Perform asks whether they can complete a useful handoff or action.
What does Siteline not measure?
It does not replace a full audit, authenticated workflow testing, broad SEO tooling, or implementation planning.
What should I do if the score is weak?
Start with blockers and core issues first. If you need deeper guidance, move to the full audit.
Where do I go next?
Use the scanner for a baseline, the contact page for a human path, and the audit page when you need a fuller engagement.
How can someone managing autonomous agents use Siteline?
Siteline is useful for agent operators who need to quickly assess whether a target site is likely to be readable, navigable, and safe to hand a human through. Use the public scanner for quick checks, the CLI for terminal workflows, and the local MCP server when you want an agent to call Siteline directly as a tool.
What Siteline does today is evaluation and interpretation. What it does not do yet is host remote authenticated tooling, maintain long-term scan history, or execute actions on third-party sites.