A technical SEO checklist for 2026 covers six core areas: crawlability, indexation, Core Web Vitals, structured data, site architecture, and AI search readiness. Get all six right and you remove every technical obstacle between your content and a ranking. Miss any one of them and you are leaving performance on the table regardless of how good your content is.
This is not a 200-point checklist. It is the senior version — the checks that actually move rankings, ordered by priority.
Why 2026 Is Different
Technical SEO in 2026 is no longer just about Googlebot. Your site is now crawled by ChatGPT (GPTBot), Perplexity (PerplexityBot), Claude (ClaudeBot), Gemini (Google-Extended), and a growing number of AI agents that pull content for answers and citations.
The fundamentals have not changed. What has changed is the surface area. According to Google’s crawler documentation, there are now over 20 distinct Google crawlers — and external AI systems add another layer. A site optimised only for classic Googlebot is already incomplete.
The teams winning organic and AI-referred traffic in 2026 are the ones that ship clean HTML, real performance numbers, and clear authority signals — and they do it consistently.
1. Crawlability
Crawlability is the foundation. If a crawler cannot access your pages, nothing else matters.
robots.txt
Your robots.txt should explicitly allow AI crawlers alongside Googlebot. Many sites still block GPTBot and ClaudeBot by default through catch-all Disallow rules written years ago.
Minimum viable configuration:
User-agent: Googlebot
Allow: /
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /Block only what genuinely should not be crawled: staging paths, admin panels, internal search result pages, and checkout flows.
XML Sitemaps
- Segment your sitemap by content type (posts, pages, products) rather than one flat file above 10,000 URLs
- Submit all sitemap files in Google Search Console and Bing Webmaster Tools
- Update sitemaps automatically on publish — if your sitemap requires a manual update, it will fall out of date
- Exclude URLs with
noindexfrom your sitemap — a URL cannot be both in your sitemap and noindexed without confusing crawlers
Crawl Budget
For most sites under 1,000 pages, crawl budget is not a problem. For large ecommerce sites or news sites, it is critical.
The fastest win is blocking low-value URL patterns via robots.txt or canonical tags: session IDs, tracking parameters, faceted navigation combinations, and internal search results. Every crawl wasted on /products?color=red&sort=price&page=4 is a crawl not spent on your money pages.
Check your crawl stats in Google Search Console under Settings → Crawl Stats. If Googlebot is crawling thousands of pages but only a fraction are indexed, you have a crawl budget problem.
2. Indexation
Crawled does not mean indexed. Indexation is where most technical problems actually live.
Index Coverage Audit
Run this monthly in GSC → Index → Pages. The report splits URLs into indexed, not indexed, and error categories. For each “not indexed” reason:
- Discovered, not crawled: Server too slow, crawl budget too low, or too many links to process
- Crawled, not indexed: Content too thin, too similar to existing pages, or a quality signal issue
- Excluded by robots.txt: Usually intentional — verify it is
- Alternate page with proper canonical: Fine if the canonical is correct; a problem if it is wrong
Canonical Tags
Every page should have a self-referencing canonical in the <head>. For pages with duplicate or near-duplicate content (product variants, paginated pages, URL parameters), the canonical should point to the version you want indexed.
Common mistakes:
- Canonical on page 2 of a paginated series pointing to page 1 (signals thin content)
- Canonical on a product variant pointing to the main product while also keeping the variant in the sitemap
- HTTP version canonicalising to HTTPS but still returning a 200 (should redirect instead)
Duplicate Content
Duplicate content does not cause a “penalty” — but it dilutes your link equity and confuses Google about which URL to rank. Consolidate with 301 redirects where possible. Use canonicals where redirection is not practical (product variants, faceted pages). For the full rule set — self-referencing canonicals, pagination, hreflang conflicts — and a step-by-step audit framework, see the dedicated guide to canonical tags and duplicate content.
Internal site: check using a crawler (Screaming Frog, Sitebulb). External duplication (scrapers, syndicators): use canonical in the syndicated copy pointing to your original.
3. Core Web Vitals
Google’s Page Experience signals use field data — real user measurements collected by Chrome. Lab data (Lighthouse, PageSpeed Insights) is for debugging. Field data is what ranks.
LCP — Largest Contentful Paint (target: under 2.5s)
LCP measures when the largest visible element loads. In most cases this is a hero image or H1. For a deeper look at how Core Web Vitals actually affect rankings, the dedicated guide covers the nuances that the checklist format cannot. The most common causes of slow LCP:
- Hero image not preloaded (
<link rel="preload">in<head>) - Image missing
fetchpriority="high"attribute - Image in WebP or AVIF but still oversized for the viewport
- Server TTFB above 600ms (hosting or caching issue)
INP — Interaction to Next Paint (target: under 200ms)
INP replaced FID in March 2024. It measures the delay between any user interaction (click, tap, keypress) and the browser’s visual response. The main culprits:
- Heavy JavaScript blocking the main thread
- Large event listeners firing synchronously
- Unoptimised third-party scripts (chat widgets, analytics, tag managers)
Use Chrome DevTools Performance panel to identify long tasks above 50ms. Break them up with setTimeout or move them off the main thread. For JavaScript-heavy sites, the JavaScript SEO guide covers how rendering choices affect crawlability and Core Web Vitals together.
CLS — Cumulative Layout Shift (target: under 0.1)
CLS measures visual instability. Common causes:
- Images without explicit
widthandheightattributes - Ads or embeds without reserved space
- Web fonts causing FOUT (Flash of Unstyled Text) that shifts layout
- Late-loading banners or cookie notices injecting above content
Reserve space for every dynamic element. Add width and height to every image — even if you override them with CSS.
4. Structured Data
Structured data does not directly boost rankings, but it enables rich results (FAQ dropdowns, review stars, how-to steps) that increase CTR — which does affect ranking signals over time.
What to implement
| Schema type | Where to use |
|---|---|
Organization + WebSite | Site-wide, in <head> |
BlogPosting / Article | Every blog post |
FAQPage | Pages with a visible FAQ section |
BreadcrumbList | Every nested URL |
LocalBusiness | Service area pages, contact page |
ProfessionalService | Main service pages with reviews |
What to avoid
- Do not mark up content that is not visible on the page — Google will reject it
- Do not use
AggregateRatingon genericServicetype — it requiresLocalBusinessor a subtype - Do not add
FAQPageschema if the FAQs are hidden behind a JavaScript expand/collapse and not in the initial HTML render
Validate everything in Google’s Rich Results Test before deploying.
5. Site Architecture
Site architecture determines how link equity flows through your site and how deep crawlers have to go to find your content.
URL depth
Key pages should be reachable within 3 clicks from the homepage. Pages buried at depth 6 or 7 rarely get crawled consistently and accumulate almost no internal link equity.
Audit your click depth with a crawler. If category or service pages are deeper than 3, flatten the structure or add prominent internal links from higher-level pages.
Internal linking
Internal links pass authority and signal topic relevance. A page with zero internal links pointing to it is effectively invisible to crawlers — what Google calls an “orphan page.”
Every time you publish a new post or page:
- Link to it from 2–3 existing relevant pages
- Include it in the relevant section of your sitemap
- Add it to any relevant navigational elements (category pages, resource hubs)
For a freelance SEO consultant site, the most valuable internal links go to service pages (/services/technical-seo/, /services/seo-audit/) from high-traffic blog posts. This is exactly how you transfer editorial authority to commercial pages without building external links to them directly. I track this deliberately across every project — the internal link structure often matters more than the external link count for service-type sites.
Redirect chains
Each redirect in a chain loses a small amount of link equity and slows page load. Run a redirect audit quarterly. Any chain of 3+ redirects should be collapsed to a single direct redirect.
6. AI Search Readiness
AI engines (ChatGPT, Perplexity, Gemini, Claude) cite content differently from traditional search. They pull structured answers, quote specific sentences, and attribute sources. Here is what signals your content is citable:
llms.txt
Add a llms.txt file at your domain root. It is not a standard yet, but it is becoming the AI equivalent of robots.txt — a machine-readable summary of your site’s key content and structure. Format:
# Site: YourSite
# Description: What you do, briefly
## Key pages
- [Home](https://yoursite.com/)
- [About](https://yoursite.com/about/)
- [Service: SEO Audit](https://yoursite.com/services/seo-audit/)E-E-A-T signals
Google’s Quality Raters Guidelines place heavy emphasis on Experience, Expertise, Authoritativeness, and Trustworthiness. For AI engines, the same signals matter when deciding what to cite:
- Author bylines with name and credentials on every post
- Author bio page with external profile links (LinkedIn, Twitter/X)
- Publish date and last-modified date rendered in HTML (not JS-only)
- About page with real credentials and background
- External citations and data references within content
Content structure for AI quotability
Short paragraphs. Direct statements. Clear H2 and H3 headings that describe what each section covers. Avoid burying the answer in the middle of a long paragraph. AI engines extract the clearest sentence that answers a query — write every key point as if it could stand alone as a cited answer.
The Audit Process
Running this checklist manually across a large site takes days. Here is the senior workflow:
- Crawl the site with Screaming Frog or Sitebulb. Export all URLs with status codes, canonical tags, meta robots, and title/description data.
- Pull GSC data: Index coverage report, Core Web Vitals field data, and crawl stats.
- Validate structured data: Sample 10–20 URLs in Rich Results Test.
- Run PageSpeed Insights on your top 10 landing pages (by traffic and by revenue).
- Check robots.txt and sitemap manually — automated tools miss logic errors.
- Audit redirect chains and orphan pages from your crawler export.
- Review llms.txt and AI bot allowlist in robots.txt.
Prioritise by impact: crawlability > indexation > Core Web Vitals > structured data > architecture > AI readiness. Fix what blocks traffic first.
If you want this run against your site with a prioritised action plan, the SEO audit is the right starting point. The technical SEO service covers implementation once you know what needs fixing. To see how every item on this checklist fits into the broader technical SEO picture, the Technical SEO Hub maps it all in one place.
Frequently Asked Questions
How often should I run a technical SEO audit?
For most sites, a full technical audit every 6 months is sufficient. After major migrations, CMS changes, or redesigns, run one immediately. Keep a lightweight monthly check on crawl errors, index coverage, and Core Web Vitals in Google Search Console — these catch regressions before they compound.
What is the most important technical SEO factor in 2026?
Crawlability and indexation still come first — a fast, beautifully structured site that Google cannot crawl or index ranks nowhere. After that, Core Web Vitals (especially LCP and INP on mobile) and structured data have the highest direct correlation with ranking performance.
How do I check if my site passes Core Web Vitals?
Use the Core Web Vitals report in Google Search Console for real-user data (field data). For diagnostics, run PageSpeed Insights on your key URLs. Lab data is useful for debugging; field data is what Google actually uses for ranking.
What is crawl budget and does it matter for my site?
Crawl budget is the number of URLs Googlebot crawls on your site per day. For sites under 1,000 pages with fast servers, it rarely matters. It becomes critical for large ecommerce sites with thousands of product variants or faceted navigation — where Googlebot can waste budget on low-value pages instead of your key content.
How do I make my site readable by AI search engines?
Add a llms.txt file at your domain root. Ensure author bylines, publish dates, and last-modified dates are in HTML. Allow AI crawlers in robots.txt. Write in clear, structured prose. E-E-A-T signals — author bios, credentials, external profiles — also improve how AI engines cite your content.
