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 Agency Owner
The On-Page API is a real crawler with JavaScript rendering built on Chromium, which they describe as a close imitation of Google, and Core Web Vitals come back as lab data alongside more than sixty checks including orphan pages, render-blocking resources and readability, with an on-page score per page. What I did not find is the layer I would actually bill against: no scheduled audits, no severity grouping with fix hints, and nothing on log files, Search Console comparison, canonical diagnosis or crawl-over-time comparison. I run forty sites on this kind of data, and the raw inspection is there but the diagnostic half is not documented. 1 3 4