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 on-site audit is documented as an automated crawl with a stated weekly page limit — the vendor's own example: a 250-page site audited weekly uses 1000 credits a month — grouping issues by type across HTML tags, content quality, performance, social tags, hreflang and links, with fix instructions for each issue. We found no public information on severity grading, Core Web Vitals, JavaScript rendering, or comparing the crawl against what search engines actually fetched. A solid mid-level issue list with limits I can hold them to; the diagnosis layer is undocumented. 2 3