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
Scheduled crawling is documented at real scale (30,000 to 4,000,000 URLs a month by tier), JavaScript rendering described as built on the same technology as the official Googlebot, error categories sorted by importance with concrete fix suggestions, and Core Web Vitals handled properly with lab and field data, daily Lighthouse measurements stored permanently and downloadable as JSON. We found no public information on log-file analysis, crawl-budget analysis, canonical or indexation diagnosis, or issues ranked by traffic impact, so this reads as a strong scanner rather than a full diagnostic. 2 3 4