Crawling & technical audit
How this is scored
Site crawling at real scale: what the crawler finds, how deeply it checks, whether Core Web Vitals and indexation problems are diagnosed rather than merely listed.
0 — No site crawler or audit; the product is keyword, rank or backlink data only.
3 — A site audit that crawls pages and reports broken links, missing tags and redirect problems.
5 — Scheduled site audits with a stated page limit, issues grouped by category and severity with fix hints, and page speed or Core Web Vitals reported.
8 — JavaScript rendering, log-file or Search Console integration to compare what the crawler sees against what Google fetched, indexation and canonical diagnosis, structured-data validation, crawl comparison over time, and issues prioritised by traffic impact rather than count.
10 — The audit is diagnostic rather than a list: crawl budget analysed, rendering differences surfaced, regressions detected between crawls with the deploy that caused them inferrable, and remediation guidance specific enough for a developer ticket.
The Technical SEO
The documented crawler is configurable the way I want it: regex include/exclude and rewrite rules, robots.txt override with desktop/mobile user-agent switch, crawl speed control, HTTP-auth crawling, scheduled crawls against stated crawl credits, a JavaScript execution toggle for JS-heavy sites, and PageSpeed Insights scoring via the user's Google API key. But I found no public information on log-file or Search Console comparison, indexation or canonical diagnosis, crawl-to-crawl regression detection, or issues prioritised by traffic impact — so this is a well-configured crawler, not yet a diagnostic one. 4 2 2