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 In-House SEO Lead
Crawls run weekly by default at stated quotas up to 4 million URLs per month, JavaScript rendering is described as based on the same technology as the official Googlebot, error categories from missing meta descriptions to broken links come with fix suggestions sorted by importance, and Core Web Vitals are available as both lab and field data with daily Lighthouse measurements kept permanently. We found no public information on log-file analysis, canonical or indexation diagnosis, or issue prioritisation weighted by traffic impact, and structured data appears only as a missing-tag check — so the audit is closer to a prioritised list than a diagnosis. 2 3 4