Screaming Frog Crawl (up to 500k URLs)

Custom extraction rules capture: status codes, canonical chains, indexing directives (meta robots / X-Robots-Tag), JSON-LD blocks, internal link counts, and response times. For JavaScript-heavy sites, we run the crawl in rendering mode to compare crawled vs. rendered content.

Google Search Console Coverage Analysis

We export the full GSC Coverage report and cross-reference it with the crawl data. Discrepancies between “Crawled — currently not indexed” and “Indexed, not submitted” pages identify specific indexing failure patterns — not just a count of excluded pages.

JavaScript Rendering Audit

Chrome DevTools Timeline records JavaScript execution for key pages. We compare the rendered DOM (what a browser sees) against the HTTP response (what Googlebot sees without rendering). Any content, schema, or internal link that exists only in the rendered DOM is flagged as an indexing risk.

Core Web Vitals Diagnosis

WebPageTest provides field data (CrUX) — what real users are experiencing. Lighthouse provides lab data for controlled measurement. We diagnose each failing metric at element level: which specific image is the LCP element, which interaction is generating the INP delay, which DOM change is causing the CLS shift.

Structured Data Validation

Every JSON-LD block is run through the Schema Markup Validator. Rich Results Test confirms eligibility. We check @id consistency site-wide — a single Organization @id mismatch across pages breaks the entity co-reference chain that AI systems read for authority signals.

Priority Matrix Delivery

Findings are categorised by severity (Critical → High → Medium → Low) and implementation effort (1-day → 1-week → 1-month → infrastructure change). This is not a generic checklist — it is a sequenced implementation plan specific to your site and stack.