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; the product is keyword data only.
3 — A crawler with a low page cap that reports broken links and missing tags, with no prioritisation and no rendering of JavaScript.
5 — Scheduled crawls at a stated page limit, JavaScript rendering, issue categories with severity, and Core Web Vitals pulled per template.
8 — Log-file or Search Console integration to compare what the crawler sees against what Google fetched, indexation and canonical diagnosis, structured-data validation, 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 Site Audit scope is real and broad — crawlability and indexability, redirects, Core Web Vitals judged against Google's good, needs-improvement and poor values at the 75th percentile, canonicals, structured data and internal linking — with crawl snapshots, a stated prioritised fix list, and rendered-browser checks in the fallback path. I found no public information on log-file analysis, crawl budget work, or regression detection between crawls with deploy attribution, which is what separates a diagnostic from a very good checklist. 4 8 2