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 Content Strategist
Site Auditor crawls up to 30,000 pages per audit, checks over 50 issues grouped into critical, error and warning severities with stated pass conditions (three-second page load, 1.5-second first byte, duplicate content scored by a similarity algorithm), diagnoses canonical problems, and keeps audit history with a change comparison between two runs. We found no public information on JavaScript rendering, structured-data validation, or prioritising issues by the traffic a page actually earns, which is what separates a diagnostic audit from a very thorough checklist. 3 4