Site Audit
Crawl execution, history, and comparison
Crawl history separates collection quality from SEO evidence and makes verification possible across equivalent run snapshots.
Bounded crawl
Keep property, authorization, run, and crawl coverage visible.
Traceable evidence
Move from summaries to rules, URLs, links, assets, and raw facts.
Comparable verification
Confirm fixes with another crawl using an equivalent scope.
Read crawl execution and history
The Crawls view shows run status, progress, activity, discovered and processed scope, operational problems, and historical runs. Select an older run to inspect its saved evidence without presenting it as the latest state.
- Running data is incomplete by definition.
- Cancelled and failed runs need error context.
- Coverage can materialize after fetching.
- Older-run banners protect against accidental current-state claims.
Separate crawler problems from SEO findings
Timeouts, blocked requests, authorization failures, queue delays, and materialization gaps can reduce evidence. Resolve or document them before concluding that a section is healthy or absent.
Compare equivalent runs
Compare identifies new, persistent, resolved, and changed evidence between selected runs. The comparison is defensible only when property boundary, authorization, limits, and completion are comparable.
| State | Meaning |
|---|---|
| New | Observed in the newer run but not the baseline. |
| Persistent | Observed in both runs. |
| Resolved | Observed in the baseline but not the newer run. |
| Changed | The underlying page or evidence differs across runs. |
Verify a remediation
1
Record the baseline run and issue instances.
2
Implement the intended change.
3
Run the same property and scope.
4
Confirm completion and coverage.
5
Check resolved instances and new regressions.
6
Keep both run IDs in the handoff or report.