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 or audit; the product is keyword, rank or backlink data only.
3 — A site audit that crawls pages and reports broken links, missing tags and redirect problems.
5 — Scheduled site audits with a stated page limit, issues grouped by category and severity with fix hints, and page speed or Core Web Vitals reported.
8 — JavaScript rendering, log-file or Search Console integration to compare what the crawler sees against what Google fetched, indexation and canonical diagnosis, structured-data validation, crawl comparison over time, 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 Skeptic
Scheduled weekly or monthly audits with page limits stated per plan, issues grouped into eighteen categories and four severity levels with fix guidance, Core Web Vitals (LCP, FID, CLS), JavaScript rendering, indexability and canonical checks, and side-by-side crawl comparison — most of the way up this category. What holds it back: issues are ordered by severity and frequency rather than traffic impact, and we found no public information on log-file comparison or structured-data validation. The captured pages also give different figures for the maximum pages per project (150,000 versus 2,000,000). 2 3 3 2