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 Technical SEO
Log files are a first-class product here, not a bolt-on: crawl budget broken down across primary pages with and without bot hits, bot trend charts over time, and a Source Gap view of what the crawler found versus sitemaps, Search Console, analytics and log files — that is crawler-versus-Google comparison, not a link count. Rendering runs on Google's own engine at a stated 350 rendered URLs per second, Search Console and analytics funnel reports prioritise by actual clicks and visits, and pre-production QA that can halt a build plus an AI dev ticket writer close the loop from regression to developer ticket. The only gaps against the top of the scale: nothing evidences rendered-versus-raw differences surfaced as such, and structured data appears as a chart category rather than documented validation. 1 2 3 9