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 Agency Owner
Scheduled crawls, a JavaScript rendering toggle, indexable/non-indexable page splits, sitemap validation and orphan-page detection put this well past a link checker, and pre-written fixes sorted by impact with one-click rollback are exactly what my team forwards to clients. But the default crawl is 100 pages with the ceiling unstated, and we found no public information on Core Web Vitals, log files, or Search Console comparison, which caps how diagnostic this can be for large sites. 1 3 4