Great content cannot rank if search engines cannot reach it, understand it or trust the version they find. A technical SEO audit checklist gives you a structured way to find those problems before you spend more on content or links.

This checklist is the same structure we use when reviewing websites for clients. It is grouped by area and ends with a simple way to prioritise what you find.

Tools you need for a technical SEO audit

You do not need an expensive stack to start:

  • Google Search Console for indexing status, crawl stats, Core Web Vitals and manual actions.
  • Bing Webmaster Tools for a second view of crawling and indexing.
  • A website crawler (desktop or cloud-based site audit tools) to map URLs, status codes, titles, canonicals and links.
  • PageSpeed Insights for lab and field performance data.
  • Google's Rich Results Test and the Schema Markup Validator for structured data.

Google's own guidance in Search Central remains the best reference for what search engines expect.

1. Crawlability checks

Crawlability is whether search engine bots can discover and fetch your pages.

  1. Is robots.txt reachable and free of accidental blocks such as "Disallow: /"?
  2. Does robots.txt reference your XML sitemap?
  3. Does the XML sitemap contain only canonical, indexable URLs that return 200?
  4. Are important pages linked from other pages with normal HTML links?
  5. Are there orphan pages that receive no internal links?
  6. Is crawl depth reasonable, with key pages reachable within three or four clicks?
  7. Are there infinite URL spaces from filters, calendars or search results?
  8. Do server logs or crawl stats show frequent errors or slow responses?

2. Indexability checks

Indexability is whether fetched pages are eligible to appear in results.

  1. Do important pages accidentally carry "noindex" in meta robots or the X-Robots-Tag header?
  2. Does every page have a self-referencing or correct canonical tag?
  3. Are duplicate versions (HTTP/HTTPS, www/non-www, trailing slashes, parameters) consolidated?
  4. Does the Page Indexing report in Search Console show valuable pages as "Crawled, currently not indexed"?
  5. Are thin, near-duplicate or auto-generated pages diluting the site?
  6. Do paginated archives remain crawlable and indexable where they help discovery?

Google explains canonical handling in its guide to consolidating duplicate URLs. Our article on keyword cannibalization covers the content side of duplication.

3. Rendering and JavaScript

  1. Does the main content appear in the HTML response, or only after JavaScript runs?
  2. Does the URL Inspection tool in Search Console show the rendered page correctly?
  3. Are links generated as real anchor elements with href attributes?
  4. Are important resources (CSS, JS) blocked by robots.txt?

Client-side rendered marketing pages are a frequent problem on SaaS and app websites. Server-side rendering or static generation is usually safer for pages you want to rank.

4. Site architecture and internal linking

  1. Is the navigation logical, with clear categories and hubs?
  2. Do URLs follow a readable, consistent structure?
  3. Do breadcrumbs reflect the hierarchy and use BreadcrumbList markup?
  4. Do important pages receive the most internal links?
  5. Do anchor texts describe the destination?

A strong structure helps both users and crawlers. Our internal linking strategy guide explains how to improve it.

5. Page speed and Core Web Vitals

  1. Do key templates pass Core Web Vitals in field data (LCP, INP, CLS)?
  2. Are images compressed, sized correctly and served in modern formats?
  3. Are render-blocking scripts and unused CSS minimised?
  4. Are third-party scripts such as chat widgets and tag managers controlled?
  5. Is server response time consistently fast?

See our Core Web Vitals optimization guide for detailed fixes.

6. Mobile, HTTPS and security

  1. Is the site fully usable on mobile, with readable text and tappable buttons?
  2. Is HTTPS enforced site-wide with valid certificates?
  3. Are there mixed-content warnings?
  4. Are security headers in place, and is the site free of malware or hacked content warnings?

7. Redirects and status codes

  1. Do retired URLs redirect with 301s to the closest relevant page?
  2. Are there redirect chains or loops?
  3. Do broken internal links point to 404 pages?
  4. Does the 404 page return a real 404 status rather than a 200 "soft 404"?

8. Structured data and metadata

  1. Is Organization, Article, Product, Breadcrumb or other relevant structured data valid and consistent with visible content?
  2. Does every indexable page have a unique, descriptive title and meta description?
  3. Are Open Graph tags present for sharing?
  4. Is there one clear H1 per page with a logical heading hierarchy?

Our schema markup guide and on-page SEO checklist cover these in detail.

Using the technical SEO audit checklist to prioritise fixes

Not every issue deserves immediate attention. Score each finding on impact and effort:

Prioritising technical SEO audit findings
PriorityTypical issuesAction
CriticalSite-wide noindex, robots.txt blocks, broken HTTPS, server errorsFix immediately
HighKey pages not indexed, wrong canonicals, major redirect chains, failing Core Web Vitals on main templatesFix within weeks
MediumMissing structured data, orphan pages, duplicate titlesSchedule into the roadmap
LowMinor image optimisation, cosmetic metadata issuesBatch with other work

Tie each issue to the pages and revenue it affects. A slow blog archive matters less than a slow pricing or demo page.

How often should you run a technical SEO audit?

Run a full audit at least twice a year, and always before and after a redesign, platform change or domain move. In between, monitor Search Console weekly for indexing drops, crawl errors and Core Web Vitals changes. Our website maintenance checklist includes these monitoring tasks.

Turning the audit into results

An audit only creates value when fixes ship. Assign each issue an owner, estimate effort, and confirm the fix with a recrawl. Report the outcome in terms leadership understands: more indexed priority pages, faster key templates, recovered rankings for important queries.

If you want a second pair of eyes, request our free SEO and AI visibility audit or explore our SEO services.

Online stores have additional technical challenges such as faceted navigation; see our ecommerce SEO guide.

Frequently asked questions

How long does a technical SEO audit take?
A small business site can be audited in a few days. Large sites with thousands of URLs, complex JavaScript or multiple languages can take several weeks, especially when log files are analysed.
What is the difference between a technical SEO audit and an SEO audit?
A technical SEO audit focuses on crawling, indexing, rendering, speed and site structure. A full SEO audit also reviews content quality, keyword targeting, backlinks and competitor positioning.
Can I do a technical SEO audit myself?
Yes, for many sites. Google Search Console, a crawler and PageSpeed Insights cover most checks. Complex sites, migrations and JavaScript-heavy platforms often benefit from specialist help.
Which technical SEO issues matter most?
Issues that block crawling or indexing of important pages, such as robots.txt blocks, accidental noindex tags, wrong canonicals and server errors, matter most because they can remove pages from search entirely.
How often should a website be audited?
Run a full audit at least twice a year and before and after any redesign or migration, with weekly monitoring in Search Console between audits.