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
Scheduled weekly crawls at stated page limits (30.000 to 4.000.000 URLs per month), JavaScript crawling, error categories with change deltas and concrete fix suggestions sorted by importance, and Core Web Vitals from both lab and field data with daily Lighthouse runs stored permanently and downloadable as JSON. I found no public information on log-file comparison against what Google fetched, indexation or canonical diagnosis, or issue weighting by traffic, so this is a strong crawl, not yet a diagnosis. 2 3 4