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
Crawl scale is documented and real: up to 10 million URLs per audit in the cloud edition, a 500,000-URL desktop default raiseable to 2 million, JavaScript rendering through headless Chrome, and daily, weekly or monthly scheduling. Diagnosis runs deep — non-self-referential canonicals, robots directives consolidated across the HTML head, HTTP header and robots.txt with the specific triggering rule per URL, structured-data and hreflang reports, audit comparisons between crawls, and a Response vs Render report. We found no public information on log-file analysis or prioritisation tied to traffic impact, which is what the top of this scale asks for. 1 2 4 7 8 10