Site Audit
Crawl automation and alerts
Automation turns a one-off audit into an owned review rhythm. Alerts should point to evidence that someone is responsible for investigating.
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.
Configure useful automation
Choose a crawl cadence that matches release frequency, risk, and review capacity. A schedule that nobody reviews creates cost and noise rather than monitoring.
- Confirm the property and crawl boundary.
- Start with a stable successful baseline.
- Name an owner for failures and findings.
- Avoid overlapping schedules that measure the same scope without purpose.
Choose alert coverage
Alert on severity, issue families, or material changes that can trigger a decision. Small expected fluctuations should remain in the run history rather than notifying the whole team.
Assign recipients
Recipients should be able to investigate or coordinate the response. Keep the list small, maintain ownership when teams change, and avoid using alerts as unowned task creation.
Respond to an alert
1
Open the exact property and run.
2
Confirm completion and comparable coverage.
3
Read the changed issue group and representative URLs.
4
Decide whether the evidence needs action, monitoring, or an accepted exception.
5
Verify after the next comparable crawl.