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 or audit; the product is keyword, rank or backlink data only.
3 — A site audit that crawls pages and reports broken links, missing tags and redirect problems.
5 — Scheduled site audits with a stated page limit, issues grouped by category and severity with fix hints, and page speed or Core Web Vitals reported.
8 — JavaScript rendering, log-file or Search Console integration to compare what the crawler sees against what Google fetched, indexation and canonical diagnosis, structured-data validation, crawl comparison over time, 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
Headless Chrome rendering with a configurable render timeout sits beside a faster HTML crawler, and the Data Studio template includes a Response versus Render report, so rendering behaviour is actually surfaced. Indexation is diagnosed rather than listed — indexable versus non-indexable split, eleven indexing and serving rules reported, canonical configuration faults such as canonicals pointing at noindexed URLs, and robots directives consolidated across head, HTTP header and robots.txt with the specific rule triggered per URL. Audit comparisons and consistent crawl intervals give regression tracking between crawls, though I found no public information on log-file analysis or crawl budget analysis. 4 7 8 2 3 10