Home›Checklists›Technical SEO Checklist

Free SEO checklist · 14 sections · 28 checks

Technical SEO Checklist

A technical SEO checklist helps you find the crawlability, indexability, redirect, canonical, status code, XML sitemap, robots.txt, structured data, and JavaScript rendering problems that stop search engines and AI crawlers from discovering and ranking your pages.

28 Checks14 High priority14 SectionsPDF · Word · Excel Formats
Download checklist

SiteAuditLint checklist library

What this checklist covers

A technical SEO checklist helps you find the crawlability, indexability, redirect, canonical, status code, XML sitemap, robots.txt, structured data, and JavaScript rendering problems that stop search engines and AI crawlers from discovering and ranking your pages.

It is organized into 14 sections: Crawlability, Status Codes, Redirects, Indexability, Robots.txt, XML Sitemaps, HTTPS and Security, Duplicate URLs, Internal Linking, JavaScript Rendering, Structured Data, Images, International and AI Crawler Accessibility. Each check lists exactly what to verify and a priority, so you can work through the highest impact items first.

For background on the concepts behind these checks, see Technical SEO course, Technical SEO checklist for search and AI, Technical SEO audit.

Testing method: For testing SEO signals sent in response headers across app, server and CDN, see HTTP header SEO testing.

Who it is for:

SEOsdevelopersagencies

Download the technical seo checklist

Use the interactive version below, or download it to share with your team, attach to tickets, or work through offline.

Technical SEO Checklist

Work through each check

0 of 28 checks complete

Crawlability

Status Codes

Redirects

Indexability

Robots.txt

XML Sitemaps

HTTPS and Security

Duplicate URLs

Internal Linking

JavaScript Rendering

Structured Data

Images

International

AI Crawler Accessibility

Progress is saved in this browser only.

Detailed explanations

Each section below explains what to check, why it matters, the problems you will usually find, how to fix them, and how to confirm the fix.

Crawlability

What to check:

  • Crawl the full site. Run a full crawl and confirm all important URLs are discovered.
  • Check crawl depth. Key pages are reachable within 3 clicks of the homepage.
  • Check crawlable links. Navigation uses <a href> links, not JS click handlers.

Why it matters: Search engines can only rank what they can discover. If crawlers cannot follow links to a URL, that page will rarely be indexed, no matter how good its content is. Crawl depth also signals importance: pages buried many clicks deep get crawled less often.

Common problems:

  • Navigation built with JavaScript click handlers instead of anchor links
  • Important pages only reachable through internal search or forms
  • Pagination or filters creating near infinite URL spaces that waste crawl budget
  • Key pages sitting five or more clicks from the homepage

How to fix it: Use standard <a href> links for all navigation, add contextual links from high authority pages to deep content, and constrain parameter and filter URLs so crawlers spend time on pages that matter.

How to verify: Run a full crawl, compare discovered URLs with your sitemap and analytics landing pages, and review the crawl depth report for any important URL deeper than three clicks.

Learn more: Crawling explained, What is a website crawler, Crawlability vs indexability, Deep page issue.

How SiteAuditLint helps: it checks crawlability across every crawled URL instead of one page at a time and lists exactly which URLs are affected.

Status Codes

What to check:

  • Check HTTP status codes. Important URLs return 200; no unexpected 3xx, 4xx or 5xx.
  • Find soft 404s. Thin or empty pages do not return 200 as fake content.
  • Check server errors. No 5xx responses on templates or sitemap URLs.

Why it matters: HTTP status codes tell crawlers whether a URL is live, moved, missing, or broken. A 200 response is required for indexing. Unexpected 4xx and 5xx responses remove pages from search results and waste crawl budget, while soft 404s confuse search engines about which pages hold real content.

Common problems:

  • Internal links pointing to 404 pages after content is deleted
  • Soft 404s, where empty or error pages return 200
  • Intermittent 5xx errors on heavy templates or under load
  • Single page apps returning 200 for routes that do not exist

How to fix it: Restore or redirect removed URLs that still receive links, return a true 404 or 410 for content that is gone, and investigate server logs for the cause of any 5xx responses.

How to verify: Crawl the site and filter by status code. Every URL in the sitemap and main navigation should return 200. Recheck flagged URLs individually with a header checker.

Learn more: Status codes lesson, HTTP status codes and SEO, HTTP 4xx issue, HTTP 5xx issue.

How SiteAuditLint helps: it checks status codes across every crawled URL instead of one page at a time and lists exactly which URLs are affected.

Redirects

What to check:

  • Check redirect chains. Redirects resolve in a single hop.
  • Check redirect loops. No URL redirects back to itself.
  • Check redirect type. Permanent moves use 301 or 308, not 302.

Why it matters: Redirects pass users and ranking signals from an old URL to a new one. Each extra hop adds latency and increases the chance that signals are lost or crawlers give up. Temporary redirects used for permanent moves can keep the old URL indexed.

Common problems:

  • Redirect chains of three or more hops left behind by repeated migrations
  • Redirect loops that make a URL unreachable
  • 302 redirects used for permanent URL changes
  • Internal links still pointing at redirecting URLs

How to fix it: Point every redirect directly at its final destination with a 301 or 308, break any loops, and update internal links so they reference the final URL rather than relying on the redirect.

How to verify: Crawl with redirect following enabled and export the redirect chains report. Each redirecting URL should resolve in one hop to a URL returning 200.

Learn more: Redirects lesson, Testing redirects, How to find and fix redirect problems, Redirect chain issue.

How SiteAuditLint helps: it checks redirects across every crawled URL instead of one page at a time and lists exactly which URLs are affected.

Indexability

On this checklist: check meta robots noindex; check X-Robots-Tag; check canonical tags. Explained in full in the Indexability Checklist.

Robots.txt

On this checklist: check robots.txt availability; check disallow rules. Explained in full in the Robots.txt Checklist.

XML Sitemaps

What to check:

  • Check sitemap validity. Sitemap loads, validates and is referenced in robots.txt.
  • Check sitemap URLs. Sitemap lists only canonical, indexable, 200 URLs.

Why it matters: An XML sitemap is a list of URLs you want search engines to find and index. It helps discovery of new and deep content and acts as a canonical signal. A sitemap full of redirects, errors, or noindexed URLs weakens trust in that signal.

Common problems:

  • Sitemaps containing redirected, 404, or noindexed URLs
  • Non canonical URL variants listed instead of the canonical version
  • Sitemap not referenced in robots.txt or submitted in Search Console
  • Stale sitemaps that are not regenerated on publish

How to fix it: Generate the sitemap automatically from indexable canonical URLs only, keep lastmod accurate, reference it in robots.txt, and submit it in Search Console.

How to verify: Crawl the sitemap URL list on its own. Every entry should return 200, be indexable, and be self canonical.

Learn more: XML sitemaps lesson, XML sitemap errors and fixes, Sitemap non-200 issue, Noindex URL in sitemap issue.

How SiteAuditLint helps: it checks xml sitemaps across every crawled URL instead of one page at a time and lists exactly which URLs are affected.

HTTPS and Security

What to check:

  • Check HTTPS. All URLs serve over HTTPS and HTTP redirects to HTTPS.
  • Check mixed content. No HTTP assets load on HTTPS pages.

Why it matters: HTTPS is a confirmed ranking signal and a browser requirement for trust. Mixed content and inconsistent protocols create duplicate URLs and security warnings that hurt both users and crawlers.

Common problems:

  • HTTP versions that do not redirect to HTTPS
  • Mixed content loading images or scripts over HTTP
  • Expired or mismatched SSL certificates
  • Internal links and canonicals still using http://

How to fix it: Force HTTPS with a single 301 from HTTP, update hardcoded internal URLs, and enable HSTS once everything is stable.

How to verify: Request the HTTP version of key URLs and confirm a single redirect to HTTPS, then crawl for any http:// resources on HTTPS pages.

Learn more: HTTPS pages linking to HTTP, Mixed content issue, Not HTTPS issue, Missing HSTS issue.

How SiteAuditLint helps: it checks https and security across every crawled URL instead of one page at a time and lists exactly which URLs are affected.

Duplicate URLs

What to check:

  • Check URL variants. Trailing slash, case, www and parameter variants consolidate.
  • Check duplicate content. Near duplicate pages are canonicalized or merged.

Why it matters: Duplicate and near duplicate URLs split ranking signals and make search engines choose a version for you. They often come from technical variants rather than copied content.

Common problems:

  • Trailing slash and non slash versions both returning 200
  • Uppercase and lowercase URL variants
  • Tracking and sort parameters creating indexable copies
  • Printer friendly or session ID versions of pages

How to fix it: Pick one URL format, redirect other variants to it, and canonicalize parameter versions that must remain accessible.

How to verify: Crawl and group pages by identical or near identical content hashes and titles, then confirm each group resolves to one indexable URL.

Learn more: Duplicate content SEO, Duplicate content checker, Near duplicate issue, URL parameters issue.

How SiteAuditLint helps: it checks duplicate urls across every crawled URL instead of one page at a time and lists exactly which URLs are affected.

Internal Linking

On this checklist: check broken internal links; check orphan pages. Explained in full in the On-Page SEO Checklist.

JavaScript Rendering

On this checklist: compare source vs rendered HTML. Explained in full in the JavaScript SEO Checklist.

Structured Data

On this checklist: validate structured data. Explained in full in the On-Page SEO Checklist.

Images

On this checklist: check image alt text; check broken images. Explained in full in the On-Page SEO Checklist.

International

On this checklist: check hreflang. Explained in full in the International SEO / Hreflang Checklist.

AI Crawler Accessibility

What to check:

  • Check AI crawler access. GPTBot, ClaudeBot, PerplexityBot and similar are allowed or blocked intentionally.

Why it matters: Search engines can only rank what they can discover. See the earlier section on this topic for common problems.

How to verify: Run a full crawl, compare discovered URLs with your sitemap and analytics landing pages, and review the crawl depth report for any important URL deeper than three clicks.

How SiteAuditLint helps: it checks ai crawler accessibility across every crawled URL instead of one page at a time and lists exactly which URLs are affected.

Common mistakes

Checking only the homepage instead of every template

Assuming a 200 status code means a page can be indexed

Forgetting the X-Robots-Tag HTTP header when checking noindex

Testing robots.txt without testing real URLs against it

Assuming the XML sitemap only contains indexable canonical URLs

Ignoring redirect chains left behind by past migrations

Reviewing source HTML without comparing it to rendered HTML

When to run the checklist

  • Before launching a new website
  • After a redesign or CMS change
  • Before and after a website migration
  • After a major deployment
  • When organic traffic or indexed pages suddenly drop
  • As a quarterly technical SEO audit

How to verify fixes

Save a baseline crawl before you change anything. Fix high-priority and template-level issues first, since one template fix resolves many URLs, then re-crawl with the same start URL and settings and compare the two audits with audit comparison. Finally, confirm important pages in Search Console with URL Inspection. See how to prioritize audit findings.

SiteAuditLint workflow

Most checks in this list run automatically in a SiteAuditLint crawl. Use audit comparison to diff crawls and scheduled audits to monitor for regressions.

All SEO checklists

See the full checklist library, with a guide to choosing the right checklist for each job.