Site Audit Improvements

What's new# Link to this section

• Audit comparison — compare two runs directly to see exactly which findings a deploy resolved and which it introduced.
• Crawl progress detail — the progress panel now reports the current fetch rate and the reason the crawler is waiting, so a slow crawl is distinguishable from a stuck one at a glance.

Improvements# Link to this section

• Adaptive rate limiting responds faster to server slowdown, reducing pressure on the site being crawled.
• JavaScript rendering coverage improved for client-side routed applications.
• Redirect chains are now reported with the full hop sequence rather than only the endpoints.
• Crawl logs are filterable by response code.

Fixes# Link to this section

• Pages returning a valid response after a retry are no longer double-counted in the health score.
• Canonical conflict detection no longer flags a self-referencing canonical on a paginated series.
• Audits stopped by an exhausted allowance now report clearly as partial rather than failed.

Known limitations# Link to this section

• Audit comparison requires both runs to have used the same page limit to be meaningful; runs with different limits are compared with a warning.