Skip to content
Strynal, Digital Agency

AI Visibility 9 min read

A Technical SEO Checklist for 2026

A practical technical SEO checklist for 2026 covering crawlability, indexation, sitemaps, canonicals, Core Web Vitals, mobile experience, and structured data.

By Strynal Team

Most SEO conversations start with keywords and content. That is the right instinct, but content only performs if search engines can reliably find, parse, and trust the page hosting it. Technical SEO is the foundation. Get it wrong and everything built on top costs more than it should.

This checklist covers the mechanics: crawlability, indexation, sitemaps, canonicals, page speed, mobile experience, and structured data. For each item, the why matters as much as the what, so that’s included too.

Crawlability: Let Search Engines In (and Nothing Else)

A crawler that cannot reach your content cannot index it. Start here.

robots.txt

  • Confirm the file exists at yourdomain.com/robots.txt.
  • Make sure no production pages or assets are accidentally blocked. A stray Disallow: / has wiped entire sites from search results.
  • Block crawlers from low-value paths: /admin/, /checkout/, internal search result pages, and any URL pattern that generates near-duplicate content at scale (e.g., ?sort=, ?color=).
  • If you use multiple sitemaps, reference them all in robots.txt.

Crawl Budget

Large sites with thousands of URLs benefit from deliberate crawl budget management. Paginated archives, faceted navigation, and session-based URL parameters inflate the crawlable surface area without adding indexable value. Use URL parameter handling in Google Search Console and rel="nofollow" or canonical signals to guide crawlers toward the pages that matter.

Crawl budget is finite. Every page a bot wastes time on is a page it didn’t spend on your best content.

Internal Linking Depth

Pages more than three or four clicks from the homepage rarely get crawled regularly. A clean internal link structure keeps important pages close to the surface. Website information architecture is the right place to start that conversation.

Indexation: What You Want in the Index (and What You Don’t)

Crawlability and indexation are not the same thing. A crawler can reach a page and still choose not to index it, or you can actively prevent indexation even when crawling is allowed.

Noindex Audit

  • Run a crawl (Screaming Frog, Ahrefs Site Audit, or similar) and pull every page with a noindex meta tag or X-Robots-Tag: noindex header.
  • Tag utility pages (thank-you pages, internal dashboards, author archives) with noindex deliberately. Do not leave them in the index generating thin-content signals.
  • Do not noindex pages you want to rank. This is more common than you’d think; staging environment settings sometimes bleed into production deployments.

Canonical Tags

Every indexable page should have a self-referencing canonical (<link rel="canonical" href="https://yourdomain.com/page/">). For content that appears in multiple locations (syndicated articles, product pages with URL parameters, paginated series), the canonical tag tells search engines which version to credit. Canonical Tags and How to Fix Duplicate Content covers the full set of edge cases and recovery steps.

Common mistakes:

  • Canonicals pointing to 301-redirect chains instead of the final URL.
  • HTTP versions of pages canonicalizing to themselves instead of HTTPS.
  • CMS templates rendering dynamic canonicals that pull the wrong URL on faceted pages.

Duplicate Content Signals

Identical or near-identical content across multiple URLs dilutes ranking signals. Audit for:

  • www vs. non-www serving both on HTTPS without a redirect.
  • Trailing slash inconsistency (/about vs. /about/ both returning 200).
  • Protocol duplication (HTTP pages not redirecting to HTTPS).

Pick one canonical form for every URL pattern and enforce it with server-level 301 redirects. Getting URL structure and site hierarchy right upstream prevents many of these inconsistencies from arising in the first place.

Sitemaps: A Direct Map to Your Content

An XML sitemap does not guarantee indexation. It is a crawl hint, a way to make sure Googlebot knows every URL you care about and when it was last updated.

Sitemap Best Practices

  • Include only canonical, indexable URLs. A sitemap full of noindex pages or redirect sources misleads crawlers.
  • Keep individual sitemaps under 50,000 URLs and 50 MB uncompressed. Use a sitemap index file to group them.
  • Set <lastmod> accurately. If your CMS updates this date every time the layout changes but the content hasn’t changed, that noise trains crawlers to ignore your timestamps.
  • Submit your sitemap URL in Google Search Console and Bing Webmaster Tools. Then monitor for errors.

For dynamically generated sites, make sure the sitemap pipeline includes new and updated content promptly. A sitemap that lags three weeks behind your blog defeats the purpose.

Page Speed and Core Web Vitals

Page speed has been a ranking factor since 2010. Core Web Vitals (Largest Contentful Paint or LCP, Interaction to Next Paint or INP, and Cumulative Layout Shift or CLS) became part of Google’s Page Experience signals in 2021 and remain relevant. More practically, speed directly affects bounce rate and conversion. The two goals align. The real cost of a slow website is worth reading if you need the business case alongside the technical one.

LCP (Largest Contentful Paint): Target under 2.5 seconds

LCP measures when the largest visible element (usually a hero image or headline) loads. Fixes that move the needle:

  • Preload your LCP image using <link rel="preload" as="image">.
  • Serve images in modern formats (WebP or AVIF); WebP typically cuts file sizes 25–35% versus JPEG.
  • Use a CDN so assets load from an edge node near the user.
  • Eliminate render-blocking scripts and stylesheets above the fold.

INP (Interaction to Next Paint): Target under 200ms

INP replaced First Input Delay in 2024. It measures the latency of all interactions across a page visit, not just the first. Heavy JavaScript, long tasks on the main thread, and unoptimized event handlers are the usual culprits. Tools like Chrome DevTools’ Performance panel and the scheduler.yield() API help break up long tasks.

CLS (Cumulative Layout Shift): Target under 0.1

Layout shift happens when content moves unexpectedly, most often because images lack explicit width/height attributes, ads inject without reserved space, or web fonts cause a flash of unstyled text that reflows the layout. Set dimensions on all images and iframes. Reserve space for ads and embeds. Use font-display: swap or optional with proper fallback metrics.

Mobile Experience

Google indexes the mobile version of your site first. Mobile-first indexing has been the default for years. If your mobile experience is degraded, your rankings reflect that.

Mobile Technical Checklist

  • Verify your site uses a responsive layout, not a separate m. subdomain with inconsistent content.
  • Test viewport configuration: <meta name="viewport" content="width=device-width, initial-scale=1"> must be present.
  • Tap targets (buttons, links) should be at least 48×48px with adequate spacing.
  • Avoid interstitials that obscure the main content immediately on mobile page load; Google penalises these.
  • Run Google’s Mobile-Friendly Test and Lighthouse in mobile mode. Look at real field data in Search Console’s Core Web Vitals report, not just lab scores.

The technical and design layers need to be in sync. Run your mobile audit against real field data, not just Lighthouse lab scores.

Structured Data: Signal, Not Decoration

Structured data (Schema.org markup, typically delivered as JSON-LD) helps search engines understand what a page is about: not just that it contains words, but that those words describe an article, a product, an event, a person. It also powers rich results: review stars, FAQ dropdowns, breadcrumbs, and sitelinks search boxes.

For brands investing in AI-driven search visibility, structured data is increasingly important. AI answer engines parse semantic markup to extract entities and relationships. Structured data for brand visibility goes deep on this. At the surface level, every site should implement:

  • Organization schema on the homepage: name, URL, logo, social profiles, contact point.
  • WebSite schema with a SearchAction if the site has internal search.
  • BreadcrumbList on every page below the homepage.
  • Article or BlogPosting on all editorial content, including author, datePublished, dateModified, and image.
  • FAQPage where relevant; this drives FAQ rich results and feeds AI answer extracts.

A Practical Guide to Schema Markup Types covers which types apply across different content and business contexts. Validate all markup with Google’s Rich Results Test and Schema.org’s validator. Broken JSON-LD silently fails; you won’t get an error, you’ll just lose the benefit.

HTTPS, Security, and Redirect Health

These are table stakes in 2026 but they still trip up sites during rebuilds and migrations.

  • Every page must be served over HTTPS with a valid, non-expired certificate. Mixed content (HTTP assets on an HTTPS page) still generates browser warnings and can affect trust signals.
  • All HTTP URLs should 301-redirect to HTTPS. All www URLs should 301-redirect to the canonical non-www form (or vice versa; pick one and be consistent).
  • Audit your redirect chains. Every hop in a chain leaks a small amount of link equity and adds latency. Collapse A → B → C to A → C.
  • Set up Strict-Transport-Security (HSTS) headers once you’re confident HTTPS is stable. This prevents protocol downgrade attacks and signals security posture to crawlers.

Keeping the Checklist Current

Technical SEO is not a one-time audit. Sites change (new templates, CMS upgrades, marketing campaigns that introduce tracking parameters), and each change can reintroduce problems. Schedule a quarterly crawl. Watch Search Console’s Coverage and Core Web Vitals reports for trend changes. Set up uptime and certificate expiry alerts so you catch regressions before they compound.

For sites investing seriously in organic and AI search visibility, the AI visibility services at Strynal pair technical hygiene with content strategy and structured data depth, treating search performance as a system, not a checklist to complete once and file away.

How Strynal Approaches Technical SEO

At Strynal, technical SEO is baked into how we build, not bolted on after launch. When we design and build a site, crawlability, performance, and structured data are architectural decisions, not an afterthought the marketing team surfaces six months later. Every project starts on a blank page, which means no inherited template debt dragging down your Lighthouse scores before you’ve written a word.

If your site has accumulated technical debt (redirect chains, inconsistent canonicals, Core Web Vitals in the red) or if you are planning a redesign and want to get the technical foundation right the first time, reach out. Bring your crawl data if you have it; we’ll come with opinions.