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 In-House SEO Lead
The audit modules go deep — crawlability and indexability, redirects, canonicals, structured data, Core Web Vitals measured against Google's published good and poor values at the 75th percentile, mobile rendering parity, even AI-crawler access — and the Enterprise tier promises multi-million-page crawling, which matters at my scale. But we found no public information on crawl page limits per plan, scheduled crawl cadence, log-file analysis or prioritisation by traffic impact, and nothing that turns findings into a diagnosis with regression tracking between crawls. 2 4 8