Codalyst Tech
SEO & Marketing11 min read

Technical SEO Checklist 2026: 18 Fixes That Move Rankings

Great content cannot rank if search engines cannot find, crawl, and index it. This 18-point technical SEO checklist covers Core Web Vitals, crawlability, structured data, and performance fixes that move rankings in 2026.

Publishing great content is necessary but not sufficient for ranking in 2026. Search engines need to be able to find, crawl, understand, and index your content before any of your writing work pays off. Technical SEO is the infrastructure layer that determines whether your content reaches its audience or sits undiscovered. If you want a specialist to run this audit for you, our SEO service covers technical audits alongside on-page and content work.

This checklist covers the 18 most impactful technical SEO fixes, ranked by the combination of implementation difficulty and ranking impact. Work through them in order and you will eliminate the most common technical issues that suppress rankings.

What technical SEO covers and what it does not

Technical SEO addresses the server, code, and site architecture layer of search optimisation. It is distinct from:

  • On-page SEO: keyword targeting, heading structure, internal linking, and content quality
  • Off-page SEO: backlinks, brand mentions, and domain authority
  • Content SEO: topic strategy, search intent matching, and editorial quality — covered in our B2B content marketing guide and SEO for small business playbook

Technical SEO ensures that the work you do in the other three areas is actually visible to Google. A site with perfect content and no backlinks but excellent technical SEO will rank better than one with perfect content and great backlinks but fundamental crawl and indexation issues.

Core Web Vitals: the foundation in 2026

Google's Core Web Vitals remain a confirmed ranking signal in 2026. The three metrics measure real-world user experience: how fast pages load, how quickly they become interactive, and how visually stable they are during load.

Fix 1: Improve Largest Contentful Paint (LCP)

LCP measures how long it takes for the largest visible content element (usually a hero image or above-the-fold heading) to render. The target is under 2.5 seconds.

Common LCP fixes:

  • Serve images in WebP or AVIF format rather than JPEG or PNG
  • Preload the LCP image with a <link rel="preload"> tag in the <head>
  • Use a CDN to serve assets from edge locations close to the user
  • Defer non-critical JavaScript to prevent render-blocking
  • Move to a faster hosting environment if your server response time (TTFB) exceeds 800ms

Fix 2: Improve Interaction to Next Paint (INP)

INP replaced First Input Delay (FID) as a Core Web Vital in 2024. It measures the responsiveness of a page to all user interactions, not just the first one. The target is under 200ms.

Common INP fixes:

  • Reduce main thread blocking time by breaking up long JavaScript tasks
  • Defer or remove unused third-party scripts (chat widgets, tracking pixels, A/B testing tools)
  • Use a service worker to pre-cache interactive elements
  • Avoid synchronous network calls in response to user interactions

Fix 3: Eliminate Cumulative Layout Shift (CLS)

CLS measures how much page content moves unexpectedly during load. The target is under 0.1.

Common CLS fixes:

  • Set explicit width and height attributes on all images and video elements
  • Reserve space for ads, embeds, and dynamically inserted content with CSS aspect-ratio or fixed dimensions
  • Avoid injecting content above existing content after page load
  • Use font-display: swap carefully and preload web fonts to reduce flash of unstyled text

Crawlability fixes

Fix 4: Audit and clean your robots.txt

Robots.txt tells search engine crawlers which pages to skip. Errors here can accidentally block crawling of your entire site.

  • Ensure your robots.txt does not disallow crawling of CSS, JavaScript, or image files
  • Check that important page paths are not blocked
  • Verify the file is accessible at yourdomain.com/robots.txt and returns a 200 status code
  • Reference your sitemap URL in the robots.txt file

Fix 5: Submit a complete XML sitemap

Your sitemap tells Google which pages to index. Audit it to ensure:

  • All important pages are included
  • No pages with noindex tags are listed
  • No redirect or error pages are included
  • Lastmod dates are accurate and updated when content changes
  • Image sitemaps are included for image-heavy sites

Submit the sitemap in Google Search Console under Sitemaps. Monitor for processing errors.

Fix 6: Fix crawl errors in Google Search Console

Check the Coverage report in Google Search Console monthly. Fix:

  • Pages returning 404 (not found): redirect to the correct URL or restore the page
  • Pages returning 5xx (server errors): investigate server configuration or application errors
  • Pages blocked by robots.txt that should be indexed
  • Pages with noindex tags that should be indexed

Each crawl error is a page that cannot rank. Fix them systematically.

Fix 7: Audit your internal linking structure

Internal links pass authority through your site and tell Google which pages are most important. Check:

  • Every important page is reachable within three clicks from the homepage
  • Orphaned pages (pages with no internal links pointing to them) are either removed or linked to
  • Anchor text for internal links is descriptive and keyword-relevant, not just "click here" or "read more"
  • No important pages are buried in pagination or accessible only through search functionality

Indexation fixes

Fix 8: Consolidate duplicate content with canonical tags

If multiple URLs serve similar or identical content, search engines split ranking signals between them. This happens with:

  • URL parameters (filter, sort, session IDs): ?colour=red, ?sort=price
  • Protocol variations: http:// vs https://
  • WWW vs non-WWW: www.example.com vs example.com
  • Trailing slash variations: /page/ vs /page

Fix with <link rel="canonical"> tags pointing to your preferred URL, and with 301 redirects for permanent consolidations. Set a preferred domain in Google Search Console.

Fix 9: Implement HTTPS sitewide

HTTPS is a confirmed ranking signal and a prerequisite for most modern browser features. Check:

  • All pages serve over HTTPS with a valid SSL certificate
  • HTTP URLs 301 redirect to HTTPS equivalents
  • Your SSL certificate is not expiring within 30 days (set up auto-renewal)
  • No mixed content warnings (HTTP resources loaded on HTTPS pages)

Fix 10: Fix redirect chains

Each redirect in a chain loses some link equity and slows page load. A chain like A → B → C → D should become A → D. Audit your redirects with Screaming Frog or Ahrefs Site Audit and collapse chains to single hops.

Structured data

Fix 11: Add schema markup for your primary content types

Structured data (schema.org markup in JSON-LD format) helps Google understand what your content is about and can generate rich results in search: star ratings, FAQ dropdowns, event dates, product prices, and more.

Priority schema types for most businesses:

  • Organization: name, logo, contact details, social profiles
  • LocalBusiness: for businesses with physical locations (enables map pack eligibility)
  • Article or BlogPosting: for blog content (enables article rich results)
  • FAQPage: for FAQ sections (enables expanded FAQ snippets in search results)
  • Product: for e-commerce pages (enables price and rating rich results)
  • BreadcrumbList: for navigational breadcrumbs (improves result appearance)

Validate your markup with Google's Rich Results Test tool and the Schema.org validator.

Fix 12: Fix structured data errors in Search Console

Google Search Console's Enhancements section reports structured data errors and warnings. Fix:

  • Missing required fields (most commonly name, url, image, or datePublished)
  • Invalid property values
  • Markup that exists on the page but was not parsed correctly

Page speed and performance

Fix 13: Eliminate render-blocking resources

JavaScript and CSS files loaded in the <head> block the browser from rendering the page until they are downloaded and parsed. Fix:

  • Add defer or async attributes to non-critical JavaScript
  • Move non-critical CSS to load after the main render path
  • Inline critical CSS (the styles needed for above-the-fold content) directly in the <head>

Fix 14: Optimise and lazy-load images

Images are the largest contributor to page weight and slow LCP on most sites.

  • Compress all images before upload using Squoosh, ImageOptim, or a similar tool
  • Use next-generation formats: WebP for photographs, SVG for graphics and icons
  • Add loading="lazy" to images below the fold
  • Use responsive images with srcset to serve appropriate sizes on different screen widths
  • Use a CDN with image transformation capabilities (Cloudflare Images, Imgix, or similar)

Fix 15: Enable browser caching and compression

  • Enable gzip or Brotli compression on your server (reduces HTML, CSS, and JavaScript file sizes by 60 to 90 percent)
  • Set cache-control headers so returning visitors load assets from their local cache instead of re-downloading them
  • Cache static assets (images, fonts, CSS, JS) for at least 30 days

Mobile and accessibility

Fix 16: Confirm mobile-first indexing compliance

Google indexes the mobile version of your site first. Ensure:

  • All content visible on desktop is also visible on mobile (not hidden behind tabs or accordions)
  • Mobile viewport is set with <meta name="viewport" content="width=device-width, initial-scale=1">
  • Text is legible without zooming (minimum 16px font size)
  • Tap targets (buttons, links) are at least 48px in height and width
  • There is no horizontal scroll on mobile screens

Fix 17: Fix broken links

Broken internal and external links waste crawl budget, frustrate users, and signal site neglect to search engines. Run a broken link audit monthly using Screaming Frog, Ahrefs, or Google Search Console's Coverage report. Fix or remove every broken link.

International and advanced fixes

Fix 18: Implement hreflang for multilingual sites

If your site serves content in multiple languages or for multiple regions, hreflang tags tell Google which version to serve to which user. Incorrect hreflang implementation is one of the most common advanced SEO errors.

  • Add <link rel="alternate" hreflang="xx"> tags to all language variants of each page
  • Include a self-referencing hreflang tag
  • Include an x-default fallback
  • Ensure all hreflang URLs are canonical and return 200 status codes

For sites not yet operating internationally, set a reminder to implement hreflang before you launch a second language version.

How to run a technical SEO audit

Use these tools to systematically identify issues before working through the checklist (or engage an SEO specialist to run the audit for you):

  • Google Search Console: Coverage, Core Web Vitals, Enhancements, and URL Inspection reports (free)
  • Google PageSpeed Insights: Page-level Core Web Vitals and performance recommendations (free)
  • Screaming Frog SEO Spider: Full site crawl for broken links, redirect chains, duplicate content, missing tags (free up to 500 URLs, paid for larger sites)
  • Ahrefs Site Audit or Semrush Site Audit: Automated issue detection with severity prioritisation (paid)
  • Chrome DevTools: Lighthouse performance audits and network request analysis (free)

Run a full audit quarterly. Treat the output as a prioritised bug list, not a report.

Technical SEO is the unsexy work that makes the rest of your SEO effort pay off. None of these fixes are glamorous. All of them compound. A site that ranks at position 7 because of technical issues it has not addressed will be overtaken by a technically clean competitor with equivalent content every time. Once your technical foundation is clean, layer on a B2B content marketing strategy to build authority, and use Google Analytics 4 to measure whether rankings are translating into traffic and leads. Our SEO service handles all three layers if you want to delegate the work.

Fix the foundation. Then build on it.

Back to all articles