Audit discoverability before chasing scores
Technical SEO helps a search engine access and interpret the pages you intend to publish. This article and its guidance were reviewed in October 2026. Sample the homepage, a service page, an article, a product and an intentionally missing URL. Record status, indexability, canonical and rendered content. A high performance score cannot compensate for an accidentally excluded page. Start with the pages that support valuable customer tasks rather than the easiest warnings to clear.
Measure the current Core Web Vitals
The metrics cover loading through Largest Contentful Paint, responsiveness through Interaction to Next Paint, and stability through Cumulative Layout Shift. Good thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, evaluated at the 75th percentile. Distinguish field measurements from a laboratory run. Lab testing helps reproduce a bottleneck; field data reflects actual visitors. If field data is insufficient, say so instead of presenting a lab score as a field pass.
Turn each metric into a repair
Identify the LCP element before compressing every asset. A large hero image, slow server and script-dependent heading need different interventions. Inspect long main-thread tasks for responsiveness and reserve image or banner dimensions for layout stability. Example investigation: an image discovered only after a component executes may benefit more from earlier discovery than a small reduction in bytes. Change the underlying cause, repeat the same conditions and check functionality. Keep the baseline so a claim of improvement can be reproduced.
Review crawling and index signals
Compare valuable URLs with internal navigation and the sitemap. Avoid redirect chains and unrelated destinations. An intentional 404 should not look like a successful content page. Robots.txt controls crawling; a crawler needs access to read noindex. Review exclusions individually instead of blocking all parameters or low-traffic pages. Inspect the rendered text and metadata when the initial HTML is only a shell. Document deliberate exclusions so a future audit can distinguish an intentional decision from an accidental publishing error.
Validate markup and mobile tasks
Structured data should describe visible content. Correct markup establishes eligibility, not guaranteed display. Google's 2026 documentation updates say FAQ rich results are no longer shown, so FAQ markup is not a shortcut to expanded results. On mobile, complete important tasks: navigation, reading, form submission and overlay dismissal. Use browser tools and Lighthouse diagnostics; the retired Google Mobile-Friendly Test is not a current testing step. Check that the keyboard does not hide critical form controls and that error messages explain how to recover.
Prioritize and verify releases
Rank fixes by business value, affected URLs, confidence and effort. A broken product canonical can matter more than a minor score difference on an unimportant page. After release, verify statuses, redirects, headings, forms and analytics. Annotate the deployment and monitor technical reports and business outcomes. Passing Core Web Vitals does not guarantee a ranking. Keep unresolved limitations documented, and repeat the checks when a template or major dependency changes rather than assuming one successful audit protects every future release.
Put this guidance into practice
For help applying these steps, review our seo service scope. For another perspective, read SEO Planning: A Practical Guide to Improving Search Visibility.
Sources and further reading
Guidance reviewed: October 29, 2026. Official references support the platform facts discussed above; worked examples and proposed tests are illustrative, not reported client results.