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
This is a crawler with real teeth: Chromium rendering for JavaScript-heavy sites, Search Console URL Inspection with a coverage column explaining why a URL is not on Google despite being indexable, structured-data validation against Schema.org, crawl comparison including staging against production, and issues tagged with a type and estimated priority based on potential impact. Core Web Vitals come through the PageSpeed Insights API with per-URL Lighthouse opportunities concrete enough for a developer ticket — fetchpriority hints, unused JavaScript, render-blocking requests — and the only thing I found no public information on is crawl-budget analysis as a named capability. 5 6 9 11 1