Technical SEO Checklist 2026: Core Web Vitals, Schema, JS Rendering & INP
Technical SEO in 2026 is no longer just about robots.txt and sitemap.xml. With INP (Interaction to Next Paint) replacing FID as a Core Web Vital, JavaScript-heavy SPAs needing pre-rendering for AI engines, and structured data driving both Google rich results and AI citations, the surface area has grown. This checklist is what we run on every audit at ITD GrowthLabs SEO audits. Treat it as a self-serve scorecard — fix the failures and you'll outrank 80% of competitors who haven't updated their tech-SEO playbook since 2022.
Core Web Vitals 2026: LCP, INP, CLS
- LCP (Largest Contentful Paint): target < 2.5s. Common fixes: image preload hints, font-display swap, server response time < 600ms
- INP (Interaction to Next Paint): target < 200ms (replaced FID in March 2024). Fixes: minimise main-thread tasks, defer non-critical JS, web workers
- CLS (Cumulative Layout Shift): target < 0.1. Reserve space for images/ads, avoid late-injected DOM
Use Chrome DevTools Performance Insights, PageSpeed Insights, and CrUX dashboard. Lab data only confirms; field data is what Google uses for ranking.
JavaScript Rendering & SPAs
Single-page apps (React, Vue, Angular, Next.js) need:
- SSR or SSG — client-side-only rendering kills SEO. Next.js 14+ App Router with React Server Components is the 2026 default
- Critical CSS inline in initial HTML
- Preload key fonts with
<link rel="preload"> - Hydration optimisation — selective/island hydration wins
- Test with Google Search Console URL Inspection — see what Googlebot actually renders
Schema Markup Audit
Mandatory schemas in 2026:
- Organization + sameAs for the homepage
- BreadcrumbList on every non-home page
- Article + Person (author) on every blog post
- Product + AggregateRating + Offer on every product page
- FAQPage on every guide and Q&A-format page
- HowTo on procedural content
- LocalBusiness for location-based sites
- VideoObject for embedded videos
Validate with the Schema.org validator and Google Rich Results test.
Sitemap.xml & Robots.txt
- Sitemap must contain ALL canonical URLs (no duplicates, no parameters)
- Use sitemap index for sites >50,000 URLs
- Submit to Google Search Console + Bing Webmaster Tools
- robots.txt: explicitly allow CSS, JS, images (Google needs them for rendering)
- Don't block AI crawlers (GPTBot, ClaudeBot, PerplexityBot) unless you have a strategic reason — you'll lose AI citations
- Add lastmod date in sitemap; update when content changes
Hreflang & International SEO
- Use full ISO codes (en-IN, en-US, en-GB, en-AU, en-AE, en-ZA)
- Always include x-default
- Hreflang must be reciprocal (page A points to B, B points to A)
- Canonical and hreflang must agree (don't canonical en-IN to en-US)
- Use either HTML head, HTTP header, or sitemap — pick one and stick
Why ITD GrowthLabs for SEO & AEO: we run full-funnel SEO audits, SEO content sprints, and GEO/AEO retrofits for clients ranking on Google + ChatGPT + Perplexity simultaneously. Talk to us if you want one team owning both organic search and AI-search visibility.
Mobile-First Indexing & Mobile Performance
- Google indexes the mobile version of your site as primary since 2023
- Content parity: mobile must show all critical content (no “tap to read more” that hides body)
- Tap targets > 48px square; spacing > 8px between
- Avoid intrusive interstitials (Google penalty applies)
- Test mobile usability in Search Console
AI-Search Readiness (the 2026 Addition)
- Allow GPTBot, ClaudeBot, PerplexityBot, GoogleOther in robots.txt
- FAQPage schema on every Q&A page (drives AI citations)
- Question-format H2s with concise answer paragraphs
- TL;DR boxes at top of long-form content
- llms.txt file at site root listing your authoritative pages (emerging spec, optional but cheap)
Crawl Budget & Index Coverage
- Search Console: monitor “Pages indexed” vs “Pages discovered, not indexed”
- Fix soft 404s (200 OK with thin content)
- Use 301 for permanent moves, 302 only for temporary
- Block parametric URLs (filters, sorting) via robots.txt or canonical
- Pagination: rel=prev/next deprecated; use canonical to first page or self-canonical depending on UX
Want a Full Technical SEO Audit?
Get a 30-minute audit of your site's Core Web Vitals, schema, JS rendering and AI-search readiness. We'll send a prioritised fix-list within 72 hours.
Book My Technical SEO AuditFrequently Asked Questions
What are the Core Web Vitals targets for 2026?
LCP under 2.5 seconds, INP under 200 milliseconds (replaced FID in March 2024), CLS under 0.1. Use field data from CrUX dashboard, not just lab data from PageSpeed Insights, since Google uses field data for ranking signals.
How do I fix INP for a JavaScript-heavy site?
Reduce main-thread blocking: code-split, defer non-critical JS, move heavy work to web workers, use React 18+ concurrent rendering, debounce input handlers, and avoid layout-thrash in event handlers. PageSpeed Insights now flags specific INP-blocking interactions.
Should I block AI crawlers like GPTBot in robots.txt?
Generally no. Blocking AI crawlers means losing AI citations across ChatGPT, Claude and Perplexity, which is now 22-30% of informational query traffic. Block only if you have a strategic content-licensing reason (publishers, paywalled news sites).
What is the most important schema for SEO in 2026?
Three are essential: Organization (homepage), Article + Person (blog posts), and FAQPage (guides and Q&A pages). FAQPage is uniquely powerful because it drives both Google rich results AND AI engine citations.
How often should I run a technical SEO audit?
Quarterly for stable sites, monthly for high-velocity SaaS or e-commerce sites with frequent code deploys. Always audit after major redesigns, framework migrations, or domain moves.