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 WebSite Auditor crawler is documented at a level I could actually brief a developer on: bulk Core Web Vitals checks combining lab and field data, factors split into Diagnostics, Opportunities and Passed audits, fix lists specific enough to name the exact images to resize and scripts to minify, and export of the affected page list. Tasks run on autopilot and crawl parameters are configurable. I found no public information on JavaScript rendering, indexation and canonical diagnosis, structured-data validation, or comparison between crawls, so this reads as a very well-specified checklist rather than a diagnostic. 1 2 3