A scan failed or got stuck β what now?
Common scan problems and fixes.
Updated
"Scan failed: site unreachable"
We couldn't load the URL. Causes:
- The site is down. Try again later.
- The site requires authentication. Add basic-auth credentials in Site β Settings β Authentication.
- The site blocks our user agent (
HelloCivicBot). Allowlist us in your WAF or robots.txt.
"Scan failed: timeout"
The site loaded but took too long (default: 60 seconds per page). For slow sites, bump the timeout in Site β Settings β Crawl options.
Stuck on "In progress" for a long time
Most scans finish in under 10 minutes. If it's been over 30:
- Refresh the page β sometimes the UI just hasn't caught up.
- Check Reports to see if it actually completed but the notification was missed.
- If it's truly stuck, contact support with the scan ID.
"Scan completed but missing pages"
Our crawler respects robots.txt, noindex headers, and any depth limits you've set. Check those first. If you want us to ignore robots, enable Settings β Ignore robots.txt (use sparingly β only on sites you fully control).
Was this article helpful?
Your feedback helps us improve our docs.

