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 documentation is unambiguous on scale and depth: a breadth-first crawl in Googlebot fashion, JavaScript rendering via integrated Chromium, structured data validated against Schema.org and rich result features, Core Web Vitals from CrUX and Lighthouse down to per-URL opportunity detail, crawl comparison including staging against production, and Google's own indexation verdicts pulled in through the URL Inspection integration, with each issue carrying a type and an estimated priority. My only pause before the top mark: we found no public information on crawl budget analysis or on attributing a regression between crawls to the deploy that caused it. 1 5 11 6