Technical SEO & crawling
Compare crawls
What it's for
A diff between two crawls: which issues were fixed, which are new, and which pages changed. The fastest way to see the impact of a release or content update.
When to use it
- After a deploy, to confirm you fixed more than you broke.
- When the health score moved and you need the «why».
How to use it
- Project → «Compare», pick a baseline and a later crawl.
- Read the «new issues» and «resolved issues» sections.
- Drill into any newly-regressed URL.
Reading your results
For each output: is it good, does it need improvement, or is it bad — and exactly what to do next.
New vs resolved issues
Good
Resolved > new: net improvement.
Needs improvement
Roughly even: the release was neutral — look closer.
Bad
New > resolved: the change introduced regressions.
What to do next
List the new issues, map each to the release, and roll back or patch the offending change.
Next steps
- File the new regressions as work; re-crawl after fixing.
- Make a clean crawl your new baseline going forward.