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 Agency Owner
Scheduled automated crawls running daily, issue grouping and filtering, prioritisation of where to start, and contextual explanations of crawl findings are all documented, which takes this past a bare broken-links checker. But we found no public information on a stated page limit, JavaScript rendering, Core Web Vitals, or any Search Console or log-file comparison, so the audit reads as a prioritised list rather than a diagnosis — and 'thousands of pages' is not a number I could underwrite for a large client site. 1 2