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
The documented crawling is all aimed at their own link index — recrawl modes, a crawl budget dashboard with warnings when the budget is exceeded, even crawling robots.txt-blocked links — and we found no public information on any crawler auditing the customer's own site: nothing on JavaScript rendering, Core Web Vitals, indexation or canonical diagnosis, structured-data validation, or Search Console and log-file comparison. The only on-site thread is broken-backlink recovery on the link side, which is remediation for link equity, not for the site's technical health. 1 2 3