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 In-House SEO Lead
Log-file analysis at a claimed half a billion lines a day, cross-referenced with crawl data, is exactly the diagnostic core I want, and Core Web Vitals arrive as lab data aggregated per page group and prioritised by organic visits and bot crawl frequency — that converts straight into a developer ticket, with JavaScript rendering and per-URL Lighthouse audits documented. I stay below the top band because the captured pages say nothing about canonical or indexation diagnosis, structured-data validation beyond exporting the dataset, or regressions traced between crawls to the deploy that caused them, and no crawl page limit is stated. 1 2 5 9