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
ContentIQ is documented at genuine crawl scale — hundreds to hundreds of millions of pages, recurring and ad-hoc crawls, single-page apps and JavaScript frameworks handled, severity filtering, custom XPath and regular-expression rules — well past a page-capped checklist. For the diagnostic layer, we found no public information on log-file analysis, indexation or canonical diagnosis, structured-data validation, Core Web Vitals per template, or crawl-budget analysis, and prioritisation runs on configurable rules and thresholds rather than traffic impact. Error totals tracked over time against site performance gesture at regression detection, but we found no public information tying a change to the deploy that caused it. 2 4