Most SEO audits fail before anyone reads them. A crawler produces four hundred issues, the issues get pasted into a document, the document goes to a developer who has three days a quarter for SEO work, and nothing changes. The audit was thorough and completely useless.

A useful audit is a shorter document that answers one question: what is stopping this site from earning the traffic it should, and in what order do we fix it? This guide covers how I run audits — the types, the sequence, the tools, what to check at each layer, and how to turn the findings into work that actually gets done.

What Is an SEO Audit?

An SEO audit is a structured review of a website's technical health, content quality, on-page implementation, authority profile and analytics setup, carried out to identify what is limiting organic performance and to produce a prioritised plan for fixing it. Its output is a ranked set of actions with owners and effort estimates, not a list of every issue a crawler can detect.

That definition rules out two things that get called audits and are not:

• A tool score. A number out of a hundred from an automated scanner is a starting point, not a diagnosis. Scanners cannot tell whether a page satisfies search intent.
• An issue dump. Four hundred findings with no priority is a way of transferring the hard decisions to someone with less context than you.

The Types of SEO Audit

Not every situation needs the same audit. Matching the type to the problem saves a great deal of wasted work.

Audit Type	When to Run It	Typical Duration	Main Output
Full audit	New engagement, or once a year	2 to 4 weeks	Complete diagnosis and 12-month roadmap
Technical audit	Indexing problems, slow site, migration aftermath	3 to 7 days	Developer ticket list
Content audit	Traffic decline, thin or ageing library	1 to 2 weeks	Keep, improve, merge, remove decisions
Backlink audit	Manual action, suspicious link growth, post-acquisition	2 to 5 days	Disavow list and outreach targets
Local audit	Map pack invisibility, multi-location business	2 to 4 days	Profile, citation and location page fixes
Pre-migration audit	Before a redesign, replatform or domain change	1 week	URL map and rollback plan
Health check	Monthly or quarterly	2 to 4 hours	Regression detection

If a site is losing traffic and nobody knows why, run a technical audit first. Technical faults are cheaper to find, faster to fix, and they invalidate any content conclusion you would otherwise draw. There is no point judging a page's quality if Google has not indexed it.

The Audit Sequence I Follow

Order matters more than completeness. Each phase either rules out a cause or narrows the next one.

Start With a Baseline You Can Compare Against

Before touching anything, record where the site stands: indexed pages, organic clicks and impressions for the last three months, the twenty pages earning the most organic traffic, Core Web Vitals status by template, and referring domains. Save the export with the date on it.

Without that snapshot you cannot demonstrate later that the audit worked, and you cannot separate the effect of your fixes from a core update that landed in the same fortnight. It takes twenty minutes and it is the difference between a report that proves value and one that asserts it.

Phase 1: Crawling and Indexing

Nothing else matters if Google cannot reach or store your pages. Check, in this order:

• robots.txt — what is blocked, deliberately or otherwise. See my guide to robots.txt for the syntax traps.
• XML sitemaps — present, submitted, current, containing only indexable canonical URLs. My guide on creating a sitemap covers the structure.
• Index coverage in Search Console — compare indexed pages against total pages worth indexing. A large gap is the finding.
• Noindex and canonical tags — every accidental noindex I have found was on a template, affecting hundreds of pages at once.
• Crawl budget — for larger sites, whether crawlers are spending their visits on pages that matter. My guide to crawl budget optimisation covers the diagnostics.

Pages sitting under "Discovered – currently not indexed" are the most informative single report in Search Console. They usually mean Google found the URL and judged it not worth crawling — a quality and internal linking problem dressed as a technical one.

Phase 2: Site Architecture and Internal Links

Crawl the site with Screaming Frog or Sitebulb and look at structure rather than errors:

• Click depth from the homepage — important pages more than three clicks deep are being deprioritised by your own site.
• Orphan pages with no internal links pointing at them. My guide to fixing orphan pages covers the remedy.
• Redirect chains and loops, which waste crawl budget and dilute signals.
• Internal link distribution — whether your money pages receive links from anywhere other than the navigation.

Architecture is the highest-leverage and least glamorous part of most audits. Moving a service page from four clicks deep to two, and adding fifteen contextual internal links to it, routinely does more than a month of content work. The reasoning is covered in my piece on website architecture and SEO.

Phase 3: On-Page and Content Quality

Now judge the pages themselves. For every URL that matters:

• Title and meta description — unique, accurate, written to earn a click rather than to hold a keyword.
• Heading structure — one H1, logical H2s that map to the questions the query implies.
• Intent match — compare the page against the top three results. If they are comparisons and yours is an essay, format is the problem.
• Coverage — subtopics that two or more ranking competitors address and you do not.
• Cannibalisation — two or more of your pages targeting the same query. Consolidate.
• Freshness — pages containing years, prices or tool lists that have aged badly.

Classify every page as keep, improve, merge or remove. Most sites carry a long tail of pages that were published for a reason nobody remembers and now dilute the site's topical focus. My on-page SEO guide covers the improvement work in detail.

Phase 4: Performance and Core Web Vitals

Use field data, not lab data, as the verdict. Search Console's Core Web Vitals report groups URLs by pattern, which tells you whether a template is at fault rather than a page. Then use PageSpeed Insights on a representative URL from each failing group to find the cause. The web.dev documentation explains what each metric actually measures, and my guide on solving Core Web Vitals failures covers the common fixes.

Phase 5: Structured Data and SERP Presentation

Check what markup exists, whether it validates, and whether it is earning anything. Article, Product, FAQ, LocalBusiness, Breadcrumb and Organization cover most needs. Validate against schema.org and Google's Rich Results Test. My guide to schema markup covers implementation.

Phase 6: Authority and Backlinks

Look for patterns rather than counting links: referring domain growth over time, the ratio of branded to exact-match anchors, links pointing at pages that no longer exist, and any sudden spike that might indicate a negative SEO attempt or a past paid campaign. Use a backlink checker to pull the profile, and treat authority scores as comparison tools rather than targets.

Phase 7: Analytics and Measurement

The last phase, and the one most often skipped. If conversions are not tracked correctly, every recommendation you make afterwards will be judged on the wrong numbers. Confirm GA4 events fire, that Search Console is linked, that internal traffic is filtered, and that organic sessions can be traced to enquiries.

Tools for Each Layer of the Audit

Layer	Primary Tool	What It Answers	Cost
Indexing	Google Search Console	What Google has stored and why it excluded the rest	Free
Crawling and structure	Screaming Frog	Depth, redirects, canonicals, orphan pages	Free to 500 URLs
Performance	PageSpeed Insights and CrUX	Real-user Core Web Vitals by template	Free
Content and keywords	Search Console plus Ahrefs or Semrush	Intent gaps and cannibalisation	Free to paid
Backlinks	Ahrefs Webmaster Tools	Referring domains, anchors, growth pattern	Free for owned domains
Structured data	Rich Results Test	Whether markup is valid and eligible	Free
Measurement	GA4	Whether organic traffic converts	Free

Almost every layer has a free option that is good enough for a first audit. If you are assembling a stack on no budget, my roundup of free SEO tools covers the gaps and the workarounds.

Prioritising Findings So They Get Fixed

This is where audits succeed or fail. Score every finding on three axes — impact on organic performance, effort to implement, and confidence that it will help — then sort into three tiers.

• Tier 1, fix now: anything blocking indexing, site-wide template errors, broken canonicals, missing tracking. Usually five to fifteen items.
• Tier 2, next quarter: content improvements to pages already ranking 5–20, internal linking, schema, page speed on key templates.
• Tier 3, ongoing: new content clusters, link acquisition, architecture changes that need a redesign.

Write every Tier 1 item as a ticket a developer can action without asking you a question: the URL pattern affected, the current behaviour, the required behaviour, and how to verify it. An audit that needs a meeting to interpret will not be implemented.

What a Good Audit Document Looks Like

• One page of summary — the three things holding the site back, in plain language.
• The prioritised action table — finding, evidence, tier, owner, effort, expected effect.
• Supporting detail per finding — screenshots, affected URL counts, the crawl export.
• A re-check date for every Tier 1 item.

Raw exports belong in an appendix, not in the body. For a structured starting point on the technical side, work through my technical SEO checklist and the broader website audit checklist.

How Often to Audit

• Full audit: annually, or at the start of any new engagement.
• Technical health check: monthly for large or frequently changed sites, quarterly otherwise.
• Content audit: every six to twelve months, or after a significant traffic decline.
• Backlink review: quarterly, and immediately if referring domains spike unexpectedly.
• Always: before and after any migration, redesign or replatform.

Between audits, let Search Console act as the monitor. Sudden movements in index coverage, Core Web Vitals or impressions are the early warning that a fresh look is needed.

Common Audit Mistakes

• Auditing everything at once. Depth in the wrong layer wastes weeks.
• Reporting tool severity as business priority. Crawlers do not know which pages make money.
• Ignoring intent. No amount of technical work rescues a page that answers the wrong question.
• No owner, no date. Findings without accountability stay findings.
• Never re-checking. Half of implemented fixes are implemented incorrectly. Verify.
• Auditing without the analytics layer. You cannot prove the work paid off.

Why Work With Sadekur Rahman

An audit is only worth what gets implemented from it. My audits come as a one-page summary, a prioritised table, and developer-ready tickets for anything technical — plus a working session to walk the team through the first tier, because that is the part that determines whether the rest ever happens.

If you want a proper diagnosis of what is holding your site back, see my SEO services and case studies, compare plans and pricing, or book a meeting to talk through your site.

Frequently Asked Questions

How long does an SEO audit take?

A focused technical audit takes three to seven days. A full audit covering technical health, content, links and analytics takes two to four weeks for a mid-sized site. Anything promising a complete audit in an hour is delivering an automated scan, which is a useful input but not a diagnosis.

Can I run an SEO audit myself?

Yes, for the technical and on-page layers. Search Console, Screaming Frog's free tier and PageSpeed Insights cover indexing, structure and performance without cost. The parts that benefit most from experience are prioritisation and intent analysis — deciding which of two hundred findings actually deserve the next month of work.

How much does an SEO audit cost?

It varies widely with site size and scope. A small business technical audit sits at the lower end; a full audit of a large ecommerce site with a migration history costs considerably more. Judge the quote on what the deliverable contains: prioritised, implementable actions rather than an exported issue list.

How soon will I see results after implementing audit fixes?

Indexing and crawl fixes often show within two to four weeks. On-page and internal linking improvements to pages already ranking typically move within four to eight weeks. Content rebuilds and authority work take three to six months. Set the expectation before the work starts, not after.