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 In-House SEO Lead
The crawler runs to an unlimited page count on scheduled recrawls with JavaScript rendering, selectable user agents and staging support, and the issue set — canonicals, hreflang, orphan pages, sitemaps, status codes — is specific enough for developer tickets, with crawl-vs-crawl comparison and Top-3-fix recommendations adding diagnostic shape. We found no public information on Search Console or log-file integration, structured-data validation, or prioritisation by traffic impact, and page speed shows as slow/fair categories rather than Core Web Vitals per template. 2 8