An SEO audit is an inspection. Somebody examines your website against a set of standards and reports what they found, ranked by how much it matters. Google’s guidance adds the part most audits miss: it should give you realistic estimates of the improvement available and of the work required to get it. An audit diagnoses. It doesn’t fix anything, and it can’t promise a ranking.
In plain English
An audit is a roadworthiness inspection for a car.
Somebody puts it on the ramp, goes through a defined list, and hands you a sheet: these three things are dangerous, these five need attention soon, these are cosmetic. They don’t repair anything. Handing you the sheet is the job.
And passing the inspection doesn’t make the car fast. It means nothing is broken. Those are different questions, and the second one isn’t what an inspection answers.
Why this matters for your site
Two expectations get set wrongly at the point of sale, and both cost money.
The first is that the audit includes the fixing. Usually it doesn’t, and businesses discover this after receiving a 60-page document they now need somebody else to implement.
The second is that fixing everything in the audit produces growth. Sometimes it does. Often it removes obstacles that weren’t what was holding the site back. A site can be technically immaculate and still lose to a competitor who simply answers the question better.
Knowing what an audit is for keeps both expectations in the right place.
What a good audit contains
Findings, with severity. What’s wrong, and how much it matters. A flat list with no ranking pushes the hard decision back onto you.
Expected improvement. What fixing this is likely to be worth. Honest here means ranges and reasoning, not promises.
Effort. Roughly what fixing it involves and who has to do it. A finding that takes a developer two days is a different proposition from one that takes a rebuild.
Evidence. What the finding is based on, so somebody can check it. Google’s guidance on evaluating recommendations is direct: ask whether they cite official Google documentation as supporting evidence.
What’s fine. A good auditor tells you what doesn’t need attention. An audit with no clean bill of health anywhere is usually padded.
What it typically covers
- Technical health. Whether Google can reach, read, and store the pages. This is technical SEO, and it’s usually where the severe findings are.
- Indexing. Which pages are actually in Google’s index, and whether that matches what you intended.
- Structure. How pages connect, and whether important pages are easy to reach.
- Content. Whether pages match what people are searching for, and whether pages compete with each other.
- Links and reputation. What the site has earned, and whether anything in the profile is a liability.
- Competitors. What the sites currently outranking you are doing that you aren’t.
Scope varies, and it should. An audit of a 40-page services site and an audit of a 200,000-page store are different jobs.
What an audit is not
Not a fix. Implementation is separate, and usually needs your developers.
Not a diagnosis of a specific event. If traffic fell on a particular date, that’s an analysis. An audit may find the cause incidentally, which is a slower and more expensive route to it.
Not a guarantee. Google’s guidance is unambiguous here: if a provider guarantees that their changes will put you first in search results, find someone else.
Not a tool report. Running a crawler produces a list of technical issues in an afternoon. That’s an input to an audit, not an audit. Google notes that third-party tools have no access to its internal ranking data and that their recommendations should be checked against official guidance before you act on them.
What this looks like in practice
Two audits of the same site.
The first is 140 findings exported from a crawling tool, sorted alphabetically. Most are real. Around a hundred are trivial. Nothing indicates which three matter or what they’re worth.
The second is 22 findings. The first three are marked as accounting for most of the available improvement, with what each is likely to be worth and what implementing it requires. The remaining 19 are listed as low priority with a note saying so.
The second one took longer to produce and is a fraction of the length. It’s also the only one somebody can act on next week.
What people usually get wrong
“The audit found 140 problems, we’re in trouble.” Volume of findings isn’t severity. Most sites generate long lists.
“We implemented the audit, so traffic should rise.” Removing obstacles helps when obstacles were the problem. If the issue is that competitors serve the searcher better, technical work won’t change it.
“We need an audit every quarter.” Sites don’t deteriorate that fast, unless something is being changed constantly. Monitoring catches drift more cheaply than repeat inspection.
“They need full access to everything.” At the audit stage, read access is enough. Google recommends specifically not granting write access to Search Console at that point.
What you can do about it
Ask what the deliverable looks like before buying. Ask to see a redacted example.
Ask whether prioritization and effort estimates are included. If they aren’t, you’re buying half the work.
Ask who implements the findings, and confirm that in writing.
Grant read access first. Write access can come later if implementation is agreed.
Treat any guarantee of rankings as a reason to stop.
Compare what you’re offered against that list, including ours: an SEO audit is one of the things we do, and the scope is written out rather than described in a call.
Google’s guidance on hiring an SEO covers the access question and the guarantee question directly, and is worth reading before you sign anything.
Words you will hear
Crawl. Software walking through your site page by page to collect information.
Severity. How much a given finding actually matters.
Remediation. The work of fixing what an audit found.
Benchmark. A comparison against competitors or against your own earlier state.
False positive. A tool flagging something as a problem when it isn’t one.
For how an audit differs from an analysis and a strategy, see Audit, analysis and strategy. For scope, deliverable and baseline, see the same entry.
