Run a site crawl and follow its progress

Choose a profile, understand the live stages, and know when a long run is still healthy.

Open this area in the app ↗
01

Pick a profile that matches the question

Standard is the normal baseline. Fast works for a small release check. Deep explores more click levels at a gentler pace. The launcher also controls the URL limit, concurrency, sitemap seed, subdomains, and query cleanup.

02

Watch the stages

Discovery and crawling increase the fetched and queued counters. Persistence writes the collected evidence as a consistent snapshot. Large sites can remain in persistence for several minutes even when the visible fetch count stops moving. The run will either complete or expose a failure state.

03

Read the crawl log before the reports

The crawl log records duration, response code distribution, and whether the URL allowance stopped discovery. This prevents a partial site sample from being mistaken for full coverage.

04

Respect ownership and crawl policy

Regular audits follow robots.txt. Verified ownership can unlock the deliberate control needed for an owner-authorized test that ignores robots rules. Major platforms and other unsafe crawl targets cannot be added as projects.

Apply the guideReturn to the evidence and complete one verifiable action.
Open the app ↗
Did this guide solve the task?No account or workspace data is recorded here.