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
Weekly Site Crawl with stated per-plan page limits, issues grouped into crawler, redirect, metadata and content categories, prioritised critical status-code problems and Moz Recommends Fixing guidance, plus a Lighthouse-based Core Web Vitals analysis whose good, needs-improvement and critical bands are published and whose lab-versus-CrUX explanation I can quote when numbers disagree with Search Console. New issues are tagged against the previous crawl and total issues are graphed over time, which touches regression detection. We found no public information on JavaScript rendering, log-file or Search Console integration, structured-data validation or traffic-impact prioritisation, and the vendor itself warns the crawlers are based in North America, so international sites may see more errors and timeouts — a direct accuracy concern for a German site. 4 5 4 5 1