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 Skeptic
The documentation is deep and specific where I can hold it: JavaScript rendering via integrated Chromium, Core Web Vitals from the CrUX report and Lighthouse with the pass levels stated, and indexation diagnosis against what Google actually fetched via the URL Inspection API, including an 'Indexable URL Not Indexed' filter and a coverage column. Limits come in numbers — a default five million URL crawl limit described as not hard, memory recommendations per crawl size, and the 2,000 URLs per property per day Google quota disclosed. Crawl comparison of staging against production plus issues carrying a type and estimated priority based on potential impact puts this above the level of a findings list. 5 6 9 11 1