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 Content Strategist
The onpage crawl is documented to real scale — plan-stated page limits from 50,000 to 500,000 Unterseiten, a JavaScript crawler for React, Angular and Vue.js architectures, Core Web Vitals plus page speed with prioritised recommendations from YSLOW and Google Pagespeed, and an Advisor that turns findings into priorisierte To-Dos with exportable affected-URL lists. We found no public information on log-file or Search Console comparison for indexation diagnosis, structured-data validation, or crawl-to-crawl comparison, so this clears a full scheduled audit with rendering without reaching the diagnostic level a developer could work tickets from. 5 12 13 9