Compare two crawls
Diff any two audits to see what was fixed and what regressed. Four figures at the top — score change, old score, resolved issues, and new issues — then a per-category breakdown showing before, after, and change.Resolved and new are the numbers that matter. A crawl that clears 30 issues and introduces 28 barely moves the score while telling you something important about your release process.The comparison is only meaningful between crawls with the same target URL and the same page limit. A 500-page crawl against a 50-page one reports hundreds of “new” issues that were always there and simply weren’t reached before.
Page detail
Everything the crawler recorded for a single URL, grouped into content, technical, links and media, SEO, and performance. This is the diagnostic view — when an issue doesn’t make sense, the underlying measurement usually explains it.Three fields do most of the work: Word Count exposes a page flagged as thin whose text is actually client-rendered, Canonical URL catches a page quietly pointing at another, and Render-Blocking Scripts is normally the real cause behind a high load time.Duplicate content and broken resources
Two dedicated views, separated out of the general issue list because they’re investigated differently.The score
Audits now produce a 0–100 score. It starts at 100 and deducts by severity — 2 points per error, 0.5 per warning, 0.1 per notice — with the deduction from each severity capped at 50, 30 and 10 respectively. Three bonuses add back five points each for HTTPS, arobots.txt, and a sitemap.Because the deductions cap, a site with 25 errors scores the same as one with 250. The score is a trend indicator; the issue list is what you work from.