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
The crawler mechanics are well documented: 100 to 30,000 pages per audit, published user agent and IP ranges, a five-second crawl delay, robots.txt handling, and over 50 issues grouped into critical, error and warning severities with load-time and first-byte tests, canonical and noindex detection, and audit history with change comparison between runs. We found no public information on JavaScript rendering, log-file analysis or structured-data validation, so this reads as a well-documented issue list rather than a diagnostic that compares against what Google fetched. 3 4