What Is a Technical SEO Audit?

What Should a Technical SEO Audit Actually Examine?

Most documents called technical audits are tool exports. Five hundred rows, colour-coded, no order of importance, and no statement of what is actually costing money.

A real audit does the opposite. It narrows hundreds of observations down to the handful of problems that explain the site's current visibility.

This guide explains what a proper audit examines, what the output should look like, and how to judge whether one was worth paying for.

Key takeaways

An audit is diagnosis, not a list — priority and impact are the deliverable.
Indexation and rendering come before speed and markup.
Findings should be grouped by template, because fixes are template-level.
Every recommendation needs an owner: SEO, developer or content.
A good audit states what to ignore as well as what to fix.
Re-crawl after implementation to confirm the fix actually landed.

What does a technical SEO audit examine?

Audit scope, in order of examination
Stage	What is checked	Why it comes here
Crawl access	robots.txt, status codes, discoverability	Nothing downstream works without it
Indexation	noindex, canonicals, coverage by template	Determines eligibility
Rendering	Rendered HTML versus source	Reveals invisible content
Architecture	Click depth, internal links, orphans	Decides which pages get attention
URLs	Duplicates, parameters, redirect chains	Prevents self-competition
Structured data	Validity, accuracy, coverage	Confirms meaning to machines
Mobile and speed	Real-device rendering, Core Web Vitals	Protects conversion
Measurement	Search Console, analytics, conversions	Makes improvement provable

The order matters. Reporting a slow page that is not indexed wastes everyone's time.

How is an audit actually carried out?

Start with Search Console, not a crawler

Search Console shows what Google has actually done with your site: what it indexed, excluded and why. A crawler only shows what it could find.

Group the page indexing report by template. Patterns appear immediately.

Crawl the site and compare

A crawl reveals the URLs that exist, including ones nobody intended to publish. Compare that set with the pages you expect to have.

Gaps in either direction — missing pages, or unexpected ones — are the most productive findings.

Inspect rendering per template

Test one page per template with URL Inspection and read the rendered HTML. This is where JavaScript problems surface.

One check per template is enough; templates fail together.

Test on a real phone

Emulators miss the things customers notice: overflow, tap targets, forms that will not submit, and genuine load time on mobile data.

Five minutes on a real device outperforms a page of synthetic scores.

What should the output look like?

A usable audit is short and decisive. If the recipient cannot start work from it, it has failed.

A summary naming the two or three issues holding the site back.
Each finding stated as observation, effect, fix and owner.
Priority based on commercial impact, not severity colour codes.
Explicit "do not bother" items, with reasons.
A verification step for each fix.

Example. One audit we ran replaced a 340-row spreadsheet with four findings. Fixing the first — a canonical error on the service template — recovered visibility across eleven pages within a month.

What are the signs of a weak audit?

An unfiltered tool export presented as analysis.
Every issue marked critical, so nothing is prioritised.
No mention of indexation or rendering.
Performance scores treated as the headline finding.
No named owner for any recommendation.
No baseline recorded, so improvement cannot be demonstrated.

Ask one question of any audit: which finding, if fixed first, will change results, and how will we know? A weak audit cannot answer it.

How often should you audit?

Full audits are not a monthly activity. Monitoring is.

A sensible cadence
Activity	Frequency
Search Console coverage review	Monthly
Rendering check on key templates	Quarterly
Full technical audit	Annually
Pre and post-launch audit	Every migration or redesign
Redirect and canonical verification	After any URL change

The reasons to run one, and the cost of not doing so, are covered in why perform a technical SEO audit.

Can you audit your own site?

You can get most of the way with free tools and an hour of attention.

Search Console page indexing, filtered by page type.
URL Inspection on one page per template.
A site: query to spot duplicates and stray URLs.
Your phone, on mobile data, for each key template.
Rich results validation where structured data is used.

Pair this with the SEO website checklist, or read the technical SEO fundamentals first if the terms are new.

Frequently asked questions

How long does a technical SEO audit take?+

For a small site, one to two days including reporting. Large or complex sites take one to two weeks, mostly because rendering and URL handling need checking per template.

What does a technical audit cost?+

It scales with site size and platform complexity. Judge value by whether the output is a prioritised diagnosis with owners, not by page count or number of issues listed.

Do I need an audit if my rankings are fine?+

Before a migration, yes. Otherwise monthly indexation monitoring is usually sufficient until something changes on the site or in results.

Who implements the fixes?+

Usually developers, with SEO providing specifications and verification. Agreeing that split before the audit is delivered is what stops findings sitting in a backlog.

Should an audit cover content?+

A technical audit should stay technical, and say where content is the cause instead. Mixing both usually produces a document nobody can action.

What a good audit gives you

A technical audit should end an argument, not start a backlog. Two or three clear findings, in priority order, each with an owner and a way to verify the fix.

If the last audit you received was a spreadsheet nobody acted on, the problem was the audit rather than your team.

Audits increasingly cover machine readability too, which sits inside our AI SEO services. If you would like a short, decisive audit, get in touch.