How to use it
- 1
Sign in and open a project with the intended origin.
- 2
Start the bounded crawl from the project overview.
- 3
Review fetched pages, partial failures, duplicates, and unlinked candidates in the context of the sample limit.
What the tool can do
- Collects HTTP status, title, description, and internal links from static HTML.
- Stays on one origin and applies SSRF and DNS/IP policy to navigation.
- Handles robots.txt and attempts to read one sitemap urlset for URL comparison.
Common use cases
- Collect a bounded technical sample of a small public site.
- Record the state of reachable pages before a template change.
- Use one result to review duplicates and unlinked candidates.
How it works inside
A run is bound to the session and owned project; the browser does not provide an arbitrary crawl origin.
Results are stored as a bounded, versioned DTO; individual page failures are not replaced with successful data.
Questions and answers
Is this a complete site audit?
No. The crawl is capped at 25 HTML pages and reports only the sample actually fetched.
Does the crawl see JavaScript-rendered pages?
No. It analyzes fetched HTML without executing JavaScript. Runtime pages need a separate browser tool.