Rendering is the whole game
A static fetch sees the HTML shell of a client-rendered application: nav links that exist only after hydration, routes that never appear in markup, and menus built by a router. Crawl that and you conclude a site is a fraction the size it is.
SiteDirective drives a full JavaScript engine, so it sees what a browser sees — including content injected after load — and records the status code and payload that a real visitor would. Depth control (1 to 10 levels) and include/exclude URL patterns keep large sites tractable without giving up rendering.
Throttling is courtesy, and it is configurable
A crawler without a throttle is a denial-of-service test on your own staging box. Request throttling, depth limits and pattern filters exist so a crawl is sized to what the server can take, and so the results describe your site rather than the artefacts of a hammered environment.
This is also the right way to treat robots.txt: read it, respect it, and use the built-in architect to author rules you have actually tested before you deploy them.
Four sitemap formats, chosen on purpose
XML is what search engines consume, so it is the default export. HTML sitemaps serve people and give crawlers a link graph that does not depend on a file path. JSON suits programmatic pipelines and static-site generators; TXT is the quick inventory for a review or a handover.
Because they come from the same crawl, the four cannot drift out of sync with each other — the failure mode of hand-maintained sitemap files. That single-source behaviour is most of the value of the tool.
The audit is a checklist you can prove
Broken-link detection covers internal and external 404s; the metadata audit flags missing or duplicate titles and descriptions, absent H1s and canonical mismatches; performance flagging identifies heavy pages by response time and payload.
These are the same checks we run against this site before a release. An offline crawler is not a Search Console replacement — it has no idea what a search engine decided to index — but it is the cheapest way to catch a broken template, a missing canonical or an orphaned route before anybody else does.
Where crawl data goes: nowhere
Crawled URLs, response bodies, audit findings and exports stay on the machine that ran the crawl. There is no vendor cloud receiving your pre-launch site, your staging credentials or your client's structure.
For agencies, that is a contractual point as much as a privacy one: the crawl of a client's unreleased site is confidential data, and a hosted SEO platform stores it somewhere you did not choose.