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 Content Strategist
The audit story is content-first rather than technical: the tool scans a domain and audits only indexed pages that already earn traffic — up to 100 pages automatically, selectable to 500, drawn from the top 20,000 ranking pages — through a Google Search Console connection. That traffic-led prioritisation is the right instinct, but the captured pages show no broken-link, redirect or tag reporting, no severity grouping, no scheduling, and no Core Web Vitals, so the diagnostic depth a technical audit is bought for remains undocumented. 3 4 1