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
Stated page caps per tier reaching 500,000 pages, a JavaScript crawler in every paid plan, and an Advisor that returns prioritised to-dos rather than a bare error list put this solidly in the middle band. Speed data comes from Google PageSpeed and YSLOW with concrete prioritised recommendations. We found no public information on log-file or Search Console comparison, indexation or canonical diagnosis, structured-data validation, or prioritisation of issues by traffic impact, so the audit reads as thorough listing with prioritised tasks rather than a diagnostic. 2 5 9