The Complete Technical SEO Checklist (2026 Edition)

Most SEO advice is about content and links. But on almost every site audit I run, the biggest wins are hiding in the plumbing: pages blocked by accident, duplicate URLs splitting signals, redirect chains, slow templates, or a sitemap full of URLs that shouldn’t exist. This technical SEO checklist is the exact order I work through on real projects.

You don’t need to be a developer for most of it. You do need access to Google Search Console, your CMS, and a crawler such as Screaming Frog (free up to 500 URLs).

1. Crawlability: can search engines reach your pages?#

Before anything ranks, Googlebot has to discover and fetch it. Crawl problems are silent — nothing looks broken to visitors — which is why they survive for months.

• Check robots.txt at yourdomain.com/robots.txt. Make sure you’re not disallowing important folders, CSS or JavaScript. See the robots.txt entry for safe patterns.
• Confirm “Discourage search engines” is off in WordPress (Settings → Reading). It’s the most common self-inflicted wound after a site launch.
• Submit an XML sitemap in Search Console and keep it clean: only canonical, indexable, 200-status URLs. More in the XML sitemap guide.
• Find orphan pages — URLs in your sitemap that no internal link points to. Crawl the site, export the URL list, and compare it with the sitemap.
• Check server response: a crawl should return mostly 200s, a few intentional 301s, and almost no 4xx/5xx errors.

2. Indexing: are the right pages in Google’s index?#

Crawled doesn’t mean indexed. Open Search Console → Indexing → Pages and read the “Why pages aren’t indexed” table carefully. Some reasons are fine (redirects, intentional noindex); others are red flags.

Also check that you are not indexing low-value pages: internal search results, tag archives with one post, thin author pages and attachment pages. Every useless URL in the index dilutes how Google judges your site’s overall quality. The indexing and thin content entries go deeper.

3. Canonicals and duplicate content#

Duplicate URLs split ranking signals. The same product or post can easily exist at several addresses: with and without www, with tracking parameters, with a trailing slash, or under several category paths.

• Pick one version of your domain (https, with or without www) and 301-redirect all others to it.
• Every indexable page should have a self-referencing canonical tag. Read the canonical tag entry for edge cases.
• Don’t canonicalise paginated pages (page 2, 3…) to page 1 — they contain different content.
• Strip tracking parameters (utm_*, fbclid) from internal links; they should only ever appear on external campaign links.

4. Site architecture and internal linking#

A good structure helps both users and crawlers find your best content quickly. As a rule of thumb, every important page should be reachable within three clicks of the homepage.

1. Group content into topic hubs. A hub page (e.g. “Technical SEO”) links to every detailed guide in that topic, and each guide links back.
2. Use descriptive anchor text. “technical SEO checklist” tells Google far more than “click here”. See anchor text.
3. Add breadcrumbs with BreadcrumbList schema — they reinforce hierarchy and often appear in search results.
4. Fix broken internal links and links that point to redirects; update them to the final URL.

I’ve written a full playbook on this: Internal Linking Strategy: Topic Clusters That Compound.

5. Redirects and status codes#

• Use 301 redirects for permanent moves. Avoid chains (A → B → C); point A straight to C. More in 301 redirect.
• When you delete content, redirect it to the most relevant live page — not blindly to the homepage.
• Return a real 404 (or 410) for pages that are gone with no replacement, and make the 404 page helpful with search and popular links.
• Monitor 5xx server errors; frequent errors make Google crawl less.

6. Page speed and Core Web Vitals#

Core Web Vitals measure real-user experience. They are part of Google’s page experience signals — not a magic ranking lever, but a tie-breaker that also directly affects conversions.

These thresholds are measured at the 75th percentile of real visits. Check the Core Web Vitals report in Search Console (field data) and use PageSpeed Insights to diagnose individual templates. If you run WordPress, follow my step-by-step guide: Core Web Vitals on WordPress.

7. Mobile-first essentials#

Google indexes the mobile version of your site. Whatever is missing on mobile is effectively missing for SEO.

• The same main content, headings, structured data and internal links exist on mobile and desktop.
• Tap targets are at least ~44 px and text is readable without zooming.
• No intrusive interstitials (full-screen pop-ups) covering content on arrival.
• Images are responsive (srcset) and lazy-loaded below the fold — but never lazy-load the hero image.

8. Structured data#

Schema markup helps search engines understand entities on your page — who wrote it, what it’s about, which organisation is behind it. Prioritise schema that matches visible content:

• Article / BlogPosting for posts, with author, dates and image.
• BreadcrumbList for navigation trails.
• Organization or Person on the homepage/about page, with sameAs links to social profiles.
• Product, LocalBusiness or Event where they genuinely apply.

Validate with Google’s Rich Results Test and the Schema.org validator. Read more in structured data.

9. HTTPS, security and hygiene#

• The whole site loads on HTTPS with no mixed-content warnings.
• HTTP and non-preferred hostnames 301 to the preferred HTTPS URL.
• Core, theme and plugins are updated; unused plugins removed. Hacked sites lose rankings fast.
• Check Search Console’s Security & Manual Actions report.

10. International and multilingual (if relevant)#

If you serve multiple languages or countries, implement hreflang with return tags on every version, and avoid automatically redirecting users based on IP — let them choose.

How often should you run this checklist?#

Run the full audit when you launch, redesign or migrate a site, and at least twice a year after that. Weekly, spend ten minutes in Search Console scanning the Pages, Core Web Vitals and Manual Actions reports. Most disasters are visible there days before traffic drops.