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
Weekly crawls run at published per-plan page caps, with issues sorted into crawler, redirect, metadata and content categories, critical 5xx/4xx problems flagged first, expert fix guidance attached, and new issues emailed after each crawl. Total pages and issues are trended over time and a Lighthouse-based Core Web Vitals module publishes exact severity bands for mobile and desktop while stating plainly that its lab data may differ from Chrome field data. I found no public information on JavaScript rendering checks, log-file or Search Console comparison, indexation or canonical diagnosis, or structured-data validation. 4 5 2 1 4 5