Short answer: An SEO audit is a structured review of a website to find what stops it ranking and earning clicks: crawling and indexing problems, technical and speed issues, weak or duplicate content, on-page gaps and link problems. To perform one, set a goal, collect Search Console and analytics data, crawl the site, check each area against a checklist, then rank the fixes by impact and effort and turn them into a dated plan.
This guide is for business owners, marketers and junior SEOs who want to audit a site themselves or understand what a professional audit should include. You will get the areas to check, the free and paid tools for each, a step-by-step method, a checklist you can tick through, and a way to prioritise findings so the audit turns into results instead of a long PDF.
What an SEO audit is, and what it is not
An SEO audit compares a site against how search engines crawl, index and rank pages, and against what searchers need. It ends with a prioritised list of fixes. It is not a tool score. Automated crawlers flag hundreds of “issues”, many of which do not matter, and they cannot judge whether your content answers the query better than the competition. The value of an audit is in the judgement: which five problems are actually holding the site back.
Types of SEO audit
- Full site audit: technical, content, on-page and links. Best for a new engagement or once a year.
- Technical audit: crawling, indexing, rendering, speed, structured data. See how technical SEO works for the background.
- Content audit: every indexable page scored and given a keep, improve, merge or remove decision. My content audit guide covers this in detail.
- Traffic drop audit: focused on one question, why traffic fell. Start with the traffic drop checklist.
- Migration audit: before and after a redesign, domain change or platform move.
What an SEO audit covers
| Area | What to check | Free tools | Paid options |
|---|---|---|---|
| Crawling | robots.txt, XML sitemap, crawl depth, broken links, redirect chains | Search Console, Screaming Frog (up to 500 URLs) | Screaming Frog licence, Sitebulb, Semrush, Ahrefs |
| Indexing | Page indexing report, noindex, canonicals, duplicates, index bloat | Search Console, URL Inspection | Crawler comparison of indexable vs indexed |
| Rendering and speed | JavaScript content, Core Web Vitals, mobile layout | PageSpeed Insights, Search Console CWV report | DebugBear, Calibre |
| On-page | Titles, meta descriptions, headings, internal links, images, structured data | Crawler export, Rich Results Test | Crawler custom extraction |
| Content | Intent match, depth, duplication, thin pages, cannibalisation, E-E-A-T signals | Search Console queries, manual review | Semrush, Ahrefs content tools |
| Links | Referring domains, lost links, anchor patterns, links to 404s | Search Console Links report | Ahrefs, Semrush, Majestic |
| Local (if relevant) | Google Business Profile, NAP consistency, reviews, location pages | Business Profile dashboard | BrightLocal, Whitespark |
Rather have an expert do this for you?
Hand it over and get back to running your business.
How to perform an SEO audit, step by step
Step 1: Set the goal and scope
Write down the question the audit must answer: “Why did traffic fall in March?”, “What stops our service pages ranking in Lahore?” or “Is the site ready to scale content?” Decide which sections are in scope and which conversions matter. An audit without a goal produces a list; an audit with one produces a plan.
Step 2: Collect the data before you crawl
Export 16 months of Search Console performance data by page and query, the Page indexing report, and organic landing-page conversions from GA4. Note known events: redesigns, migrations, plugin changes, and Google updates. Line the traffic graph up against the dates on the Google algorithm updates timeline before assuming a technical cause.
Step 3: Crawl the site
Crawl with JavaScript rendering on if the site relies on it, and connect Search Console and GA4 to the crawler so each URL carries its clicks and impressions. Compare the number of indexable URLs in the crawl with the number in Search Console’s indexed count and the number in your sitemap. Big gaps between those three numbers are usually the first real finding.
Step 4: Check crawling and indexing
Review robots.txt for accidental blocks, then go through the Page indexing report. Google’s own help says you should not expect all URLs to be indexed, only canonical pages, so focus on important pages that are excluded, and on low-value URLs that are indexed. My guide to the Search Console coverage report explains each status. Index bloat, the second problem, usually comes from tags, filters and thin archives. Duplicate URL patterns are covered in my guide on avoiding duplicate content.
Step 5: Check technical health and speed
Look at redirect chains, 4xx and 5xx errors, HTTPS and mixed content, mobile rendering and Core Web Vitals field data. Fix broken internal links first; the free broken link checker finds them on a single page, and a crawler does the whole site. Test templates, not individual pages: one slow product template affects every product.
Step 6: Review on-page elements and content
Export titles, descriptions and H1s. Look for duplicates, missing values and titles that do not match what the page ranks for in Search Console. Then read the key pages as a searcher would. Does each important page answer its main query better than the top three results? Is there a named author, sources and first-hand detail where trust matters?
Step 7: Review links and competitors
Check referring domains over time, links pointing to pages that now 404 (easy wins with a redirect), and whether internal links point to your most important pages. Compare against two or three competitors who rank where you want to rank.
Step 8: Prioritise and write the plan
Score each finding for impact (how many important pages or how much traffic it affects) and effort (developer time, content time, approvals). Do high-impact, low-effort fixes first. Group the rest into a 30, 60 and 90-day plan with an owner for each item. My guide to prioritising audit findings includes a scoring template.
Worked example: how a findings list becomes a plan
On a typical small WooCommerce store audit, a crawl might return 40 issue types. In practice I group them like this. Fix this week: the staging site is indexed (high impact, low effort), the category template has no canonical and sort parameters are indexed (high, low), 30 internal links point to deleted products (medium, low). Fix this month: product descriptions copied from suppliers on the top 50 products (high, medium effort), images served as full-size PNGs on the product template (medium, medium). Plan for next quarter: no blog content supports category pages (medium, high). Ignore for now: missing alt text on decorative icons and “low word count” warnings on contact pages. Forty issues become three weeks of focused work, and the owner knows exactly why each item is on the list.
SEO audit checklist
- Goal written: one question the audit must answer, and the conversions that matter.
- Data exported: 16 months of Search Console data, Page indexing report and GA4 organic landing pages.
- Timeline marked: redesigns, migrations and Google updates lined up against the traffic graph.
- robots.txt checked: no important sections or resources blocked.
- Sitemap clean: lists only indexable, canonical 200 URLs.
- Indexing reviewed: important pages indexed; low-value URLs kept out.
- One site version: HTTP and www variants redirect to one HTTPS version in one hop.
- Errors fixed: no internal links to 404s or redirect chains.
- Speed checked: Core Web Vitals field data reviewed per template, mobile first.
- Rendering checked: main content and links present in the rendered HTML.
- Titles and descriptions: unique, accurate and matched to the queries each page ranks for.
- Content reviewed: thin, duplicate and cannibalising pages listed with a decision for each.
- Structured data valid: no errors in Search Console enhancement reports.
- Links reviewed: referring-domain trend, lost links and links to dead pages checked.
- Plan written: findings scored by impact and effort, with owners and dates.
Ticks are saved in your browser.
How often to audit, and how long it takes
For most small and medium sites, a full audit once a year and a lighter monthly check of Search Console is enough. Run an extra audit before and after any migration or redesign, after a sustained traffic drop, and before a big content push. A small brochure site can be audited in a day or two; a store or publisher with tens of thousands of URLs can take a few weeks, mostly in analysis and writing up, not crawling.
Mistakes I see in SEO audits
- Exporting a tool report and calling it an audit. A 200-page PDF of warnings with no priorities rarely gets implemented.
- Chasing tool scores. A “site health” score of 95 does not mean the site ranks well.
- Auditing pages, not templates. On CMS sites most problems live in a template and repeat across hundreds of URLs.
- Skipping the content read-through. Many sites are technically fine but simply less useful than the pages outranking them.
- Ignoring local and language specifics. On Pakistani sites I often find English-only pages targeting customers who search in Roman Urdu, or one generic “Pakistan” page trying to rank in Karachi, Lahore and Islamabad.
- No follow-up. Without a re-crawl after fixes, you never confirm the issues are gone.
If you are hiring someone, be wary of anyone who promises guaranteed rankings; Google itself warns against this. Ask to see a sample audit and how findings are prioritised.
Frequently asked questions
What is included in an SEO audit?
Crawling and indexing, technical health and speed, on-page elements, content quality and duplication, internal and external links, and local signals where relevant. A good audit ends with prioritised recommendations, not just a list of issues.
Can I do an SEO audit for free?
Yes, for a small site. Google Search Console, PageSpeed Insights, the free version of Screaming Frog (up to 500 URLs) and a careful manual review cover most of it. Paid tools mainly save time on large sites and add backlink data.
How often should I do an SEO audit?
A full audit once a year suits most sites, with monthly Search Console checks in between. Audit again before and after a migration or redesign, and whenever traffic drops for more than a few weeks.
How long does an SEO audit take?
From a day for a small site to several weeks for a large store or publisher. Most of the time goes into analysis and prioritisation rather than running tools.
What is the difference between a technical SEO audit and a full audit?
A technical audit covers crawling, indexing, rendering, speed and structured data. A full audit adds content quality, on-page optimisation, links and competitors, and usually local or international factors.
What should I fix first after an audit?
Anything stopping important pages being crawled or indexed, then high-impact fixes on templates that affect many pages, then content improvements on pages with plenty of impressions but weak clicks or rankings.
Sources
- HTTP Archive, “Web Almanac 2024: Performance chapter” (2024).
- Google Search Console Help, “Page indexing report” (accessed 2026).
- Google Search Central, “Do you need an SEO?” (last updated 2026).
If you would rather have someone else do the crawling, analysis and prioritisation, my SEO audit service delivers a ranked action plan rather than a tool export, or you can request a free audit to start.
Request received
Thank you! Saad will contact you within the next 24 hours.
Keep an eye on your phone and inbox.