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 audit has diagnostic instincts: scheduled crawls, an indexable/non-indexable page split, sitemap findings cross-checked against the crawl, orphan-page detection, and a JavaScript rendering toggle off by default. Severity tiers with catastrophic site-level findings first, pre-written fixes sorted by impact, and rollback push remediation toward developer-ticket quality. We found no public information on Core Web Vitals, log-file or Search Console comparison, structured-data validation, or issue-level regressions between crawls, and history is documented only as health-score movement. 1 3 4