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
Crawling at genuine scale with JavaScript rendering through headless Chrome at no extra cost, scheduled daily, weekly or monthly crawls up to 10m URLs on the cloud edition, and indexation diagnosed rather than listed — non-self-referential canonicals, robots directives consolidated across HTML head, HTTP header and robots.txt with conflicts flagged, and full indexable-state categorisation. Audit Comparisons plus delta columns since the previous audit catch regressions between crawls, a Response vs Render report surfaces rendering differences, and hints carry prioritisation with built-in education. We found no public information on log-file analysis or crawl budget treatment, and the captured pages never state that prioritisation is by traffic impact rather than severity. 1 2 3 4 7 8 10