Technical audit & evidence
Every finding proves itself.
Each finding names its rule, lists the affected URLs and shows the served evidence, so you can defend it to a client or a developer.
Download free →Free Free. Compare plans →
THE PROBLEM
Traffic lights don’t tell you what to fix.
- “The score said 100. The site was set to noindex.”
- “The developer asked for proof and I had a screenshot of a red dot.”
- “Two thousand warnings and no idea which ten matter.”
HOW IT WORKS
Technical audit
01
Rule ID, affected URLs, served evidence
Every finding links to its rule page and the exact HTML or header that triggered it.
Read how it works →
02
Honest scores
What IndexPlane can’t measure shows N/A, never a fake 100. Sitewide critical issues cap the score.
Read how it works →
03
Template cohorts
Pages are grouped by template, so one broken layout is one finding with a URL count.
Read how it works →
PROOF
What you can check for yourself.
- Rules are versioned; false positives are pinned to a rule version.
- Evidence types are labelled: deterministic, observed or heuristic.
- Reports “index-eligible”, never claims a URL is indexed.
Free Free. Compare plans →