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
Weekly Rogerbot crawls run at stated per-plan page limits with issue categories and severity, new issues flagged against the previous crawl by email, fix visibility, and Core Web Vitals analysed per tracked URL on a weekly re-check with 90 days of history — that part is genuine diagnosis, though the crawler sits in North America, which the vendor itself says can impact accuracy for international sites. Prioritisation is by issue type and frequency rather than traffic impact, and I found no public information on JavaScript rendering, log files, Search Console integration, indexation or canonical diagnosis, or structured-data validation. 2 4 5