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 Content Strategist
Weekly scheduled crawls at published page limits, issue categories graded from Critical Crawler Issues down to Content Issues, Core Web Vitals with per-metric thresholds and Moz Recommends Fixing guidance put this at the scheduled-crawl level. We found no public information on JavaScript rendering, log-file or Search Console comparison, or indexation and canonical diagnosis, and issues are prioritised by type and frequency rather than by traffic impact. 4 5