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
The onpage analysis crawls up to 500.000 Unterseiten per domain at Enterprise, on definable days, reports Core Web Vitals and page speed with prioritised recommendations from YSlow and Google Pagespeed, and a JavaScript crawler handles React, Angular and Vue single-page apps — though the captured pages describe it as an unlimited beta in all paid plans. What I did not find is log-file analysis, indexation or canonical diagnosis, structured-data validation, or any crawl-to-crawl comparison that would catch regressions. The Advisor promises priorisierte To-Dos, but nothing captured says the priority is traffic impact rather than issue count. 5 12 13 9 2