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 Technical SEO
The captured audit material runs well past a checklist: crawlability and indexability, canonicals, structured data, mobile parity and rendering, AI crawler access, Core Web Vitals judged against Google's good/needs-improvement/poor bands at the 75th percentile, a snapshot-based workflow across crawls, and multi-million-page crawling at the enterprise tier. It stops short of genuine diagnosis: we found no public information on log-file analysis, crawl budget analysis, or prioritisation by traffic impact rather than count — the only phrasing captured is a prioritized fix list — and regression detection between crawls is likewise undocumented. 2 4 8