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
A real crawler with 100 to 30,000 pages per audit, issues grouped Critical, Error and Warning across 50-plus checks, speed tests like time to first byte past 1.5 seconds and load time past 3 seconds, plus audit history and a compare view showing change between two audits. Canonical and noindex handling is diagnosed rather than merely listed. We found no public information on JavaScript rendering, structured-data validation, or prioritising issues by traffic impact, which holds it short of the diagnostic depth a developer ticket needs. 3 4 5