Skip to main content

Scan Progress

Open in QuickMonitoring→ Sites → [Your Site] → Scans → [Select a scan]

QuickMonitoring runs scans asynchronously. You can watch real-time progress — which module is currently running, how many pages have been crawled, and estimated completion. You don't need to stay on the page; the scan continues in the background and results are ready when you come back.

What you'll see​

While a scan is running, the scan detail page shows a live progress indicator:

  • Current module — which phase is active: Crawling → Error Detection → Validation → Link Validation → API Metrics → Spell Check → Context Analysis
  • Pages processed — count of pages crawled so far
  • Module status — each module listed with its state (Pending / Running / Completed / Failed)
  • Overall status — Running / Completed / Failed

When the scan completes, the status updates and all sidebar sections become available. If you have email notifications configured (Phase 2), you'll get an email when it's done.

How to use it​

  1. Start a scan
  2. Stay on the scan detail page to watch real-time progress — the UI updates automatically
  3. Or leave the page — the scan continues in the background. Come back when you're ready.
  4. When the status shows "Completed", select the scan to see its crawled pages — then use the sidebar to navigate to Errors, Validation, Links, API Metrics, and Spelling

For long scans (large sites, full module suite), leave it running and come back in a few minutes. There's no need to stay on the page.

Pass condition​

✅ You've earned this achievement when you observe a scan transitioning through at least two progress states — for example, "Crawling" → "Analyzing" — before completing.

Common issues​

  • Scan stuck on "Crawling" for over 5 minutes — Your site may have very deep pagination, infinite scroll that generates new URLs, or the crawler is hitting rate limits on your server. Try: reducing crawl depth, adding pagination URL patterns to the exclusion list, or checking whether the site has rate limiting on the crawler's IP.

  • "Failed" status with no error message — The most common cause is the site becoming unreachable during the scan — a firewall, a server restart, or a deployment happening mid-scan. Check that your site is publicly accessible and re-run the scan. If it fails again, check the scan logs for the last successful module.

  • One module fails, others complete — Each module is independent. If Spell Check fails, the rest of the scan still completes. Check the failed module's status and re-run a scan with only that module enabled to isolate the issue.

  • Scan completed but some sections are empty — If a module completed but returned no data, the section will show an empty state rather than an error. This is normal on sites where that check produces no findings (e.g. a static site with no API calls, a site with no spelling errors).