A technical SEO audit is a structured review of everything that affects whether search engines can crawl, render, index, and serve your site, ending in a prioritised list of what to fix. That second half is the part that separates a real audit from an expensive PDF, and it's worth understanding before you commission one, whether from me via my SEO audit service or from anyone else.
The territory a technical audit covers
A proper technical audit works through five layers, in order, because each gates the next.
Crawlability. Can search engines reach everything that matters? Robots.txt, the sitemap, internal linking, and on larger sites, where the crawl budget actually goes. The auditor should be looking at server logs or crawl stats for sizeable sites, not just running a desktop crawler and exporting the result.
Rendering. Does the page a crawler sees match the page a user sees? On JavaScript-heavy sites this is where rankings quietly go to die, and it's the layer automated tools check least well.
Indexation. What's actually in Google's index versus what should be? Missing money pages, indexed junk, canonical tags doing the opposite of what was intended. If you want the concept groundwork first, I've explained what technical SEO is in plain terms separately.
Architecture. Whether the site's structure concentrates authority on the pages that earn money, or dissipates it across pages that don't. This is the most judgement-heavy layer and the one where audits differ most in quality.
Performance. Core Web Vitals from field data, template by template, with causes named rather than scores recited.
Alongside those five, expect structured data, redirects, HTTPS, and mobile behaviour. The full working list is in the checklist I use, which is effectively this post's contents page expanded.
What the deliverable should look like
The output of a good technical audit is a prioritised roadmap, and the priority is the product. Every finding should carry three things: what's wrong, what fixing it is worth (in plain language, not a severity colour), and what fixing it costs in effort. Sorted by that ratio. A developer should be able to pick up any item and act on it without a clarifying meeting.
What you should not accept: a health score with no plan, a hundred findings with equal weight, screenshots of tool outputs standing in for analysis, or "issues" that are really the tool's opinions (word counts, text-to-HTML ratios) rather than things that affect rankings.
What a good audit deliberately leaves out
The mark of an experienced auditor is the confidence to say "this is technically imperfect and does not matter for you". Every site has hundreds of measurable imperfections; most affect nothing. An audit that flags them all is transferring the prioritisation work to you, which is the job you were paying to have done. When I finish an audit, findings that wouldn't measurably improve anything get cut before delivery, and the roadmap is shorter and better for it.
Who needs one, and when
Three situations reliably justify a technical audit: organic traffic has stalled or dropped without an obvious cause; a migration, redesign, or replatform is coming (audit before, verify after); or SEO spend is ramping up and you want to know the foundations will carry it. Outside those, a small brochure site with stable traffic probably needs an hour of sense-checking, not a full audit, and an honest consultant will say so.
Technical SEO audit FAQs
What's the difference between a technical SEO audit and a full SEO audit?
A technical audit covers the machinery: crawling, rendering, indexing, architecture, speed. A full audit adds content and intent analysis (do your pages match what people search for?) and competitive context. My audits cover all three, because technical findings without content context are half a diagnosis.
How much does a technical SEO audit cost?
It scales with the size and complexity of the site, and with how much of the work is judgement versus collection. Be wary at the cheap end: automated crawls cost pennies to produce, and that's usually what £200 buys.
Can I do a technical audit myself?
You can get a long way with Search Console and a crawler, and my checklist is the working order I'd follow. What's hard to self-serve is the prioritisation: knowing which of your hundred findings are the three that matter.
How long does a technical audit take?
Typically one to three weeks depending on site size, most of it analysis rather than crawling. Anyone offering same-day turnaround is selling you the export button.
Want a hand with any of this?
Tell me what you're working on and what you're trying to achieve, and I'll give you an honest view of whether I can help and what it would take.
Get in touch