Guide

The complete technical SEO audit guide

A practical, step-by-step walkthrough of every technical SEO check that matters — what it is, why it affects rankings, and exactly how to fix it. The same process we run on 10+ production sites.

What is a technical SEO audit?

A systematic review of the technical factors that decide whether search engines can crawl, index and rank your pages — and a prioritised list of what to fix.

Technical SEO is the foundation everything else sits on. You can have the best content in your niche, but if a page is blocked by robots.txt, carries a stray noindex, canonicalises to the wrong URL, or takes eight seconds to load, it won't rank. A technical audit finds those barriers. This guide walks through the audit in the order we actually run it — fixing root causes first so you don't chase symptoms.

The 8-step technical SEO audit

Work top to bottom. Each step has a free tool to check it instantly.

Step 1 — Crawlability: can search engines reach your pages?

Start with robots.txt. A single over-broad Disallow: can block more than you intend, and blocking a URL stops Google re-crawling it (so it can't even see a noindex you add later). Confirm your important paths aren't blocked and that your sitemap is declared. Then check for broken internal links and redirect chains that waste crawl budget. Broken Link Checker →

Step 2 — Indexability: are your pages allowed in the index?

A page is indexable only if it has no noindex tag or X-Robots-Tag header, isn't blocked in robots.txt, has a self-referencing canonical, and returns HTTP 200. The classic outage is a stray noindex on a shared template that ships to production and deindexes a whole section. Search Console's Pages report is the source of truth for what's indexed and why the rest isn't. Indexability Checker →

Step 3 — Canonicalisation: which URL is the master?

Every indexable page should self-reference its canonical. The common bug is a canonical pointing to a redirect or 404 (Google ignores it and picks its own), or every paginated page canonicalising to page 1 (which deindexes the rest). Keep canonical, hreflang and internal links all pointing at the same URL. Canonical Checker →

Step 4 — Sitemaps: are you guiding crawlers correctly?

Your XML sitemap should contain only canonical, indexable, 200-status URLs — no redirects, 404s or noindex pages. Declare it in robots.txt and submit it in Search Console. For large sites, use a sitemap index pointing to child sitemaps (50,000 URLs max each). Also flag indexable pages missing from the sitemap — they may be under-crawled. Sitemap Validator →

Step 5 — Redirects: are you leaking authority?

Collapse redirect chains (A→B→C should be A→C) and fix redirects that land on 404s. Use 301s for permanent moves so backlink equity transfers, and update internal links to point at the final URL directly. After HTTP→HTTPS or trailing-slash migrations, re-check that canonicals and sitemaps reference the new URLs.

Step 6 — On-page meta: titles, descriptions, headings

Each page needs a unique, descriptive title (~50–60 chars), a meta description under ~160 chars, one H1, and a sane heading hierarchy. These are quick wins that affect click-through and clarity. Meta Tag Checker →

Step 7 — Structured data & international

Validate any JSON-LD — invalid schema can throw errors in Search Console and block rich results (a frequent one is aggregateRating on an unsupported type). If you're multilingual, hreflang is the most error-prone area: it needs reciprocal return tags, a self-reference, valid language codes, and targets that return 200. Hreflang Checker →

Step 8 — Core Web Vitals & page speed

Speed is a ranking factor and the first thing users feel. Optimise LCP (compress the hero image, preload it, cut TTFB), CLS (set image dimensions, reserve space, font-display: swap), and INP (break up long JS tasks, defer non-critical scripts). Test your key templates on mobile, not just the homepage. PageSpeed Test →

Audit, fix, re-crawl, repeat

A technical audit isn't a one-time task. Run it, fix root causes, re-crawl to confirm (and to catch issues the first fix revealed), then re-audit after every deploy that touches templates, redirects or the sitemap. Tracking your health score over time turns SEO from guesswork into a measurable trend.

Technical SEO audit FAQ

How long does a technical SEO audit take?

For a small-to-medium site, a few hours — the crawl runs in minutes; reviewing and prioritising issues is the bulk of it. Large sites take longer; re-audits after fixes are much faster.

How often should you audit?

After any deploy touching templates, redirects, canonicals or the sitemap, and at least monthly. Regressions are introduced by changes, so auditing right after a release catches them early.

What tools do you need?

Google Search Console and PageSpeed Insights (both free) plus a crawler. Screaming Frog's free tier does 500 URLs; Kalenux SEO Audit crawls your whole site against 80+ checks plus PageSpeed for one-time pricing.

Does technical SEO guarantee rankings?

No — it removes the barriers stopping pages from ranking. It ensures your content can be crawled, indexed and loaded fast. Content quality and relevance still decide where you rank among the pages that can compete.

Run the audit instead of just reading about it

Free to start. Crawl your whole site against every check in this guide.

Start my free audit