Review project pages

Before you start

Project Pages is the current review step between project creation and the first scan. Use it after the project exists and discovery has run. Domain ownership and Billing may still block a private scan, but page review stays on the project screen. The goal is simple: confirm WebRiskOps found the public pages you expect, then continue to the project action that starts the scan. Do not add private, admin, login-only or unrelated-domain targets to the first run.

Review project pages

Follow the path `Projects → Project detail → Project Pages → Actions`.

1. Open `/projects` and choose the project. Result: the project detail page shows the domain, verification state, Project Pages and Actions.
2. In Project Pages, read the discovery summary. Result: you know how many public pages and scan groups are ready.
3. Check the listed URLs. Result: checkout, pricing, cart, contact or other intended public pages are visible before the scan.
4. If the expected page is missing, click Discover pages before starting the scan. Result: discovery refreshes from the same project domain.
5. Keep unrelated hosts, private paths and admin areas out of the first run. Result: the scan remains inside the safe public-page boundary.
6. Continue to Actions when the page list looks right. Result: Run whole scan becomes the next scan entry point when account and domain blockers are clear.

Continue to the first scan

When Project Pages looks correct, continue to [Run the first scan](/docs/getting-started/run-first-live-audit). The next page explains how to start the scan and read the scan result state.

Blocked states

• Discovery empty means WebRiskOps did not find candidate public pages. Refresh discovery or confirm the domain is reachable.
• Project setup comes first means setup choices still need to be saved before the first scan path can move forward.
• Credits required means Billing needs available credits or an active plan before a private scan can run.
• Unsupported target means the project is outside the self-service public-page boundary. Use a supported public website or split the work into a different project.