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; the product is keyword data only.
3 — A crawler with a low page cap that reports broken links and missing tags, with no prioritisation and no rendering of JavaScript.
5 — Scheduled crawls at a stated page limit, JavaScript rendering, issue categories with severity, and Core Web Vitals pulled per template.
8 — Log-file or Search Console integration to compare what the crawler sees against what Google fetched, indexation and canonical diagnosis, structured-data validation, 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 Skeptic
This is the product's real substance: Chromium rendering, crawl comparison against staging via URL mapping, structured-data validation against Schema.org, issues typed with an estimated priority based on potential impact, and Search Console and PageSpeed data pulled into the crawl. It holds at 8, not higher, because nothing in the evidence documents log-file or crawl-budget analysis, and the URL limit is 'unlimited, dependent on allocated memory and storage' — stated, which I respect, but not an analysed budget. 1 1 2