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 In-House SEO Lead
The crawler is documented in real depth — scheduled audits by day, time and timezone, per-plan crawl credits, a JavaScript execution toggle, PageSpeed Insights scoring with the user's own Google API key, regex include/exclude, and sitemap or custom URL-list seed sources — which sits comfortably above a plain broken-link checker. But I found no public information on issues grouped by severity with fix hints, indexation or canonical diagnosis, structured-data validation, Search Console or log-file comparison, or crawl-to-crawl regression tracking, so nothing evidences findings specific enough to hand a developer as a ticket. 4 12 5 2