An SEO audit is a structured review of why a website does or doesn’t earn search traffic, ending in a ranked list of fixes. If you’re wondering how to do an SEO audit properly, you set the goal first, collect 16 months of data, review five areas in a fixed order (technical, content, links, local and AI visibility), score every finding by impact and effort, then present a short plan someone will actually act on. That’s the whole process.
The order matters more than the tools. I’ve watched people spend days on a crawler export while the real problem sat in one robots.txt line, so this guide is about how I run an audit, not what to tick. The checks themselves live in my SEO audit checklist, and I’ll point you to the deeper guides as we go.
What Decides How to Do an SEO Audit on Your Site?
Every audit I run starts with one question: why are we doing this now? The answer changes where I look first, how deep I go and what I leave out. Four variables shape everything after that.
- The goal. A traffic drop, a growth plateau, a migration and a website purchase each need a different audit. I’ll cover each in the next section.
- The site type. A ten-page service site, a blog with 800 posts and a store with filters fail in different places.
- Local or not. If the business serves a town or region, the Google Business Profile becomes part of the audit. If it sells online only, skip it.
- Who fixes things. An owner with a page builder, an in-house developer and an agency need different reports. Write for the person who will do the work.
Get these four on paper before you open a tool. It takes ten minutes and saves days.
Step 1: Scope the Audit by Goal
Here’s the decision tree I use. Pick the row that matches your situation, and let it set the depth.
| If your goal is… | Start with | Go deep on | Go light on |
|---|---|---|---|
| Find a traffic drop’s cause | Date of the drop, update timeline, change log | The pages and queries that fell | Anything that held steady |
| Break a growth plateau | Query and page performance, competitor gaps | Content quality, internal links, authority | Technical items that already pass |
| Plan or check a migration | Full URL inventory, redirect map | Indexing, redirects, canonicals | Content rewrites (later) |
| Buy or sell a website | Manual actions, link profile, traffic history | Risk: spam, thin content, lost links | Cosmetic on-page fixes |
| Annual health check | Baseline numbers | Whatever the data flags | Nothing, but keep it short |
If traffic dropped, the audit is really a diagnosis. Don’t audit the whole site evenly. Find the date, check it against confirmed updates, and work outward from the pages that lost the most. My traffic drop diagnosis path covers the six checks I run first.
If traffic is flat, nothing is broken in the usual sense. The site is simply not good enough to beat the pages above it. So I spend most of the time on content, intent and authority, and very little on technical checks that pass.
If you’re migrating, audit twice. Once before launch, to build the redirect map and record the baseline, and once after, to confirm Google followed it. Google’s site move documentation says to keep redirects “for as long as possible, generally at least 1 year,” which is why I never let a client remove old redirects during cleanup.
If you’re buying a site, you’re auditing for risk, not growth. I check the Manual Actions report, the link profile and the traffic history first, and I ask the seller for Search Console access rather than screenshots. Screenshots can be cropped. Live access can’t.
Step 2: What Data Should You Collect Before Judging Anything?
Collect first. Judge later. When I mix the two, I end up chasing the first problem I see instead of the biggest one.
Here’s my standard data set. Most of it is free, and I map each free tool to the audit area it covers in 10 best free SEO audit tools.
- Search Console Performance data for 16 months. Google’s traffic drop debugging guide recommends the “Last 16 months” view so you can spot seasonal dips. Export pages and queries separately.
- Search Console Page indexing, Manual Actions and Security issues reports. Screenshots with dates.
- Google Analytics 4 key events. Which pages produce leads or sales, not just sessions.
- A full crawl. Any crawler works. Save the export with the date in the file name.
- Link data. The Search Console Links report at minimum.
- Google Business Profile data, for local businesses only.
- AI visibility data. The Generative AI performance report in Search Console shows impressions in AI Overviews, AI Mode and AI features in Discover, and Google rolled it out to all sites as of August 31, 2026. It shows impressions, not clicks.
- A change log. Every redesign, plugin swap, theme change and content push, with dates.
That last one is the item people skip. It’s also the one that solves the most mysteries. Honestly, half the “algorithm hits” I’m asked about turn out to line up with a theme update somebody forgot.
Step 3: Work Through the Five Areas in Order
Order matters because each area depends on the one before it. A brilliant article that Google can’t index earns nothing, and links pointing at a broken URL pass nothing. So I always go in this sequence, and I don’t skip ahead even when something later looks more interesting.
Technical: Can Google Reach and Render the Pages?
Start with indexing. Which important pages are indexed, which aren’t, and why? Then crawlability, canonicals, rendering, speed and structured data. For speed, Google’s “good” marks are an LCP within 2.5 seconds, an INP under 200 ms and a CLS under 0.1, and INP replaced FID in March 2024.
I won’t repeat the full process here. My technical SEO audit guide walks through it step by step, and the technical SEO checklist holds every check.
Content: Does Each Page Deserve to Rank?
This is where I spend the most time on most sites. I read the top pages myself. Does each one answer its query fast? Does it match what the searcher wants? Is there anything on it a competitor can’t copy?
Then I look at the page level basics with the on-page SEO checklist. After that, I sort the weak pages into keep, refresh, merge or remove. My content refresh strategy covers the update side, and content pruning covers removal.
Links: Do They Help or Put the Site at Risk?
On a clean site, this part is short. I look for linked URLs that now return a 404, a quick win with a 301 redirect, and for patterns that look bought. If the site has a manual action or a history of paid links, I switch to a full backlink audit and review every referring domain.
Local: Is the Business Visible in Its Area?
Skip this if you have no local customers. If you do, audit the profile before the site, because that’s where I usually find the biggest single fix for a local business. The full local audit, including how to do it for multiple locations, is in my local SEO checklist.
AI Visibility: Do AI Answers Mention or Cite You?
This area is new. It’s also mostly a check of the four above, because Google’s AI features documentation says there are no extra requirements to appear in AI Overviews or AI Mode. So I confirm robots.txt and snippet controls don’t block key pages, read the Generative AI report, and run a fixed set of prompts in the main AI assistants. My guide to tracking brand mentions in AI answers shows the manual method I use.
Step 4: How Do You Prioritize the Findings?
A finished audit often has 40 or 50 findings. Nobody can fix that many at once. So I put each finding on a simple impact and effort grid, and the grid decides the order of work.
| Low effort | High effort | |
|---|---|---|
| High impact | Do now (quick wins) | Plan now, schedule this quarter |
| Low impact | Batch into a cleanup sprint | Drop, or park for next year |
Impact means how many important pages a finding touches and how close those pages are to money. A noindex tag on the services template is high impact. A missing alt attribute on an old blog image isn’t.
Effort means who has to fix it, how long it takes and how risky the change is. Rewriting one title is low effort. Rebuilding faceted navigation is high. If you want a numeric score instead of a grid, my technical audit guide has a scoring formula and template.
My take? The “high impact, high effort” box is where audits go to die. Those items look scary, so they slide down the list every month. I give each one an owner and a start date in the report, even if the start date is two months out.
One more rule. If a finding blocks indexing or breaks tracking, it jumps the queue no matter what the grid says. You can’t measure any other fix without tracking, and you can’t rank a page Google can’t index.
Step 5: How Should You Present SEO Audit Findings?
An audit nobody reads is worth nothing. I’ve seen 120-page PDFs sit unopened in inboxes, so I write every report for the busiest person who has to approve the work.
Mine always has five parts, in this order.
- A one-page summary. The three to five findings that matter most, each with the business reason. “Your service pages aren’t indexed, so they can’t bring in leads” beats “indexing anomalies detected.”
- The prioritized plan. The grid above turned into a list: finding, owner, effort, target date.
- Evidence for each finding. A URL list, a screenshot or a short export. Without evidence, developers push back, and they’re right to.
- What I didn’t check, and why. Missing access, out-of-scope sections, data gaps.
- The baseline. Clicks, impressions, key events and indexed pages on the audit date, so the next report has something to compare against.
Split the plan by audience if more than one team is involved. The developer gets the technical tickets, the writer gets the content list and the owner gets the summary. For ongoing reporting after the audit, my monthly SEO report template picks up where the baseline leaves off.
What Changes the Process?
- A site with thousands of URLs. Sample by template rather than by page. If one product page has a problem, the template usually does, and fixing the template fixes them all.
- No Search Console access. You can still crawl and read pages, but you can’t see indexing or queries. I note it as a limit in the report rather than guessing.
- A manual action in the report. Stop the audit’s normal order. The manual action comes first, because no other fix matters until it’s resolved.
- A rollout in progress. If Google is mid-update, I wait. Rankings move around during a rollout, and a snapshot taken then can mislead you.
- A brand-new site. Most checks will be “not applicable.” Focus on tracking, indexing and a handful of strong pages.
How Often Should You Do an SEO Audit?
My default is one full audit a year and a light monthly look at the indexing and performance reports. That rhythm catches slow problems without repeating the same findings every few weeks.
Some events trigger a full audit straight away, whatever the calendar says.
| Trigger | Audit type |
|---|---|
| Traffic drop of more than a normal seasonal dip | Diagnosis audit, focused on what fell |
| Redesign, new theme or platform change | Pre-launch and post-launch audit |
| Domain or URL change | Migration audit with redirect map |
| Buying or selling a website | Risk audit |
| Growth stalled for 6 months | Content and authority audit |
Anything more often than quarterly usually means you’re auditing instead of fixing. The audit is the map. The work is what moves rankings.
When Is It Worth Getting Help?
If the site has thousands of URLs, a manual action, a migration on the calendar or a drop you can’t explain after the steps above, a second pair of eyes saves time. Small business owners doing it themselves should start with my DIY SEO audit for small business, which fits into an afternoon.
At Skyranko, a full audit is the first step of our complete SEO service, and the plan we hand over follows the same five steps you just read. That’s how to do an SEO audit the way I’d want one done on my own site. If you’d like a quick outside view first, request a free SEO audit and I’ll tell you which findings I’d fix first.
Frequently Asked Questions
How Long Does an SEO Audit Take?
It depends on site size and goal. A small service site can be audited in a day or two. A large store or a migration takes longer because of the URL inventory and template sampling. Collecting data usually takes as long as the analysis itself.
Can I Do an SEO Audit Myself?
Yes. Search Console, Google Analytics, PageSpeed Insights and a free crawler cover most of the work on a small site. The hard part isn’t the tools. It’s prioritizing honestly and fixing the high-effort items instead of only the easy ones.
What Is the Difference Between an SEO Audit and a Technical SEO Audit?
A technical SEO audit covers one area: crawling, indexing, rendering, speed and structured data. A full SEO audit adds content, links, local and AI visibility, then ranks findings across all five areas so you know what to fix first.
What Should an SEO Audit Report Include?
A one-page summary, a prioritized plan with owners, evidence for each finding, a note on what you couldn’t check and a baseline of the key numbers. If the report doesn’t tell someone what to do on Monday, it needs another pass.
Last updated: October 2026 by Mizanur Rahman
