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
The crawler is the strongest thing here: JavaScript rendering (disabled by default), automatic duplicate detection, canonical-chain analysis and internal PageRank, robots and meta-robots indexation parameters, a structured-data testing tool among the technical features, Search Console data pulled in, and multi-domain crawling on the Pro tier. It stops short of diagnostic grade because we found no public information on Core Web Vitals, scheduled crawling, log files, or issues prioritised by the traffic a fix would recover — across forty client sites I would still be triaging by hand. 1 2 6 7