Guide
What an SEO audit finds, and what you get at the end
An SEO audit explains why a site ranks where it does and what holds it back. A real one reads your Search Console data next to a crawl of the site, checks setup, content and links, and ends with fixes in priority order, each tied to a page, a reason and a way to check it worked.
On this page
Part of my guide to Technical SEO checklist: what I check first on any site.
"SEO audit" can mean anything from a free automated report to a month of expert work. Both get called audits, and buyers often cannot tell them apart until the result arrives. This guide explains what a real audit covers, how it builds on the technical SEO checklist, and what you should have in your hands at the end.
If you are comparing audit offers, use this as the standard. Ask each seller which of these parts they cover, and what the final document looks like.
What to take from this
- A tool report lists warnings. An audit explains which ones matter for your site and why.
- The best audits start from your own Search Console data, not from a generic checklist.
- The deliverable is a priority list your developer and writer can act on, not a long PDF.
What an SEO audit is for
An audit answers one question: why does this site perform the way it does in search, and what should be done about it, in what order?
That question has three parts. The first is diagnosis: what is wrong, and what is working. The second is cause: why it is wrong, traced to a template, a setting, a page or a decision. The third is priority: which fixes will make the most difference for the least effort.
A list of problems without causes and priorities is not an audit. It is an inventory. Many sites have hundreds of minor warnings and two or three real problems, and the value of an audit is in telling those apart.
How an audit differs from a tool report
SEO tools can crawl a site and produce long reports: missing alt text, titles too long, pages with low word count, slow scripts. Those reports are useful starting points. They are not audits, for three reasons.
Tools do not know your goals. A tool flags a thin page whether it is your main service page or an old event from 2018. A person knows which one matters.
Tools do not read your search data. The most important evidence about a site sits in Search Console: which pages Google indexes, which searches bring impressions, where clicks fell. A tool crawling from outside cannot see any of that.
Tools do not trace causes. A tool sees fifty pages with duplicate titles. A person sees that they all come from one template setting and fixes it once.
A good audit uses tools for evidence and a person for judgement.
What a full audit covers
Search performance
The audit starts with Search Console. It looks at clicks, impressions and positions over at least a year, finds any sharp changes and their dates, and sees which pages and searches drive the site. This gives the rest of the audit its focus: the parts of the site that matter most, and any problems that already cost traffic.
Crawling and indexing
Next, can Google reach and index the pages that matter? The audit reviews robots.txt, server responses, the Pages report in Search Console, sitemaps, and how the site renders for Google. It compares how many pages the site has with how many Google indexes, and explains the gap.
Google's SEO starter guide describes the basics any site should meet. An audit checks your site against those and goes further.
Duplicates and site structure
The audit checks for duplicate URLs, canonical problems, parameter and filter pages, and redirect chains. It looks at how the site is organised: how deep important pages sit, how categories and services are linked, and whether the menu and internal links point Google to the right places.
Speed and mobile
The audit reviews Core Web Vitals from real visitor data where Google has it, and tests the main templates for speed and mobile layout. It separates problems that affect every page through a template from those that affect one page.
Structured data
It checks that the right schema types are used, that the data matches the visible page, and that there are no errors in Google's tests.
Content
The audit reads the main pages as a searcher would. Does each page target a clear search? Does it answer it well? Do several pages compete for the same search? Are there thin or outdated pages pulling the site down? The content side of an audit uses the same tests I describe in content checks in an audit.
Links
It reviews the backlink profile: who links to the site, whether any links look like spam or paid schemes, and whether there is a manual action. It also compares links with the competitors that rank above you. The method is in my backlink review guide.
Local and AI visibility
For local businesses, the audit includes the Business Profile, listings and location pages. For any business, it now includes a check of whether AI crawlers can access the site and how AI tools describe the business.
What you should get at the end
The deliverable matters as much as the work. A good audit ends with a document that a developer, a writer and an owner can each act on without a meeting.
It should contain:
- A short summary in plain words: what is wrong, what it costs you, what to do first.
- A priority list of fixes. Each fix names the pages or template affected, the evidence, what to change, who should do it, and how to check that it worked.
- Effort and impact for each fix, so you can plan the work.
- The evidence: screenshots and exports from Search Console and the crawl, so anyone can verify the findings.
- What is working, so nobody breaks it.
What you should not get is a hundred page PDF of tool output with no priorities. If the audit is longer than anyone will read, the important findings are hidden in it.
Red flags in an audit offer
Some audit offers are not worth the price, however low it is. Watch for these.
The audit arrives in an hour. No person can read a year of search data, crawl a site and think about causes in an hour. A fast audit is a tool export with a cover page.
It does not ask for Search Console access. An audit that never looks at Google's own data about your site is guessing.
Every finding has the same priority. If the audit lists two hundred problems and marks them all "high", nobody has decided what matters.
The fixes are generic. "Improve page speed", "add more content" and "build backlinks" are not fixes. A fix names the page, the change and the reason.
It ends with a sales pitch for a monthly package. A good audit can lead to ongoing work, but its findings should stand alone. You should be able to hand it to any developer or writer and get the work done.
It scores your site out of 100. Scores from tools are easy to produce and easy to game. They tell you little about why you rank where you do.
How audits find causes
A case shows why the cause matters more than the symptom. A business services firm had four regional pages competing for the same searches. A tool would flag the pages as similar. The audit traced Google switching between them in Search Console, recommended merging them into single intent pages, and paired that with schema and speed work. Comparing three months with the three months before, organic clicks rose by . The audit that found the cause explains the work and what the screenshot can and cannot show.
What an audit costs
Audit prices vary as widely as SEO prices in general. Free scans cost nothing and find surface problems. Manual audits by an experienced person cost more because they take days of reading. My own technical audit costs PKR 120,000 and takes 7 to 10 business days. How audit pricing fits with monthly SEO costs is in my guide to what SEO work costs.
When you need an audit
You need an audit when:
- Traffic fell and you do not know why.
- You are planning a redesign or migration.
- You have paid for SEO for months and cannot see what it did.
- You are about to start monthly SEO and want to know what to work on.
- You bought a site or a business and want to know what you have.
You probably do not need a full audit for a new site with ten pages. A checklist and a few hours with Search Console will do.
How to prepare for an audit
Give the auditor read access to Search Console and Analytics, a list of your main services or products, the dates of any redesign, migration or big change, and what you want from search: more calls, more orders, more of a particular kind of customer. The more context, the more focused the audit.
After the audit arrives, read the summary first, then book a short call to go through the top five fixes. Ask how each one will be checked once it is done. Those five fixes usually carry most of the value, and they are where you should spend your first weeks.
If you want a full audit with a priority list your team can act on, my full SEO audit service page lists exactly what I check and what you receive.
Questions people ask
How long does an SEO audit take?
A small business site can be audited in a few days. A store with thousands of products or a site with a long history usually takes one to two weeks, because the data takes longer to read.
What is the difference between a free SEO audit and a paid one?
A free audit is usually an automated scan of one page or a sample of pages. It is useful for spotting obvious problems. A paid audit adds a person reading your search data, the whole site and your market, and deciding what matters.
How often should a website be audited?
Once a year for most sites, and before and after any redesign or migration. Large sites that change daily benefit from lighter monthly checks between full audits.
What do I need to give for an SEO audit?
Read access to Google Search Console and Analytics, a list of your main services or products, any recent changes to the site, and what you want the site to achieve.
Muhammad Usman Ali, independent SEO consultant
I work alone from Pakpattan, Punjab, on technical SEO, local search, ecommerce structure and content clean ups. I write and check every post on this blog myself.
Last reviewed 3 November 2026. How I write and check these posts