Technical SEO Checklist 2026: 25 Checks for a Fast, Crawlable Site
A 25-point technical SEO checklist covering crawling, indexing, Core Web Vitals, mobile, schema, redirects and AI crawler access, with fixes.
Key takeaways
- Technical SEO ensures search engines and AI crawlers can find, render and index your pages.
- Start with Google Search Console's indexing and Core Web Vitals reports.
- Most issues fall into five areas: crawling, indexing, speed, structure and structured data.
- Prioritise fixes by impact; a single robots.txt mistake can outweigh dozens of minor issues.
- Re-audit after redesigns, migrations and major CMS updates.
How to use this checklist
Work through each section with Google Search Console, a crawler such as Screaming Frog or Sitebulb, and PageSpeed Insights. Mark each item pass, fail or not applicable, then fix failures in order of impact.
Crawling
- robots.txt doesn't block important pages or resources (CSS, JavaScript, images).
- AI crawlers are allowed unless you've chosen otherwise: GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended.
- XML sitemap exists, contains only indexable 200-status URLs and is submitted in Search Console.
- No orphan pages: every important page is linked internally.
- Crawl depth is shallow: key pages are reachable within three clicks of the homepage.
Indexing
- Search Console's Pages report shows no unexpected "Excluded" or "Not indexed" spikes.
- Canonical tags point to the preferred URL on every page.
- No accidental noindex tags on pages you want ranked.
- Duplicate content is consolidated: HTTP vs HTTPS, www vs non-www, trailing slashes, URL parameters.
- Thin or low-value pages (tag archives, empty categories) are improved, merged or noindexed.
Speed and page experience
- Core Web Vitals pass for mobile: LCP 2.5 s or less, INP 200 ms or less, CLS 0.1 or less.
- Images are compressed, sized correctly, lazy-loaded below the fold and served in modern formats.
- JavaScript and CSS are minimal; unused code is removed and non-critical scripts are deferred.
- Fonts load efficiently with
font-display: swapand limited weights. - Server response time (TTFB) is fast, helped by caching and a CDN.
See our deep dive on Core Web Vitals.
Site structure
- Clean, descriptive URLs using lowercase words and hyphens.
- Logical hierarchy with breadcrumbs reflecting it.
- Internal links use descriptive anchor text and point to key pages.
- No redirect chains or loops; old URLs 301-redirect directly to the final destination.
- No broken internal links (404s).
- Mobile-friendly layout with readable text and tappable buttons.
- HTTPS everywhere with no mixed content.
Structured data and metadata
- Unique title tags and meta descriptions on every indexable page.
- Valid schema markup: Organization, LocalBusiness, Service, Article, FAQPage, Product and BreadcrumbList as relevant. Test with Google's Rich Results Test. See our schema guide.
- Open Graph and Twitter Card tags for clean social sharing.
How to prioritise fixes
| Priority | Examples |
|---|---|
| Critical | Site-wide noindex, robots.txt blocking, broken HTTPS |
| High | Failing Core Web Vitals, duplicate content, redirect chains |
| Medium | Missing schema, orphan pages, thin archives |
| Low | Minor meta description length issues |
When to re-audit
Run a full audit at least twice a year and always after a redesign, migration, CMS change or traffic drop. Monitor Search Console weekly between audits.
Frequently asked questions
What is a technical SEO audit?
A review of the technical factors that affect how search engines crawl, render, index and rank your site, such as speed, structure, indexation and structured data.
How often should I do a technical SEO audit?
At least twice a year, and after any redesign, migration or significant traffic drop.
Which tools do I need?
Google Search Console, PageSpeed Insights and a site crawler cover most needs. Rich Results Test validates schema.
Does technical SEO affect AI search?
Yes. AI crawlers need accessible, fast HTML. Blocked crawlers or JavaScript-only content can keep you out of AI answers.
Can I fix technical SEO myself?
Many items, such as titles, images and sitemaps, are manageable. Server, JavaScript and migration issues usually need a developer or specialist.
Conclusion
Technical SEO is the foundation everything else stands on. Work through these 25 checks, fix critical issues first and keep monitoring. A fast, crawlable, well-structured site ranks more easily, converts better and is easier for AI to understand. Need help? Our technical SEO service can audit and fix it for you.
