---
title: "Technical audit"
description: "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."
url: "https://tryindexplane.com/features/audit/"
markdown: "https://tryindexplane.com/features/audit.md"
---

# Technical audit

Technical audit & evidence

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](https://wordpress.org/plugins/indexplane/)
- [Browse the rule reference](https://tryindexplane.com/docs/rules/)

Plan: Free.

## 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.”

## Technical audit

### 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](https://tryindexplane.com/docs/rules.md)

### Honest scores

What IndexPlane can’t measure shows N/A, never a fake 100. Sitewide critical issues cap the score.

[Read how it works](https://tryindexplane.com/docs/getting-started.md)

### Template cohorts

Pages are grouped by template, so one broken layout is one finding with a URL count.

[Read how it works](https://tryindexplane.com/docs/monitoring.md)

## 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.