Audit History

Audit History is the trend of your audit runs over time. Each run you complete is recorded, so you can see whether your work is moving the numbers in the right direction — or whether a deploy quietly made things worse. A single audit tells you the state of your site today; the history tells you whether that state is improving.

What you’ll see

Every historical run is listed newest first, with the key metrics for that run:

Column	What it tells you
Date	When the run completed.
Overall score	The headline audit score for that run.
Critical issues	How many critical-severity findings were open at the time.
Total issues	The full finding count across all severities.
Pages crawled	How much of the site that run covered.

Reading across a row gives you one run’s snapshot. Reading down a column gives you the trend — the part that actually matters.

How to use it

Use the history three ways:

• Confirm a fix landed. After a remediation push, compare the run before your changes to the run after. If the score rose and the relevant counts fell, the fix worked. If nothing moved, the change didn’t reach the pages you expected.
• Catch regressions. A score drop or a jump in criticals right after a deploy is your early warning that the release introduced a technical-SEO problem. The history surfaces it before it costs you.
• Show progress. The trend over weeks is the cleanest way to demonstrate to stakeholders that the work is paying off, without asking them to read individual findings.

One caveat on pages-crawled: if that number changes sharply between runs, the score and issue counts aren’t strictly comparable — a much larger crawl can surface more issues simply because it covered more ground. Check it before reading too much into a swing.

Next steps

• Comparing two audit runs — diff two specific runs finding-by-finding
• My audit score dropped — what to check when the trend turns the wrong way
• Theme Breakdown — group the latest run’s findings by root cause