March 5, 2026

Technical SEO Checklist 2026

Technical SEO hasn't gotten simpler — it's gotten more layered, now that AI crawlers sit alongside traditional search crawlers with their own access and rendering behavior. Here's a practical checklist that reflects both.

Crawlability & indexability

  • robots.txt allows the crawlers you actually want (Googlebot, Bingbot, and — deliberately — AI crawlers like GPTBot, Google-Extended, PerplexityBot, and ClaudeBot, unless you have a specific reason to block them)
  • XML sitemap is auto-generated, references only canonical, indexable URLs, and is submitted in Google Search Console
  • Canonical tags are present and self-referencing on every page, with no conflicting canonical/redirect signals
  • No orphaned pages — every important page is reachable through internal links, not just the sitemap

Site architecture & internal linking

  • A clear hierarchy: hub pages link to and from their related subpages (topic clusters), rather than a flat list of disconnected URLs
  • Internal links use descriptive anchor text, not just "click here" or "read more"
  • Breadcrumb navigation exists (and is marked up with BreadcrumbList schema) on every subpage

Core Web Vitals

  • Largest Contentful Paint (LCP) under 2.5s: hero images and fonts are optimized and preloaded where appropriate
  • Cumulative Layout Shift (CLS) near zero: images and embeds have explicit width/height, fonts are loaded with fallbacks that don't cause reflow
  • Interaction to Next Paint (INP) stays responsive: minimal blocking JavaScript on initial load, especially on static marketing pages

Structured data

  • Organization/ProfessionalService schema site-wide
  • Person schema for named experts/founders, consistent with their bio everywhere else on the site
  • FAQPage schema on any page with genuine Q&A content
  • Article/BlogPosting schema on blog posts and case studies
  • Validate everything with Google's Rich Results Test or the generic Schema Markup Validator — schema with syntax errors is often worse than no schema at all

JavaScript rendering

  • Confirm critical content renders in the initial HTML response, not only after client-side JavaScript executes — use "View Source" or a crawler simulation, not just your browser's rendered DOM
  • Test with Google's URL Inspection tool in Search Console to see exactly what Googlebot renders

AI-specific additions for 2026

  • An llms.txt file at the site root, summarizing who you are and what the site contains in plain language
  • Entity consistency: the same name, title, and description for your brand/founder across your schema, About page, and footer

None of this replaces good content — but without the technical foundation, even excellent content struggles to get crawled, indexed, and understood by either traditional search engines or AI systems.