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 Technical SEO
The Site Auditor crawls up to 30,000 pages per audit, publishes its crawler IPs and user agent, groups findings into Critical, Error and Warning with concrete pass/fail rules — time to first byte over 1.5 seconds, page load over 3 seconds — and keeps past audits you can compare against with a change indicator, which is how regressions between crawls get caught. Canonical issues and duplicate content scored 0-to-10 on a similarity measure are genuinely diagnosed, not just listed. We found no public information on JavaScript rendering, log-file analysis, structured-data validation, or issues prioritised by traffic impact rather than count. 3 4