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
The On-Page API is a real crawler: JavaScript rendering through a Chromium library kept on the current Chrome version, Core Web Vitals measured as lab data with layout shift, paint and input delay returned per page, and over 60 on-page check-ups including orphan pages and render-blocking resources. What I found no public information on is the diagnostic layer I would brief a developer from — crawl-to-crawl comparison, a Search Console or log-file cross-check, and prioritisation by traffic impact rather than count. 3 4 8