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 Technical SEO
The pitch is continuous monitoring rather than scheduled audits: technical issues surface the moment they appear, alerts fire the moment something changes and route by person and sensitivity level, and every issue is ranked by business impact rather than by count — the prioritisation I actually want. Sixty months of history with every snapshot preserved gives change-tracking over time, but the captured page gives no information on JavaScript rendering, log-file or Search Console comparison, indexation and canonical diagnosis, structured data validation or crawl budget analysis, so I cannot call it diagnostic at depth. 1