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
A dedicated crawler with scheduled crawls, user-set limits, regex scoping and a JavaScript execution toggle is documented, and the crawl-credit mechanics are stated down to which HTTP status consumes them — limits I can hold a vendor to. What the captured pages don't show is issue categories with severity prioritisation, Core Web Vitals per template, or any log-file and Search Console comparison; the speed check runs through PageSpeed Insights only if you supply your own Google API key. 4 12 9