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 Data Analyst
Scheduled recrawls at weekly, biweekly or monthly cadence, JavaScript crawling, selectable user agents, staging-directory authentication and a side-by-side crawl comparison make this a real crawler, and the page range is published as 100 to unlimited. What holds it back is diagnosis: page speed arrives in coarse very-slow, slow and fair buckets or via the customer's own PageSpeed Insights key, and we found no public information on Search Console or log-file comparison, structured-data validation, or Core Web Vitals per template. Top 3 fixes are prioritised, but nothing ties that priority to traffic impact. 2 8