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 runs at stated scale — 50.000 to 500.000 pages per domain with paid add-ons up to half a million, plus a JavaScript crawler for SPAs in an unlimited beta across all paid plans — and the issue set covers status codes, duplicate content, click depth, image checks and pagespeed from YSLOW and Google Pagespeed, exportable per affected URL, with the Advisor handing out prioritised to-dos. What I can't see is the diagnosis layer: we found no public information on log-file analysis, crawl budget, canonical or indexation diagnosis, structured-data validation, or regressions compared between crawls. 5 2 9