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; the product is keyword data only.
3 — A crawler with a low page cap that reports broken links and missing tags, with no prioritisation and no rendering of JavaScript.
5 — Scheduled crawls at a stated page limit, JavaScript rendering, issue categories with severity, and Core Web Vitals pulled per template.
8 — Log-file or Search Console integration to compare what the crawler sees against what Google fetched, indexation and canonical diagnosis, structured-data validation, 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 Data Analyst
The crawler is the product: unlimited URLs bounded only by the customer's own memory and storage, Chromium rendering, custom JavaScript execution, structured-data validation against Schema.org, GA/GSC/PageSpeed joins, and crawl comparison with staging-vs-production URL mapping so regressions trace to a deploy. Issues carry a type and estimated priority, but the evidence never documents crawl-budget analysis or log-file work, which is what separates this from the top anchor. 2 1