Technical SEO checklist (2026)
TL;DR
- Technical SEO makes sure engines can crawl, render and index your site.
- Priorities: crawl and indexing, rendering, speed and schema.
- Without a technical base, the best content doesn't perform.
- Fix by impact, not by an endless list.
Technical SEO is the layer that makes a site eligible: if engines can't crawl, render and index it, nothing else matters. Here's the essential, in order of impact.
What to check
| Area | What to confirm |
|---|---|
| Crawl and indexing | robots.txt, sitemap, Search Console coverage |
| Rendering | Content visible without fragile JS |
| Core Web Vitals | LCP, INP and CLS in "good" |
| Structured data | Valid schema for your content types |
| Canonicals | Clear preferred version, no conflicts |
It's the starting point of any technical SEO engagement.
Fix in this order - impact first
The mistake I see most is teams working a 300-item audit top to bottom. Sequence by consequence instead: if a page isn't crawled and indexed, nothing downstream matters, so that's always first. Then rendering - can Google see the content without executing fragile JavaScript? Then speed and Core Web Vitals, then structured data. Ten fixes in the right order beat a hundred in the wrong one.
Rendering: the trap that hides good content
Google renders pages, but it doesn't guarantee it renders yours perfectly or promptly. On JavaScript-heavy sites, critical content and links can be invisible in the initial HTML and arrive too late - so Google indexes a shell. The test is simple: view the rendered HTML (Search Console's URL Inspection, or "view source" vs the live DOM). If your main content or internal links aren't in the server response, that's a priority-one fix, not a nice-to-have.
The prioritized checklist
- Crawl & indexing: robots.txt allows key paths, XML sitemap is clean (200s only), Search Console coverage has no surprises.
- Rendering: main content and links present in the HTML, not dependent on client-side JS.
- Canonicals: self-referencing and consistent, with no conflict against noindex.
- Core Web Vitals: LCP, INP and CLS in 'good' on field data.
- Structured data: valid schema that matches the visible content.
- Internal linking: important pages are a few clicks deep and well-linked.
- HTTPS, redirects (301, no chains) and a sane 404.
How to verify - mostly free
You don't need an expensive stack to start. Search Console shows coverage, rendering and field Core Web Vitals; PageSpeed Insights diagnoses performance; the Rich Results Test validates schema. A desktop crawler (Screaming Frog) then catches the long tail. Confirm each fix in the field, not just the lab - a green lab score that real users never feel is a vanity metric.
Key data
| Pages with no organic traffic | 96,6% |
|---|---|
| Pages with 1–10 visits/month | 1,9% |
| Pages with no backlinks | 66,3% |
Ahrefs study from 2023 (~14B pages).
Sources: Ahrefs — Search Traffic Study · Botify
Common mistakes and how to do it right
Nearly two decades of this taught me that brilliant content can't save a site Google can't read. By order of pain:
| Avoid | Do |
|---|---|
| ✗ Leaving key pages on noindex after a deploy | ✓ Auditing meta robots and coverage in Search Console after each release |
| ✗ Trusting JavaScript to always render | ✓ Checking the rendered HTML; critical content shouldn't depend on fragile JS |
| ✗ Pointing canonicals to the home by mistake | ✓ A correct self-referencing canonical, no conflicts with noindex |
| ✗ Leaving heavy images for the end | ✓ Handling LCP and image weight from the start |
| ✗ Having 404 or noindex URLs in the sitemap | ✓ A clean sitemap, indexable 200 URLs only |
Tools I use and recommend
- Screaming Frog SEO SpiderDesktop crawler for deep technical and on-page audits.
- PageSpeed InsightsCore Web Vitals and performance diagnostics (free, Google).
- Rich Results TestValidate structured data (free, Google).
- Google Search ConsoleOrganic performance, coverage and field Core Web Vitals.
- SEO Pro ExtensionOn-page and technical checks at a glance (extension).
Sources
Frequently asked questions
Where do I start with technical SEO?
With crawl and indexing: if pages aren't crawled and indexed, nothing else counts. See service →
Do I need expensive tools?
Search Console and PageSpeed Insights, both free, cover much of the initial diagnosis. Core Web Vitals →