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
Log-file crawl-budget breakdowns, Source Gap charts lining the crawl up against sitemaps, Search Console, analytics and log files, JavaScript rendering on Google's own engine, and Core Web Vitals from both Lighthouse lab data and CrUX field data — plus an AI dev-ticket writer that turns findings into assignable work. It sits just under the top mark because I found no public information on regression comparison between crawls tied to a specific deploy; pre-production QA and CI/CD triggers get close but do not evidence deploy-level attribution. 1 2 3 9