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 Agency Owner
Scheduled crawls by day, time and timezone, configurable limits (their example stops at 10,000 pages or 48 hours), a JavaScript execution toggle for JS-heavy sites, HTTP-authenticated crawling on Advanced and up, and PageSpeed Insights scoring that requires my own Google API key cover the audit basics across client sites. We found no public information on log-file or Search Console comparison, structured-data validation, or regression comparison between crawls, so the diagnostic depth stops short of developer-ticket level. 4 5 2