SEO audit report: what you should get and how to read it

Someone sold you an SEO audit. You paid, waited three weeks and got back a ninety-page SEO audit report full of colourful charts, a list of 340 issues and a final section titled ‘Recommendations’.

You opened it twice.

And still, nothing: six months later your traffic hasn’t moved an inch, because nobody told you which of those 340 issues actually move the needle and which ones are noise that no crawler is ever going to penalise.

An SEO audit isn’t measured by how thick the report is. It’s measured by how many decisions you can make on the following Monday morning.

What an SEO audit looks at, and what it doesn’t

It’s worth fencing off the ground first, because the word ‘audit’ gets used for very different things. If what you need is the full picture of the site, with performance, content and security in the same report, that’s the general check-up that covers four angles at once, which goes by the name of website audit.

The SEO audit is just one of those four angles. It answers a single question: why search engines aren’t sending you the traffic your content deserves.

To answer it, the audit works through four layers:

• Crawling and indexing. This covers which URLs Google sees, which ones it ignores and which ones it has decided not to index. It’s where the noindex tags inherited from the old site turn up, along with the blocks in robots.txt and the orphan pages nobody links to.
• Architecture and canonicalisation. This is about how your URLs are grouped, which version Google treats as the right one and where two of your own pages are competing for the same query.
• Content and intent. The question here is whether what you publish answers what people actually type, because a flawless page answering an intent nobody has will never rank.
• Technical experience signals. Structured data, semantic hierarchy and the performance thresholds all sit here, and I go through those in detail in measuring and fixing Core Web Vitals.

The link profile gets reviewed as context rather than as a layer of its own: which domains link to you, whether you’re dragging toxic links behind you from old campaigns and which pages pile up authority without putting it to any use. For a small business it’s rarely the main reason you don’t rank, and the architecture is to blame far more often.

What an SEO audit doesn’t do is redesign your site, write your copy or promise you a ranking. Anyone selling you an audit with a guaranteed first position is selling you something else entirely.

Why your website doesn’t show up on Google

It’s almost always one of four causes, and each one lives in a different layer of the audit. The page isn’t indexed because something is stopping it (a forgotten noindex, an inherited robots.txt). Google has picked another of your URLs for that search, so the one you want is competing against itself. The content answers a search that nobody makes. Or the page is so slow that it loses out to a worse but faster one. The audit tells you which of the four it is before you touch anything.

The six deliverables you should demand

If you’re wondering what an SEO audit report should include, the answer fits neatly in a table, and it’s the difference between a report and a proper piece of work. Ask for these six in writing before you sign anything:

The fifth is the one that gets forgotten most often and the one that’s worth the most. Without a snapshot of the starting point, there’s no honest way of knowing whether the work did its job.

How to read an SEO audit report without drowning

A list of 340 issues isn’t a plan. It’s raw material.

Reading it usefully means putting every single point through two filters and keeping only whatever survives both of them.

The two questions that sort out any list

First question: does this affect a page that can actually bring me business? A crawl error on a 2019 tag page with zero visits isn’t a priority, however red the traffic light next to it happens to be.

Second question: how much does it cost to fix? Some issues are solved with one line of code and others mean rebuilding the architecture. They don’t weigh the same, even if the report lists them one after the other.

With those two answers, the 340 issues turn into three blocks: what gets fixed this week, what goes into the plan for the quarter and what gets documented and left alone. Carrying out those blocks is hands-on technical SEO work, not copywriting or design, so it’s worth knowing who’s going to do it before you commission the report.

‘An audit that doesn’t end in a task list with an owner and a date is a diagnosis without treatment: you know what you’ve got and you’re just as ill as before.’

The questions to ask whoever’s selling it to you

These five separate someone who’s going to work on your site from someone who’s going to hand you the export from a tool:

1. Tools and judgement. What do you crawl the site with, and what do you do when the tool and the Search Console data contradict each other?
2. Real scope. How many URLs go into the analysis, and what happens if my site turns out to have more than you planned for?
3. Prioritisation. Will you give me the issues ranked by impact on the business or by technical severity?
4. Execution. Who applies the fixes, and which part of the work is going to need my developer?
5. Verification. When do we measure again, and which metric do we use to decide whether it worked?

If the answer to the third question is ‘by severity’, you already know what kind of report you’re going to get.

An audit isn’t an MOT

The comparison is tempting and it’s wrong. You pass an MOT, they hand you the certificate and you forget about the whole thing for a year.

A website changes every week: you publish, install and edit, and sooner or later someone uploads a 4 MB image. That’s why an audit marks a starting point rather than a certificate, and why it makes sense to look again every six or twelve months instead of every time someone panics.

Between one review and the next, what holds the results in place is keeping the site up to date and not letting technical debt pile up all over again.

No reports that never get acted on.

When an audit isn’t what you need

There are two situations where spending your money on an audit is premature.

The first is when your site was handed over recently, built on a template in a rush and with no thought-out structure. There’s nothing to optimise there, because the problem isn’t the errors but the foundations, and it’s the same story as sites launched without a planned structure and what a cheap template really saves you.

The second is when you don’t have any content. If your site is five service pages and none of them answers what your customer is searching for, the report will tell you everything is fine and you’ll still have no traffic. Before auditing, that’s the moment to publish, and it’s worth knowing what a well-planned project costs so you don’t repeat the cycle.

In every other case, and especially if your site has been running for years and has passed through several pairs of hands, the diagnosis pays for itself. You’ll see that in the before and after of projects with their numbers on show.

I hand over the inventory, the cannibalisation map and the prioritised list with estimated hours for every point. If I can’t explain in one sentence what an issue is costing you, it doesn’t make the list. It’s all laid out in my website audit service.