Technical SEO Checklist 2026: 18 Fixes That Move Rankings

Content cannot rank if search engines cannot find, crawl, and understand it. Technical SEO is the foundation layer that determines whether your pages even get considered for rankings. In 2026, with Core Web Vitals as a confirmed ranking signal, structured data enabling rich results, and Google's crawl budget increasingly selective on larger sites, the technical gap between optimised and unoptimised sites is wider than it has ever been.

This 18-point checklist covers every technical area that influences rankings, ordered by impact.

Crawling and Indexing (Fix These First)

1. Verify your pages are indexed. Open Google Search Console and navigate to Indexing > Pages. You will see how many pages are indexed and how many are excluded, and why. "Discovered but not indexed" and "Crawled but not indexed" are the most common issues. A page Google will not index will not rank, regardless of content quality.

2. Check your robots.txt for crawl blocks. Your robots.txt file tells search engine crawlers what they can and cannot access. A single misconfigured Disallow directive can block Google from crawling entire sections of your site. Check it at yourdomain.com/robots.txt and confirm you are not blocking any pages you want indexed.

3. Fix broken internal links. Broken links waste crawl budget and signal poor maintenance. Use Screaming Frog SEO Spider (free up to 500 URLs) to crawl your site and identify 404 responses within your internal link structure. Redirect broken links to the correct destination or remove them.

4. Eliminate redirect chains. A redirect chain occurs when URL A redirects to URL B which redirects to URL C. Each hop loses PageRank and adds latency. Identify chains using Screaming Frog and condense them to a single redirect from the original URL directly to the final destination.

5. Set canonical tags correctly. Canonical tags tell Google which version of a URL is the authoritative one when multiple URLs serve similar content (for example, with and without trailing slashes, with and without UTM parameters). Missing or self-referencing canonicals cause duplicate content issues that split ranking signals across page versions.

6. Submit and maintain your XML sitemap. An XML sitemap lists every page you want indexed, with its last modification date. Submit yours in Google Search Console > Sitemaps. Include only canonically indexable pages. Remove pages that return 404, redirect, or are blocked by noindex.

Core Web Vitals (Confirmed Ranking Signal)

7. Achieve Good LCP (Largest Contentful Paint). LCP measures how quickly the main content element loads. The target is under 2.5 seconds. The most common causes of LCP failure are unoptimised images (serve WebP, add explicit width and height attributes, preload the LCP image), render-blocking JavaScript in the document head, and slow server response times (Time to First Byte above 600ms).

8. Pass INP (Interaction to Next Paint). INP replaced First Input Delay in 2024 and measures overall page responsiveness across all interactions during a visit. The target is under 200 milliseconds. Long JavaScript tasks and heavy third-party scripts are the primary causes of INP failure. Measure INP using the Chrome User Experience Report or the INP field data in Search Console.

9. Minimise CLS (Cumulative Layout Shift). CLS measures visual stability: how much page elements shift after the initial load. The target is under 0.1. Common causes: images without explicit size attributes (add width and height to every image element), ads injected after load, and web fonts that swap after the page renders. FOUT (Flash of Unstyled Text) from font swapping is often the cause of unexpected CLS failures on otherwise well-optimised pages.

Check your Core Web Vitals in Search Console > Experience > Core Web Vitals and in Google PageSpeed Insights. Use field data (real-world measurements from the Chrome User Experience Report) rather than lab data for ranking context, since Google uses field data for ranking signals.

HTTPS and Security

10. Enforce HTTPS site-wide. HTTPS is both a confirmed ranking signal and a baseline trust signal for visitors. If any pages on your domain still serve over HTTP, implement a redirect from HTTP to HTTPS and ensure your SSL certificate is current. Check for mixed content warnings (HTTPS page loading HTTP resources) using Chrome DevTools > Security tab.

Site Performance

11. Improve Time to First Byte (TTFB). TTFB is the time from a browser sending a request to receiving the first byte of a response. Target under 600ms. The main levers are: server-side caching (for WordPress, WP Rocket or Nitropack; for custom applications, Redis or page-level caching), a content delivery network (CDN) to serve static assets from edge locations, and database query optimisation for pages that are dynamically generated.

12. Compress and convert images to WebP. Images are typically the largest payload on any web page. Serve images in WebP format (25 to 34 percent smaller than equivalent JPEG at the same quality), compress before uploading, and use lazy loading for images below the fold. Tools: Squoosh for manual compression, Cloudinary for automated optimisation via CDN.

13. Eliminate render-blocking resources. JavaScript and CSS files loaded in the document head block page rendering until they finish executing. Defer non-critical JavaScript (add defer or async attributes), inline critical CSS, and move non-essential scripts to load after the main content. Google PageSpeed Insights identifies specific render-blocking resources on each page.

Site Architecture

14. Implement logical URL structure. URLs should be short, descriptive, and use hyphens as separators: /services/seo-audit rather than /services?category=12&item=89. Avoid parameter-heavy URLs for key content pages. Consistent, readable URL structure also improves click-through rate in search results.

15. Build and maintain internal linking. Every important page should be reachable within three clicks from your homepage. Pages with no internal links pointing to them ("orphan pages") may never be discovered or accumulated internal PageRank. After publishing new content, link to it from two or three topically related existing pages.

16. Ensure mobile usability. Google uses mobile-first indexing, meaning it primarily uses the mobile version of your content for ranking. Test your key pages in Google Search Console > Mobile Usability and in the URL Inspection tool. Fix text that is too small to read, buttons too close together to tap, and content that extends wider than the screen.

Structured Data

17. Implement Organisation or LocalBusiness schema. Organisation schema tells Google about your business: name, URL, logo, contact information, and social profiles. For local businesses, LocalBusiness schema additionally includes address, phone number, and opening hours. This enables your business information to appear correctly in Knowledge Panel results and rich search features.

18. Add content-type schemas. Add Article or BlogPosting schema to blog content. Use FAQPage schema on pages with FAQ sections (this can generate expanded FAQ rich results directly in search). Add BreadcrumbList schema to enable breadcrumb rich results. Validate all structured data using Google's Rich Results Test (search.google.com/test/rich-results) before publishing.

Running the Audit Without Paid Tools

This sequence works with free tools:

1. Google Search Console: Coverage report (indexing issues), Core Web Vitals report (field data), Mobile Usability report, Enhancements (structured data errors), Sitemaps
2. Google PageSpeed Insights: Per-page performance analysis with field and lab data and specific recommendations
3. Screaming Frog SEO Spider (free tier): Crawls up to 500 URLs, identifies broken links, redirect chains, missing title tags, duplicate content, and missing meta descriptions
4. Google Rich Results Test: Validates structured data markup
5. Chrome DevTools Lighthouse: On-demand audit covering Performance, SEO, Accessibility, and Best Practices for any page

For each issue found, start with the highest-impact fix. Indexing blocks (issues 1 to 3) take priority because no other optimisation matters if pages are not indexed. Core Web Vitals failures take second priority because they have a confirmed ranking impact.

Timelines for Seeing Results

• Crawl and indexing fixes (noindex removal, canonical corrections): 2 to 4 weeks after Google re-crawls
• Core Web Vitals improvements: visible in Search Console field data within 28 days
• Structured data additions: rich results typically appear within 4 to 6 weeks
• Submit fixed URLs for priority re-crawling via the URL Inspection tool in Search Console

For more context on how technical SEO fits into a full search strategy, read SEO for small business and how long does SEO take. For the specific audit steps used in each check, our technical SEO audit checklist goes deeper on finding and fixing each issue type.

If working through 18 technical checks is not practical alongside running your business, an experienced SEO specialist can complete a full technical audit and implement the fixes in two to three weeks. Our SEO service includes a comprehensive technical audit as the foundation of every engagement. Get a free assessment to see exactly where your site's technical gaps are.