Run a focused crawl
A crawl inspects accessible pages and records technical observations. Confirm the selected website and its domain before starting. Review the action’s credit and service requirements.
Start with the intended site or supported target. A blocked, inaccessible or heavily script-dependent page may not provide the same information as a page you can see in a normal browser.
Inspect the results
- Wait for the crawl’s recorded completion state.
- Review the pages that were actually discovered.
- Open a finding and identify the affected URL.
- Check the evidence and severity.
- Compare it with the page’s intended purpose.
- Decide who should make the change and how to verify it.
A list of findings is not a complete instruction to change everything. Some observations depend on the website’s architecture, content or deliberate indexing choices. Prioritise issues that have a clear effect and an understandable remedy.
Use visual evidence
Desktop and mobile captures, where available, help identify layout differences and visible problems. Compare them with the underlying page and the time the capture was taken.
A screenshot cannot prove that a form, checkout or interaction works. Use the relevant website’s own test process for those behaviours.
Check the improvement
After a change is published on the website, run the appropriate follow-up observation. Compare the same target and relevant settings. Keep the earlier result as context rather than assuming a different date or device is a like-for-like comparison.
If the crawl did not reach a page, investigate access, redirects and the target URL before concluding that the page is missing. If the provider or allowance is unavailable, resolve that prerequisite instead of repeatedly submitting the same crawl.