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's core, with JavaScript rendering at a stated multi-hundred-million-URL scale, Core Web Vitals collected as lab data and broken down per page group against organic visits and bot crawl frequency, and log-file analysis of Googlebot, Bingbot and AI bots cross-referenced with crawl data — that is diagnosis weighted by traffic impact, not a link list. What holds it below the very top: we found no public information on structured-data validation, indexation or canonical diagnosis, or on regression detection between crawls with the deploying change attributable. 1 2 9