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 crawler runs on a schedule (weekly by default, configurable down to four-weekly or manual), crawls whole domains with subdomains at documented volumes of 30,000 to 4,000,000 URLs per month depending on package, and its JavaScript crawling is stated to use the same technology as the official Googlebot. Error counts carry change deltas between crawls, relevant page changes are automatically detected and displayed, and Core Web Vitals are covered with both lab and field data, daily permanently stored Lighthouse measurements and a raw JSON download. We found no public information on log-file analysis, crawl budget analysis, or indexation and canonical diagnosis, which keeps this short of a fully diagnostic audit. 2 3 4