What Is a Technical SEO Audit?

A technical SEO audit is a structured review of everything that affects whether search engines can find, crawl, render, understand and rank your pages — separately from the question of whether your content is any good.

That distinction matters. Content problems and technical problems need different people and different fixes, and conflating them is why so many SEO engagements produce activity without results.

What it covers

Crawling and indexing

Can search engines reach your pages, and are the right ones in the index?

This includes robots.txt directives, meta robots tags, accidental noindex on templates, blocked CSS or JavaScript, crawl depth, orphan pages with no internal links, and the gap between how many pages you have and how many are indexed. A large gap in either direction is a finding.

Duplication and canonicalisation

Is each piece of content available at exactly one URL? Common failures: the same page on www and non-www, HTTP and HTTPS, with and without a trailing slash, with tracking parameters, and — on stores — every combination of filters generating a new indexable URL.

Rendering

Does the content exist in the HTML a crawler receives, or only after JavaScript executes? This is one of the most common serious problems on modern sites and one of the least visible, because everything looks fine in a browser.

Site architecture

How pages relate to each other: hierarchy, internal linking, breadcrumbs, anchor text, and whether important pages are reachable in a few clicks. Architecture determines which pages accumulate authority, and it’s frequently the highest-impact category.

Performance

Core Web Vitals from field data, not just a lab score: LCP, INP and CLS, traced back to specific causes — images, JavaScript weight, font loading, layout shift.

Metadata and on-page structure

Titles, descriptions, heading hierarchy, image alt text — checked at scale to find duplicates, missing values and templated text repeated across hundreds of pages.

Structured data

Whether it’s present, valid, and — the part tools don’t check — actually true. Marking up reviews you don’t have is worse than no markup at all.

Content and intent

Which pages target which searches, where two pages compete for the same query, where the intent is mismatched, and where an obvious commercial query has no page at all.

What you should get at the end

A useful audit deliverable has three properties:

Prioritised. Ranked by likely impact, not grouped by tool category. A crawler will flag 400 issues; perhaps twelve matter. Sorting them is the actual expertise.

Specific. Every finding names the affected URLs and shows the evidence. "Improve internal linking" is not a finding. "These 34 service pages have no inbound internal links except from the sitemap" is.

Actionable. Each item states what to change and roughly what it takes. Ideally it distinguishes what a content editor can do from what needs a developer.

Plus a conversation. The value of an audit is in discussing trade-offs, not in receiving a file.

How to tell a real audit from a tool export

A tool export:

• lists everything, undifferentiated;
• uses the tool’s severity ratings rather than judgement about your business;
• flags things that don’t matter on your site;
• contains no reference to what you sell or who buys it.

A real audit:

• explains why each finding matters for you;
• includes things no crawler can detect, like intent mismatch or a competitor covering a topic you’ve ignored;
• says which findings to ignore, and why;
• states what it couldn’t determine and what access would be needed.

What it costs you to skip

Technical SEO is a threshold rather than a growth lever. Above it, more technical work has diminishing returns and content becomes the constraint. Below it, everything else you do is capped — you can publish excellent content into a site that can’t get it indexed.

Most business sites we look at are below the threshold in one or two specific ways, and the fixes are usually smaller than expected.

The part where audits usually stall

Many findings require development work: template changes, rendering behaviour, redirect logic, structured data implementation. That’s the point where reports go into a backlog and stay there.

It’s the reason we do both the analysis and the implementation. An audit whose recommendations never ship has cost you money and changed nothing.

If you want to know what’s actually holding your site back, send us the URL.