Site Audit
Crawl settings and domain verification
Settings define what future crawls are allowed to collect. A scope change is a data-contract change and must be documented before old and new runs are compared.
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.
Review crawl settings
Base URL and maximum URL count are high-impact boundaries. Changing them affects discovery, coverage, issue totals, health, structure, links, and later comparisons.
- Use the exact intended protocol and host.
- Set a limit large enough for the decision but operationally bounded.
- Document intentional exclusions.
- Run a new crawl after saving; old runs remain unchanged.
Complete domain verification
Follow the displayed challenge and confirm it through the supported server path. Verification status belongs to the property and authorization model, not only to the current browser session.
Understand quick checks
A quick check is intentionally restricted and useful for early evidence. It is not proof that a full verified crawl would have identical reach, links, or issue totals.
Handle a scope change
1
Record the old base URL, limit, and authorization.
2
Explain why the change is required.
3
Save the new settings.
4
Run and monitor the first new-scope crawl.
5
Do not present the first delta as organic improvement without scope qualification.