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
The crawler states a real envelope — 100 to unlimited pages, 10 to 30 URLs per minute, recrawls weekly to monthly — with JavaScript crawling, severity folded into a 1-100% health score built on errors and warnings, Top 3 recommended fixes, and crawl-to-crawl comparison between two dates. We found no public information on log-file or Search Console comparison, structured-data validation, or issues weighted by traffic impact rather than count, which is what separates a diagnostic audit from a long list. 2 8