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 recurring crawls with crawl history, live stats, crawl-to-crawl comparison and Diff Between Crawls filters, Core Web Vitals field data from the CrUX API available as filters and report columns, and log data via LogAnalyzer alongside a daily full Search Console import for crawl-versus-Google comparison. We found no public information on JavaScript rendering, a stated page cap, structured-data validation, or canonical and indexation diagnosis, so the audit stays capable rather than fully diagnostic. 2 3 6 9