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 Agency Owner
This is the anchor-8/9 crawler evidence: unlimited URLs bound only by my own hardware, Chromium WRS rendering, scheduled and CLI-automated crawls, Search Console data fetched per URL, canonical and structured-data diagnosis, issues with type and impact-based priority, and crawl comparison including staging-versus-production so regressions can be tied to a deploy. It stops short of 10 only because nothing evidences crawl-budget analysis. 2 1