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
Site Audit is documented as a genuinely configurable crawler — day, time and timezone scheduling, JavaScript execution behind a toggle, custom URL list uploads, regex include/exclude, ignore-robots control and HTTP-authenticated crawling — with PageSpeed scores flagged when low, though the user must supply their own Google API key. We found no public information on log-file or Search Console comparison against what Google fetched, structured-data validation, or issue prioritisation by traffic impact, so the evidence describes a well-configured crawler rather than a diagnosis. 4 12