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 or audit; the product is keyword, rank or backlink data only.
3 — A site audit that crawls pages and reports broken links, missing tags and redirect problems.
5 — Scheduled site audits with a stated page limit, issues grouped by category and severity with fix hints, and page speed or Core Web Vitals reported.
8 — JavaScript rendering, log-file or Search Console integration to compare what the crawler sees against what Google fetched, indexation and canonical diagnosis, structured-data validation, crawl comparison over time, 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
Rogerbot crawls weekly against per-plan page limits, groups issues into Crawler Warnings, Redirect Issues, Metadata Issues and Content Issues with 'Moz Recommends Fixing' guidance, and tags new issues found since the previous crawl with an email alert — genuine regression spotting between crawls, plus Total Pages Crawled and Total Issues trended over time. Core Web Vitals arrive as Lighthouse-style lab data simulating a mediocre mobile device, with the docs candid that this may differ significantly from CrUX field data. I found no public information on JavaScript rendering, log-file or Search Console integration, structured-data validation or crawl budget analysis (robots.txt tuning is crawl control, not budget analysis), issues are prioritised by severity rather than traffic impact, and the crawlers sit in North America with timeouts more likely on international sites. 4 5 1 4 5