Technical SEO Checklist 2026: 40 Things to Check
A practical technical SEO checklist for crawlability, site speed, structured data, mobile UX, and security, with fixes prioritized by technical risk.

Technical SEO removes barriers that prevent search engines and users from accessing, rendering, understanding, and navigating a site. It does not guarantee rankings, but crawl blocks, unintended noindex directives, broken canonicals, rendering failures, and poor page experience can limit otherwise useful content.
What is technical SEO
Technical SEO covers the website systems that affect how search engines crawl, index, render, and understand pages. It includes site structure, performance, HTTPS, mobile compatibility, and machine-readable signals such as sitemaps, structured data, and canonical tags. AEO readiness is a related content and entity layer: technical access makes extraction possible, while clear answers and evidence make a page more useful as a source.
Crawlability and indexability checklist
If Google can't find or index your pages, nothing else matters. Check these first.
Site speed checklist
Google recommends good Core Web Vitals for search success and user experience, while warning that strong scores alone do not guarantee top rankings. Measure both field and lab data with Google PageSpeed Insights.
Mobile and UX checklist
Google predominantly indexes sites with the mobile version of the content. Important content, links, metadata, and structured data should therefore remain equivalent and usable on mobile.
Structured data checklist
Structured data (JSON-LD schema) helps Google and other systems understand eligible pages and can support rich results when the page meets the relevant guidelines. It also makes pages easier for answer engines to parse, but it does not guarantee citations in Google AI features, Perplexity, or ChatGPT. Refer to Schema.org for the full type reference, and see our full SEO audit guide for how to implement and test each schema type.
Security checklist
Security belongs in a responsible technical audit because it protects users and affects browser behavior. HTTPS is a documented page-experience signal. Other headers such as CSP, HSTS, and X-Frame-Options are valuable security controls, but Google does not document them as individual ranking factors.
How to prioritise technical SEO fixes
Not all technical issues have equal impact. Prioritize crawl and index blockers first, then broken rendering, canonicals, internal navigation, and HTTPS. Address page experience and supported structured data based on affected templates and business value. VisRank shows which audited category contains the detected gaps; it does not predict the ranking gain from each fix. Run a free technical SEO audit
Key takeaways
- Fix crawl and index issues before any content or link work - they're blocking everything else
- Core Web Vitals support page experience, but good scores alone do not guarantee rankings
- Google uses the mobile version for indexing, so equivalent mobile content and functionality matter
- Structured data can clarify eligible content but is not required for or a guarantee of AI Overview citations
- Security headers are important protections even when they are not documented ranking factors
- Run this checklist after every major site change, not just quarterly
- Automated audits catch what manual checks miss - use both for full coverage
Check your website's SEO & AEO score
Free visibility audit - no signup required.
Scan my website for free