Technical SEO Checklist for 2026: Core Web Vitals, Indexing, and Crawlability

A website can have excellent content and still struggle in search results if search engines cannot crawl it properly, decide not to index it, or find that it loads slowly for real visitors. Technical Search Engine Optimization is the part of the work that makes sure none of those problems stand between your pages and your audience.

This checklist is written for business owners, marketing teams, and developers who want a clear, practical way to review a website in 2026. It is organised in the order that problems usually need to be solved: first, can search engines reach your pages; second, are those pages being indexed; and third, do they deliver a good experience once a visitor arrives. Each item explains what to check, why it matters, and how to fix it.

What Is Technical SEO and Why Does It Still Matter in 2026?

Technical Search Engine Optimization covers everything that helps search engines discover, understand, and store your pages, along with the performance factors that shape how visitors experience them. It does not replace good content. It makes sure good content gets a fair chance to rank.

The importance of this foundation has grown rather than shrunk. Google now crawls and indexes websites using its smartphone crawler, so the mobile version of your site is the version that counts. Artificial Intelligence search features, such as Google’s AI Overviews and answer engines like ChatGPT Search and Perplexity, also rely on pages they can access and interpret cleanly. If a page is blocked, slow, or poorly structured, it is less likely to appear in traditional results and less likely to be cited in AI-generated answers.

Part 1: Crawlability Checklist

Crawlability is about whether search engine bots can find and access your pages. If a page cannot be crawled, nothing else on this list matters for that page.

1. Review Your Robots.txt File

Your robots.txt file, found at yourdomain.com/robots.txt, tells crawlers which areas of your site they may and may not request. A single incorrect line can block an entire website, and this happens more often than most people expect, especially after a site moves from a staging environment to a live domain.

• Confirm that important folders such as /blog/, service pages, and product pages are not disallowed.
• Make sure CSS and JavaScript files are not blocked, because Google needs them to render pages correctly.
• Add a line pointing to your XML sitemap, for example Sitemap: https://yourdomain.com/sitemap_index.xml.
• Decide deliberately how you want to treat Artificial Intelligence crawlers such as GPTBot, Google-Extended, and PerplexityBot. Blocking them may reduce the chance of your brand being referenced in AI answers.

Remember that robots.txt controls crawling, not indexing. A blocked page can still appear in search results if other websites link to it. If you want a page kept out of the index, use a noindex tag instead and allow it to be crawled so the tag can be seen.

2. Submit and Maintain an Accurate XML Sitemap

An XML sitemap is a list of the pages you want search engines to know about. Most WordPress search plugins, such as Yoast SEO and Rank Math, generate one automatically, but automatic does not always mean accurate.

• Submit the sitemap in Google Search Console and Bing Webmaster Tools.
• Include only pages that return a 200 status code, are indexable, and use their own canonical URL.
• Remove redirected URLs, deleted pages, thin tag archives, and pages marked noindex.
• Check that the last modified dates update when content genuinely changes.

3. Build a Logical Internal Linking Structure

Search engines discover most pages by following links. A page with no internal links pointing to it, often called an orphan page, may be crawled rarely or not at all, even if it appears in your sitemap.

• Keep important pages within three clicks of the homepage.
• Link from relevant blog posts to the service pages they support, using descriptive anchor text rather than phrases such as “click here”.
• Use breadcrumb navigation so both visitors and crawlers can understand where a page sits in your site hierarchy.
• Run a crawl with a tool such as Screaming Frog or Sitebulb to find orphan pages and deep pages that need stronger links.

4. Fix Broken Links and Redirect Chains

Broken links waste crawl activity and frustrate visitors. Redirect chains, where one URL redirects to another that redirects again, slow down both users and bots.

• Find internal links that return 404 errors and update them to point to the correct live page.
• Replace redirect chains with a single 301 redirect from the old URL to the final destination.
• Update internal links so they point directly to the final URL instead of relying on a redirect.

5. Check Crawl Activity in Google Search Console

The Crawl Stats report, found under Settings in Google Search Console, shows how often Googlebot visits your site, which response codes it receives, and how quickly your server responds. A sudden increase in server errors or a sharp rise in response time is an early warning sign that crawling may slow down.

Crawl budget, the number of pages Google is willing to crawl in a given period, is mainly a concern for large websites with many thousands of URLs. For smaller business websites, the more common issue is not a shortage of crawl budget but crawl waste on filtered URLs, duplicate parameters, and low-value archive pages.

6. Make Sure JavaScript Content Can Be Rendered

If important content, links, or navigation only appear after JavaScript runs, search engines have to render the page before they can see them. Google can render JavaScript, but rendering may be delayed, and some Artificial Intelligence crawlers do not render JavaScript at all.

• Use the URL Inspection tool in Google Search Console and view the rendered HTML to confirm that your main content appears.
• Make sure navigation links use standard <a href> elements instead of click events alone.
• Where possible, use server-side rendering or static generation for important content.

Part 2: Indexing Checklist

Being crawled does not guarantee being indexed. Google evaluates each page and decides whether it deserves a place in its index. These checks help you understand and influence that decision.

7. Review the Page Indexing Report

The Page Indexing report in Google Search Console groups your URLs into indexed and not indexed, along with the reason for each exclusion. Two statuses deserve particular attention:

• Discovered – currently not indexed: Google knows the URL exists but has not crawled it yet. This often points to weak internal linking or a large volume of low-value URLs competing for attention.
• Crawled – currently not indexed: Google visited the page and chose not to index it. This is usually a content quality or duplication signal, not a technical fault.

Not every excluded URL is a problem. Redirects, intentional noindex pages, and alternate versions with correct canonical tags are expected to appear here. Focus on pages that you want ranking but that are missing.

8. Audit Noindex Tags

An accidental noindex tag is one of the fastest ways to make a page disappear from search. It frequently happens when the “Discourage search engines from indexing this site” setting in WordPress is left switched on after launch, or when a plugin applies noindex to a whole content type.

• In WordPress, go to Settings, then Reading, and confirm that the search engine visibility box is unchecked.
• Check your search plugin settings for each post type and taxonomy.
• Use a crawler to list every URL carrying a noindex directive and confirm each one is intentional.

9. Set Correct Canonical Tags

A canonical tag tells search engines which version of a page is the main one when similar or identical content exists at more than one URL. Common examples include URLs with tracking parameters, printer-friendly versions, and product pages reachable through several category paths.

• Every indexable page should have a self-referencing canonical tag.
• Duplicate or near-duplicate pages should point their canonical to the preferred version.
• Canonical URLs should use the same protocol, domain version, and trailing slash format as the rest of your site.

Google treats canonical tags as a strong hint rather than a strict instruction. If your internal links, sitemap, and canonical tags disagree, Google may choose a different canonical than the one you intended. Consistency across all three signals is what makes the canonical stick.

10. Resolve Duplicate and Thin Content

Pages that offer very little unique value, or that repeat content found elsewhere on your site, are less likely to be indexed. They also dilute the signals that should be flowing to your stronger pages.

• Merge pages that target the same topic and search intent, then redirect the weaker version.
• Add genuinely useful detail to thin service or location pages instead of swapping the city name on a template.
• Consider applying noindex to low-value archives, such as author or date archives on single-author blogs.

11. Use a Consistent URL Structure and HTTPS

Every page should be reachable at a single, secure address. If your site responds at both http:// and https://, or at both www and non-www versions, search engines may treat them as separate pages.

• Redirect all variations to one preferred version with a permanent 301 redirect.
• Keep URLs short, readable, and descriptive, for example /web-development/landing-page-design/ rather than /page?id=4821.
• Check for mixed content warnings, where a secure page loads images or scripts over an insecure connection.

12. Add Structured Data That Matches the Page

Structured data, usually written in JSON-LD format, helps search engines understand what a page is about and who is behind it. It can also support rich results in search. Add only schema types that reflect content visible on the page.

• Organization or LocalBusiness on the homepage and contact page.
• Service on service pages.
• Article or BlogPosting on blog posts, including author and publication date.
• BreadcrumbList across the site.
• Product and Review on ecommerce product pages, where reviews are genuine.

Validate your markup with the Rich Results Test and the Schema Markup Validator, and monitor the Enhancements section in Google Search Console for errors.

Part 3: Core Web Vitals and Page Experience Checklist

Core Web Vitals are a set of metrics Google uses to measure real-world user experience. They are measured from actual visitor data collected through the Chrome User Experience Report, and a page is assessed on the experience of the 75th percentile of visits. In practical terms, most of your visitors need a good experience, not only those on fast connections.

13. Largest Contentful Paint: Loading Performance

Largest Contentful Paint measures how long it takes for the largest visible element, often a hero image or main heading, to appear on screen. A good score is 2.5 seconds or less.

• Compress and resize images, and serve them in modern formats such as WebP or AVIF.
• Do not lazy-load the main hero image; instead, preload it so the browser fetches it early.
• Improve server response time through quality hosting, page caching, and a content delivery network.
• Reduce render-blocking CSS and JavaScript, particularly from page builders and unused plugins.

14. Interaction to Next Paint: Responsiveness

Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024. It measures how quickly a page responds visually after a visitor clicks, taps, or types, across the whole visit rather than only the first interaction. A good score is 200 milliseconds or less.

• Audit third-party scripts, such as chat widgets, tracking tags, and advertising pixels, and remove any that no longer earn their place.
• Delay non-essential JavaScript until after the page has loaded or until the user interacts.
• Break up long JavaScript tasks so the browser can respond to input between them.
• Limit heavy animations and sliders, which often consume processing time on mobile devices.

15. Cumulative Layout Shift: Visual Stability

Cumulative Layout Shift measures how much the page content moves around unexpectedly while it loads. A good score is 0.1 or less. Layout shift is the reason a visitor sometimes taps the wrong button because something above it suddenly appeared.

• Set width and height attributes on images and videos so the browser can reserve space for them.
• Reserve fixed space for banners, embeds, and advertising slots.
• Load web fonts carefully, using font-display: swap and preloading key font files to reduce text reflow.
• Avoid inserting content above existing content unless it is a direct response to a user action.

16. Measure With Field Data, Not Only Lab Tests

Lighthouse and PageSpeed Insights lab scores are useful for diagnosing problems, but Google’s assessment is based on field data from real visitors. A page can score well in a lab test and still fail Core Web Vitals in the field because real users have slower devices and networks.

• Use the Core Web Vitals report in Google Search Console to see which groups of URLs pass or fail.
• Use the “Discover what your real users are experiencing” section of PageSpeed Insights for page-level field data.
• After fixing an issue, allow around 28 days for field data to reflect the change, then use the Validate Fix option in Search Console.

17. Confirm the Mobile Experience

Because Google indexes the mobile version of your site, any content, links, or structured data missing on mobile may be missing from Google’s view of your page entirely.

• Make sure the mobile version contains the same main content and headings as the desktop version.
• Check that tap targets are large enough and not crowded together.
• Avoid intrusive pop-ups that cover the main content as soon as a visitor lands from search.
• Test key templates on real mid-range Android devices, not only on a desktop browser resized to mobile width.

Part 4: Ongoing Technical SEO Maintenance

Technical issues rarely stay fixed forever. Plugin updates, theme changes, new page templates, and content migrations can all introduce new problems. A simple maintenance routine catches them before they affect rankings.

• Weekly: Check Google Search Console for new indexing errors, manual actions, and security issues.
• Monthly: Run a full site crawl, review the Core Web Vitals report, and fix new broken links.
• Quarterly: Review robots.txt, sitemap accuracy, redirect rules, structured data, and plugin load on performance.
• Before and after every major change: Crawl the site, compare results, and keep a record of what changed.

If you are already seeing a decline in traffic, our guide on why your website may be losing organic traffic walks through the twelve most common causes and how to diagnose each one. Regular website maintenance also prevents many technical issues from appearing in the first place.

How Technical SEO Supports Visibility in AI Search

Artificial Intelligence search tools still depend on the same foundations covered in this checklist. A page that is crawlable, indexed, clearly structured with meaningful headings, and supported by accurate structured data is far easier for these systems to read, summarise, and cite.

Technical health is the entry requirement, but it is not the full picture. Brand mentions, authoritative content, and clear answers to real questions also influence whether AI tools reference your business. We cover those factors in detail in our guide on how to get your brand mentioned by AI search engines, and you can learn more about our approach to AI search optimization.

Quick Technical SEO Checklist for 2026

Use this summary as a working list during your next review.

Crawlability

• Robots.txt does not block important pages, CSS, or JavaScript
• XML sitemap is accurate and submitted to Google and Bing
• Important pages are within three clicks of the homepage
• No orphan pages, broken internal links, or redirect chains
• Crawl Stats show stable response times and few server errors
• Main content and links are visible in the rendered HTML

Indexing

• Page Indexing report reviewed and unexpected exclusions resolved
• No accidental noindex tags
• Self-referencing canonical tags on every indexable page
• Duplicate and thin pages merged, improved, or excluded
• One secure, consistent version of every URL
• Valid structured data that matches visible content

Core Web Vitals and Page Experience

• Largest Contentful Paint at or under 2.5 seconds
• Interaction to Next Paint at or under 200 milliseconds
• Cumulative Layout Shift at or under 0.1
• Field data reviewed in Search Console and PageSpeed Insights
• Mobile version matches desktop content and is easy to use

Frequently Asked Questions

How often should I run a technical SEO audit?

A full technical audit every quarter works well for most business websites, with lighter monthly checks in Google Search Console. You should also run an audit before and after any redesign, migration, or major plugin change, because these are the moments when serious issues are most often introduced.

Are Core Web Vitals a major ranking factor?

Core Web Vitals are part of Google’s page experience signals, but they do not outweigh relevance and content quality. A fast page with weak content will not outrank a genuinely helpful page simply because it loads faster. Their real value is that they improve the experience for visitors, which supports engagement and conversions, and they can make a difference when competing pages are otherwise similar in quality.

Why is Google not indexing my new pages?

The most common reasons are an accidental noindex tag, a robots.txt block, weak internal linking, or content that Google considers too similar to other pages. Start by inspecting the URL in Google Search Console, which shows whether the page can be crawled, whether it is indexed, and which canonical Google has selected. Then make sure the page is linked from relevant existing pages and offers something distinct.

What is the difference between crawling and indexing?

Crawling is when a search engine bot visits a page and downloads its content. Indexing is when the search engine processes that content and stores it so it can appear in search results. A page must be crawled before it can be indexed, but being crawled does not guarantee it will be indexed.

Can I handle technical SEO myself on a WordPress website?

Many basic checks are manageable without a developer, including reviewing Google Search Console, configuring a search plugin, compressing images, and fixing broken links. Issues such as JavaScript rendering, server performance, complex redirects, and Interaction to Next Paint optimisation usually benefit from technical expertise, because the cause is often buried in theme code, plugins, or hosting configuration.

Does technical SEO affect visibility in AI search tools?

Yes. AI search tools need to access and interpret your pages before they can reference them. Pages that are blocked, slow, or rely heavily on JavaScript to display content are harder for these systems to use. Strong technical health does not guarantee a mention, but weak technical health makes one much less likely.

Need Help With Your Technical SEO?

Working through this checklist will uncover most of the technical issues holding a website back. The harder part is deciding which problems to fix first and implementing those fixes without breaking something else. That is where an experienced team makes a difference.

TechBlare reviews crawlability, indexing, Core Web Vitals, and site architecture together, then gives you a prioritised plan based on what will have the greatest effect on your visibility and leads. If you would like a clear picture of your website’s technical health, explore our Search Engine Optimization and digital marketing services and speak with our team about a technical review.