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
This is the diagnostic end of the market: a crawler at 350 rendered URLs per second on Google's own rendering engine, log-file analysis with a Crawl Budget Breakdown, a Search Console funnel, and Source Gap charts that cross-reference web, sitemaps, Search Console, analytics and log files so what the crawler saw can be compared against what Google fetched. Protect pre-production tests with thresholds to halt builds plus an AI dev-ticket writer push remediation toward deploy-level attribution; the only gap I see is that a crawled-versus-rendered difference view is not described in the captured pages. 1 2 3 9