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 Agency Owner
The crawler runs 100 pages to unlimited with JavaScript rendering, scheduled recrawls weekly to monthly, issue categories feeding a one-to-hundred health score, canonical and hreflang checks, a compare-crawls view and a Top 3 fixes list — real mid-table substance for forty sites. We found no public information on log-file or Search Console data to check what Google actually fetched, crawl budget analysis, structured-data validation, or issues ranked by traffic impact, so remediation stays a list rather than a diagnosis. The PageSpeed key being one I supply myself is handy for staging but the guidance is not developer-ticket specific. 2 8 1