A technical SEO audit tells you whether search engines can reach and understand your site. A full SEO audit tells you what to do about it, and in what order.
Quick answer
A technical SEO audit checks the infrastructure: crawling, indexation, redirects, canonicals, sitemaps, rendering, structured data and speed. A full SEO audit includes all of that, then adds content, search demand, internal linking, competitors and the commercial priorities that decide what gets fixed first.
If there is a clear technical symptom, such as a traffic drop after a migration or pages that will not index, start with the technical audit. If the site is technically reasonable but organic enquiries are flat, you need the wider one.
What a technical SEO audit covers
The question it answers is: can Google find, crawl, render, index and understand the pages that matter?
- Crawlability: robots.txt, internal links, crawl traps, buried or orphaned pages
- Indexation: what is indexed, what should be, and the noindex and canonical signals behind it
- Status codes: redirects, chains, 404s and soft 404s
- XML sitemaps: do they list only canonical, indexable pages that return 200?
- Rendering: whether important content depends on JavaScript
- Structured data, hreflang and page experience signals
The output is usually a list of faults and fixes, grouped by template. It is the right tool when something has broken, or before something big changes, such as a site migration.
What a full SEO audit adds
The question it answers is: why is this site not getting the organic enquiries it should, and what should happen first?
- Search demand and intent: which queries matter, and whether the right page answers each one
- Content performance: thin, outdated, duplicated or competing pages
- Site architecture and internal linking
- On-page basics: titles, descriptions, headings and how the result looks in search
- Sector-specific checks for local, ecommerce or publishing sites
- Competitors and authority signals
- A prioritised action plan with owners, effort and expected impact
The technical findings still sit inside it. The difference is that they are ranked against everything else, so a canonical fix and a content rewrite are not competing in a pile of two hundred "issues".
Two examples from my own work
For a UK plastic storage retailer, the problems were foundational. The homepage had eight H1 tags, no page had a meta description, and faceted navigation had no canonical tags, which left around 130 near-duplicate pages indexed. A technical audit and a structured fix programme was enough: organic clicks rose 197% at 90 days with no new content. The full figures are in the ecommerce case study.
A UK software agency was different. Its content and authority were strong, and one service page had 124,000 monthly impressions but only a 0.1% click-through rate. The cause was several technical problems compounding, including broken hreflang on 422 pages, no structured data and an average Largest Contentful Paint of about seven seconds. Spotting that pattern needed the wider view of content, snippets and architecture alongside the technical crawl. See the software agency case study.
How to choose
- Traffic dropped after a migration, redesign or platform change: technical audit first
- Search Console shows pages not indexing or coverage errors: technical audit
- You are about to migrate or restructure URLs: technical audit, plus a redirect map
- The site is technically healthy but enquiries are flat: full audit
- You do not know where to start, or need priorities rather than a fault list: full audit
- You have a development team and need a backlog: technical audit, but ask for it to be prioritised
Warning signs of a weak audit
- It is a tool export with a cover page, and the tool's health score is presented as a finding
- Nothing is ranked by impact and effort
- There is no Search Console evidence behind the claims
- Recommendations name no pages or templates ("improve internal linking")
- No one has said who needs to do what
If that sounds familiar, why audit recommendations do not get implemented explains how to avoid it.
Where the Visibility Review fits
The Visibility Review is a full audit (see SEO audits for the offer) built around a decision: a crawl and indexation review, content performance, internal linking and architecture, and a prioritised action plan. If all you need is a technical check, for example before a launch, I scope that separately under Technical SEO.
To see what the output looks like first, there are sample outputs and a free first-look audit template you can run yourself.
FAQ
Is a technical SEO audit part of a full SEO audit?
Yes. A full audit includes the technical review, then adds content, linking, competitors and prioritisation.
Can I start with a technical audit and add the rest later?
Yes, and it is often sensible when technical problems are blocking everything else. Fix the blockers first, then widen the review once the foundations are sound.
How often should a site be audited?
After any major change such as a migration, redesign or platform move, and with a lighter review at regular intervals. How often depends on how fast the site changes.
When to get support
If you are not sure which one you need, send me your website and the problem you are trying to solve, and I will tell you which fits. For a decision-ready plan, start with the Visibility Review.