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 Content Strategist
This is the product's centre of gravity and it shows: 300+ hints checked and prioritised with built-in education, JavaScript rendering via headless Chrome, scheduled daily-to-monthly crawls at up to 500,000 URLs on desktop and ten million in the cloud, and Search Console integration that layers real Google performance data into the audit. Canonical diagnosis, robots directives checked across the head, HTTP header and robots.txt for conflicts, an Indexability report with granular indexing rules, and structured-data and hreflang reports push it past the middle of the scale, with audit comparisons and a 'Response vs Render' view edging toward genuinely diagnostic territory. We found no public information on crawl-budget analysis or on tying regressions between crawls to the deploy that caused them. 1 2 3 4 6 7 8 10