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 Skeptic
Crawls run on a stated schedule (weekly by default, configurable down to manual or four-weekly) against a published URL budget per package, with JavaScript crawling on the same technology as the Googlebot, Core Web Vitals from both lab and field data, daily Lighthouse runs stored permanently with JSON download, and error categories carrying fix suggestions sorted by importance plus change monitoring between crawls. We found no public information on log-file analysis, indexation or canonical diagnosis, or prioritisation by traffic impact, so this is a strong scheduled audit rather than a full diagnostic one. 2 3 4