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 crawler genuinely renders — Chromium-based, described as a close imitation of Google — and Core Web Vitals come back as lab data from a simulated page load with LCP, FID and CLS as named fields, alongside 60-plus checks including orphan pages and render-blocking resources, all retrievable through free filters. What I see is a findings list delivered over an API rather than a diagnosis: we found no public information on log-file or Search Console comparison, crawl-over-time regression detection, or issues prioritised by traffic impact. 3 4