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 In-House SEO Lead
The crawler is documented at the scale I actually run: a default limit of five million URLs that is not a hard one, memory guidance per crawl size, and a hybrid storage engine that writes to disk. Core Web Vitals are diagnosed rather than listed — CrUX and Lighthouse data with nineteen page-speed insights, per-URL opportunity detail and filters like render-blocking requests or layout shift culprits with fix hints — and the URL Inspection integration puts Google's own coverage verdicts next to the crawl, including user-declared canonicals Google did not select, at two thousand URLs per Search Console property per day. Crawl comparison, staging-versus-production mapping, structured-data validation and issue explanations with a type and estimated priority make findings actionable; we found no public information on crawl budget analysis or on attributing a between-crawl regression to the deploy that caused it. 1 5 6 11 1