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
Rendering with an integrated Chromium engine, URL Inspection data showing what Google actually fetched with coverage and canonical-mismatch filters, an indexability status that states why a page is excluded, structured data validated against Schema.org, and crawl comparison including staging against production — this is diagnosis, not a checklist. Core Web Vitals are split into CrUX field data and Lighthouse lab data with per-resource opportunity filters, the level of detail a developer can work from, and crawl scale is honestly documented (5 million URLs by default, memory and disk modes). I held it just short of the top because nothing documents log-file or crawl-budget analysis tying crawl behaviour to Googlebot's actual fetches. 1 5 9 10 11 1