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 Data Analyst
Scheduled crawls (weekly default, configurable) with whole-domain, subdomain or directory scope, issues grouped into named categories with change deltas and fix suggestions sorted by importance, and Core Web Vitals covered from both lab (daily Lighthouse, results stored permanently and downloadable as JSON) and field data — plus JavaScript crawling on the same technology as the official Googlebot, structured-data checks, minute-level uptime monitoring and automatic detection of page changes between crawls. We found no public information on crawl budget analysis or prioritisation by traffic impact, so this sits below the top level. 3 4 2