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 Technical SEO
This is my kind of tool: a crawler with JavaScript rendering, Core Web Vitals collected as lab data per URL and per page group with Lighthouse on demand, then cross-analysed against log files and analytics so issues are weighted by organic visits and bot crawl frequency rather than counted. Log monitoring with Fresh Rank — days between first Googlebot crawl and first organic visit — is genuine crawl-budget analysis, and orphan-page and internal-linking diagnosis sits alongside it. What keeps it from the top of the scale: we found no public information on canonical or indexation diagnosis as a feature, structured data appears only as an export dataset rather than validated, and no regression detection between crawls with deploy attribution. 1 2 5 6 9