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 Skeptic
The audit pages state crawl limits per plan up to 100,000 analysed pages, 300+ checked factors per page, audits schedulable daily, weekly or monthly with a selectable interval, issues tagged by severity with fix instructions, JavaScript crawling, per-URL drill-down, and error categories that include indexing and canonical link errors. I hold to the stated limits and the failed-request reporting, which are plain. We found no public information on page speed or Core Web Vitals, log-file or Search Console comparison, structured-data validation, or crawl comparison over time — so this is a well-organised, scheduled audit, not the diagnostic layer the top of the scale describes. 5 5 2 11