The complete technical SEO checklist for 2026

00 The 2026 technical SEO baseline

This is the checklist we'd hand to a developer about to launch a new site, or to an SEO inheriting an audit no one's run in eighteen months. Fifty checks across ten categories, written for people who actually have to ship the fixes — not just identify them.

Each item below tells you what to check, why it matters in 2026, and the single fix that resolves the most common failure mode. Print it, hand it to your team, work top-to-bottom. Or run it as a Smart SEO Audit and let our crawler do the legwork.

01 Crawling & indexing

If a page can't be crawled, nothing else you do matters. Start here.

• robots.txt is reachable at /robots.txt and returns a 200 status. A 404 or 500 here is treated as "no rules" and may cause unpredictable crawling.
• robots.txt doesn't accidentally block CSS or JS. Googlebot needs them to render your pages.
• XML sitemap is submitted in Google Search Console and referenced from robots.txt with a Sitemap: directive.
• Sitemap contains only canonical, indexable URLs — no redirects, no 404s, no noindex pages.
• No accidental noindex on pages that should rank. Check both meta robots and X-Robots-Tag HTTP headers.
• No accidental Disallow: / in robots.txt on production. (Sounds obvious. Happens at least once a year somewhere.)
• Crawl budget isn't being burned on faceted URLs, calendars, internal search results, or login pages. Block or noindex these as appropriate.

02 Rendering

If your site relies heavily on JavaScript, this section is your highest-leverage area.

• Critical content renders without JavaScript, or via a server-rendered/static fallback. Inspect with View Source — not just DevTools' rendered DOM.
• Lazy-loaded content uses native loading="lazy" rather than IntersectionObserver hacks that hide content from crawlers.
• No infinite scroll without paginated fallbacks. Crawlers can't trigger scroll events.
• Hydration doesn't change the page's main content — what Google sees on first crawl should match what users see post-hydration.
• Test with the URL Inspection tool in Google Search Console for any page where rendering matters.

03 On-page elements

• Every page has a unique, descriptive title tag under ~60 characters / 580 pixels.
• Every page has a meta description under ~160 characters that earns the click.
• Exactly one H1 per page that matches user intent.
• Logical heading hierarchy (H1 → H2 → H3) with no skipped levels in a single section.
• All images have descriptive alt attributes (decorative images can use alt="").

04 URL structure

• URLs are short, readable and lowercase. Hyphens between words, no underscores.
• No session IDs, tracking params or filter state in canonical URLs.
• Trailing slash policy is consistent across the site (either always or never — pick one).
• HTTP redirects to HTTPS with a 301, not a 302.
• www and non-www variants resolve to one canonical version.

05 Canonical & duplicates

• Every indexable page has a self-referential canonical tag.
• Pagination uses self-canonical, not rel="canonical" back to page 1 (which Google now treats as a hint, not a directive).
• UTM-tagged URLs canonicalize to the clean version.
• Faceted URLs either canonicalize or carry noindex — never leave them open as duplicates.

06 Performance & Core Web Vitals

• LCP under 2.5 seconds at the 75th percentile on mobile.
• INP under 200 milliseconds at the 75th percentile.
• CLS under 0.1.
• HTTP/2 or HTTP/3 enabled — both are 2026 baseline expectations.
• Brotli compression enabled on text assets.
• Images served as WebP or AVIF, with appropriate srcset for responsive sizes.
• LCP image is preloaded with <link rel="preload">, not lazy-loaded.

07 Structured data

• Schema.org markup is implemented in JSON-LD (Google's preferred format).
• Organization or LocalBusiness schema on the homepage.
• Article, Product or Recipe schema as appropriate to your content.
• Breadcrumb schema on every non-homepage URL.
• All schema validates in Schema Markup Validator with no errors.

08 International SEO

• hreflang annotations on every alternate URL, in both directions (return tags).
• x-default hreflang for the locale-fallback URL.
• Language attribute on the html tag: lang="en", lang="de", etc.
• No mixed content — translated pages don't pull in original-language strings or untranslated UI.

09 Security & protocol

• Site is fully HTTPS, with valid certificate from a trusted CA.
• HSTS header is set with a long max-age.
• No mixed content warnings — every asset loads over HTTPS.
• 404 page returns a 404 status, not a 200 with "page not found" content (a "soft 404").

10 Monitoring & ongoing

• Google Search Console connected to all properties (incl. domain property).
• Bing Webmaster Tools connected.
• Server-side log analysis in place for Googlebot crawl behaviour, at least quarterly.
• Automated SEO regression checks on every deploy. Smart SEO Audit's scheduled audits + alert channels handle this for you.

Most "SEO problems" are technical bugs that no one bothered to monitor for. Set the alarms, then go work on content.

? Frequently asked questions

What is technical SEO?

Technical SEO is the set of site-level and page-level optimisations that help search engines crawl, render and index your site correctly — things like site speed and Core Web Vitals, crawlability and robots.txt, indexation and canonicals, structured data, HTTPS, mobile-friendliness, and a clean XML sitemap. It's the foundation that lets your content and links actually perform.

How often should I run a technical SEO audit?

Run a full audit at least quarterly, and after any significant change — a redesign, migration, CMS update or new deployment, since these are when regressions slip in. Better still, schedule automatic re-audits so a broken canonical, a noindex left on after launch, or a protocol regression is caught within hours instead of months.

What technical SEO issues matter most?

The highest-impact problems are ones that block indexing or rendering entirely: accidental noindex tags, robots.txt blocking important resources, canonical mistakes that drop pages from the index, broken HTTPS, and severe Core Web Vitals failures. Fix the issues that stop pages being found before optimising finer on-page details.

→ Related guides

Keep going — these companion guides go deeper on related topics.