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
Scheduled crawls at published page limits from 1,000 to 100,000 pages, JavaScript crawling on the paid plans, 300+ factors per page, issue categories tagged by severity with fix instructions per URL — that is a real audit, not a broken-link checker. What would make it diagnostic rather than a list is absent from the captured pages: no Core Web Vitals per template, no log-file or Search Console comparison against what Google actually fetched, no structured-data validation, no crawl-budget analysis, and no regression detection between crawls; prioritisation is by severity tag, never by traffic impact. 5 2