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
Weekly Rogerbot crawls with per-plan page limits, issues grouped into crawler, redirect, metadata and content categories with critical 5xx/4xx errors prioritised and expert fix guidance, plus full Core Web Vitals reporting with Lighthouse-backed page scores — that is a proper scheduled audit. Trend graphs over time, new-issue flagging between crawls and on-demand recrawls to validate fixes nudge it a notch higher. We found no public information on JavaScript rendering, log-file or Search Console comparison, indexation or canonical diagnosis or structured-data validation, and the help pages themselves warn the crawlers run from North America, with more errors and timeouts possible on international sites — which is most of my book. 4 5 4 1 2