Site Audit
Site Audit
Site Audit turns a bounded crawl into connected evidence about health, issues, URLs, internal links, structure, history, automation, and page-level technical facts.
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.
Use the Site Audit operating loop
1
Select or verify the property and define the crawl boundary.
2
Run the crawler and confirm completion and coverage.
3
Use Overview and Statistics to choose an investigation.
4
Trace the finding through Issues, Pages, Internal Links, and URL details.
5
Document the intended fix and affected scope.
6
Run a comparable crawl and verify resolved, persistent, new, or returning evidence.
Choose the correct workbench view
| View | Primary question |
|---|---|
| Sites | Which property and verification boundary are active? |
| Overview | Where should investigation start? |
| Issues | Which rules and URLs are affected? |
| Pages | What does the crawler know about this URL set? |
| Statistics | Which distributions reveal a pattern? |
| Internal Links | Which source-target relationships explain the issue? |
| Compare | What changed between equivalent runs? |
| Crawls | Did collection complete reliably? |
| Automation | When should evidence refresh and notify? |
| Settings | What boundary will future crawls use? |
Read scope before score
Health and issue totals only describe the selected site and run. A narrower crawl, blocked section, failed fetches, or changed limits can improve a score while reducing evidence. Confirm scope and completion first.
Close work with verification
A ticket or code change is not proof. Use a comparable follow-up crawl, inspect the exact issue instances, and check that the intended fix did not create new indexability, linking, rendering, or performance regressions.