Good content on a technically broken website rarely ranks the way it should. Search engines need to crawl a page, render it correctly, and trust its structure before your writing even gets evaluated. This checklist covers the technical fixes that consistently move the needle, organized in the order most sites should actually tackle them.

1. Core Web Vitals
Google uses three Core Web Vitals metrics as ranking signals: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Mobile page experience signals have been factored into rankings since May 2021, with desktop signals added in February 2022, according to Ahrefs’ breakdown of Core Web Vitals. The current good thresholds are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less, and a CLS score of 0.1 or lower, each measured at the 75th percentile of real user visits rather than a single lab test.
INP is worth extra attention since it replaced First Input Delay as a Core Web Vital in March 2024, and it’s a stricter metric because it evaluates the worst interaction delay across an entire visit rather than just the first click. Sites that scored well on the old FID metric can still show up as needing improvement under INP, according to Cloudflare’s analysis of the INP rollout. This is a good reason to pull an updated Core Web Vitals report even if your site passed its last audit under the old metric set. For a deeper breakdown of fixing each metric individually, see our post on Core Web Vitals optimization.
Practical fixes worth prioritizing:
- Compress and serve images in WebP format, and lazy load anything below the fold
- Move to a fast host or CDN if server response time is a bottleneck for LCP
- Minify and defer non critical CSS and JavaScript
- Reserve space for images and embeds before they load to prevent CLS
- Break up long JavaScript tasks to improve INP responsiveness
2. Crawlability and indexation
A page that search engines cannot crawl or choose not to index cannot rank, regardless of content quality. Check your XML sitemap for accuracy, confirm robots.txt is not blocking sections it shouldn’t, and review Google Search Console’s Coverage report for pages marked “Crawled, currently not indexed,” which usually signals a content quality or duplication issue rather than a technical block. This step pairs directly with the on-page SEO optimization work most sites need alongside it.
3. Redirect chains and duplicate content
Redirect chains, where one URL redirects to another that redirects again, waste crawl budget and dilute link equity. Audit your redirects with a crawler and flatten any chain down to a single hop. Duplicate content, including duplicate homepage URLs (like a site being accessible at both the root domain and a “/home/” path), confuses search engines about which version to index and rank. Canonical tags need to point to one clear, consistent version of every page.
4. Schema markup
Structured data does two jobs at once. It helps traditional search engines generate rich results, and it gives AI systems a machine readable summary of your content, which increasingly matters for AI Overview and chatbot citations. FAQ schema, Article schema, and LocalBusiness schema (for multi-location businesses) are the highest priority types for most sites. Validate every implementation, since duplicate or malformed schema, like conflicting FAQPage markup on the same page, can cause more harm than having no schema at all. Our full schema markup implementation guide covers setup for each schema type step by step.
5. Mobile and page experience
Mobile-friendliness, HTTPS, and the absence of intrusive interstitials are all part of Google’s page experience signals alongside Core Web Vitals. Test every important page on an actual mobile device, not just a desktop browser resized smaller, since rendering issues frequently only appear on real mobile viewports.
6. Internal linking structure
Internal links distribute authority across a site and help both users and crawlers understand which pages matter most. A common gap is high-value service or product pages that receive few or no internal links from the rest of the site. Map out your most important pages and make sure they’re linked from relevant blog content, not just the main navigation. This is a core part of the content strategy and hub-and-spoke model we use across client sites.
7. Site speed at scale, not just on one page
A single fast page doesn’t mean a fast site. Templates matter more than individual pages, since a slow product or service page template can be replicated across hundreds of URLs. Audit Core Web Vitals at the template level using Search Console’s field data grouped by page type, not just individual URL tests in PageSpeed Insights.
Why this list matters more in 2026
Technical SEO used to be treated as a one time setup task. That’s no longer accurate. AI crawlers, including GPTBot and Google-Extended, add another layer of technical requirements on top of traditional search crawlers, and a site that’s technically sound for Googlebot isn’t automatically well set up for AI crawling and citation, particularly since AI answer engines increasingly cite earned, third party sources over brand owned pages when the structure and authority signals aren’t clearly established, according to Instant Press’s AEO and GEO statistics roundup. Marketing teams that used to treat AI SEO as optional are shifting fast: nearly 38 percent of teams report they’re already actively optimizing for AI search, even though most practitioners were still figuring out what the terms meant only a year earlier, per GoodFirms’ 2026 SEO statistics report.
Where to start if this feels overwhelming
If you’re working through this list for the first time, start with Core Web Vitals and indexation, since both directly gate whether a page can rank at all. Schema markup and internal linking come next, since they compound the value of content you’ve already published. A full technical SEO audit will surface which of these issues are actually present on your site and rank them by impact, which is usually faster than working through a generic checklist blind.
