Run scans from Project Pages

Before starting a scan

A scan is the automated browser run that turns reviewed Project Pages into evidence. It should use the current project boundary, not a fresh guess at every URL on the internet. Use this page after the project has domain authorization when required, plan or credit readiness and [Project Pages review](/docs/projects/accepted-scan-scope). If any of those gates is missing, fix that state before starting the scanner.

Start from Project Pages

Follow the path `Projects → Project detail → Project Pages → Actions → Run whole scan`.

1. Open /projects and choose the project. Result: the project detail page keeps the domain, Project Pages, Scans and Actions in one place.
2. Review Project Pages before starting the run. Result: only public same-domain pages are scanner input.
3. Check Actions for Run whole scan and any billing, domain or scanner safety blockers. Result: the next action is visible without another setup page.
4. Click Run whole scan once. Result: WebRiskOps queues one scan and prevents duplicate worker demand for the same project.
5. Open /scans and click Open scan. Result: the scan detail page shows queued, running or completed state, current page and artifacts.
6. Wait for Completed before opening the report path. Result: screenshots, HTML snapshots, console and network evidence and skipped-page reasons can be tied to the project pages.

Watch scan status

Use `/scans/{scanRun}` when you need the run state, worker progress, current page, queue timing and artifact links.

• Queued or running status means the scanner has accepted the job or is collecting browser evidence. Wait for the current run instead of starting another scan.
• Completed status means the run has terminal evidence for report generation or review.
• Active scan means another queued or running scan already exists for the project. Open that scan instead of creating a duplicate run.
• Plan required means open [Billing](/billing), resolve the automated plan or credit blocker and return to the project after billing state is ready.

Understand skipped or failed pages

Skipped and failed states should explain what happened without asking the customer to guess.

• Skipped outside boundary means the page was not inside the project domain, public page list or path rules.
• Scanner failed means the run could not collect enough evidence. Retry only after the failure reason says the target is reachable and the project boundary is still correct.
• Rendering blocked means browser rendering could not observe the page reliably. Use [Browser rendering](/docs/projects/browser-rendering) before retrying.
• Evidence incomplete means read the available screenshots, HTML snapshots and console/network evidence before deciding whether to retry or continue.

Continue to crawler evidence

When the scan is running, use the scan detail page until the run reaches a terminal state. If it completes cleanly, continue to [Read your first report](/docs/getting-started/read-first-report). If the run skips pages or behaves differently than expected, continue to [Crawler behavior](/docs/projects/crawler-behavior), [Browser rendering](/docs/projects/browser-rendering) or [Failure and skipped-page meanings](/docs/projects/failure-and-skipped-page-meanings) based on the state shown by the product.