SEO Audit Guide: The Exact Order to Run One (and What to Fix First)

By Christoph Olivier, Founder, CO Consulting. Last reviewed: July 2026.

Most SEO audits fail because people check things in the wrong order. They spend an afternoon rewriting title tags on pages Google cannot even crawl. This guide gives you the run order I use on client sites: seven stages, the one tool that matters at each stage, and a two-axis triage that turns a messy findings list into a ranked fix queue. It is the operating procedure, not another list of things to fix.

What an SEO audit is (and the one rule that changes everything)

An SEO audit is a staged inspection of a website to find what is stopping it from ranking, then sorting those findings into a priority order to fix. The rule that changes everything: work top-down through the stack. Crawl and index issues first, then technical health, then on-page, then content, then authority, then AI-search readiness. A perfect title tag on a noindexed page earns nothing.

Each layer sits on the one below it. If Google cannot crawl the page, nothing else you fix matters. If the page is crawled but blocked from the index, your on-page work is invisible. This is why order beats effort. Working the stack in sequence means every fix you make can actually take effect, instead of stacking optimizations on a broken foundation. For the difference between an audit (find and fix) and analysis (understand the current state), see our breakdown of what SEO analysis is.

Before you start: set the scope and pull your baseline

Set scope first: pick the property, the date range, and the metric you are trying to move. A small site under 50 pages takes two to five hours to audit; a 50 to 500 page site takes a few days. Pull one baseline export from Google Search Console (last 3 months of clicks, impressions, and position) so you can prove the audit worked later.

Write down the single goal before you open a tool. “Recover the 12 pages that lost position in the last 90 days” is a scope. “Improve SEO” is not. The goal decides which findings are worth logging and which are noise you can skip on this pass. Save that GSC export as your before-picture; a re-audit in 90 days against the same export is how you defend the work to a client or a boss.

The 7-stage SEO audit run order

Run these seven stages in order. Do not jump ahead. The table below is the whole audit at a glance: the stage, the question it answers, the one tool to reach for, and roughly how long it takes on a small site.

Stage 1: Crawlability

Crawlability confirms bots can reach your pages. Run a crawler like Screaming Frog against the full site, then open robots.txt and confirm no critical section is disallowed. Flag orphan pages (zero internal links in), broken internal links (404s), and redirect chains longer than one hop. Nothing below this stage matters if bots hit a wall here.

The fastest win at this stage is usually a robots.txt line blocking a folder that should be crawled, or a nav change that stranded a set of pages with no inbound links. Both are template-level and touch many URLs at once, which is exactly the kind of fix that earns its place at the top of the queue.

Stage 2: Indexability

Indexability confirms the right pages are in Google’s index and the wrong ones are not. Open the Pages report in Google Search Console and read the “Why pages aren’t indexed” reasons. Cross-check for accidental noindex tags, canonical tags pointing at the wrong URL, and thin pages Google chose to drop. Money pages must be indexed; tag and filter pages usually should not.

The two failures that quietly kill traffic here are a noindex left on after a staging launch and a canonical that points every variant at the homepage. Both make good pages invisible while looking fine to a casual glance. Compare the indexed count in GSC against your real page count; a big gap in either direction is the finding.

Stage 3: Technical health

Technical health checks that pages load fast, render on mobile, and stay visually stable. Run PageSpeed Insights on a template sample (home, a service page, a blog post) and read the field data (CrUX), not just the lab score. The three Core Web Vitals to log are LCP (load), INP (responsiveness, which replaced FID), and CLS (layout shift).

Audit by template, not by page. One slow hero image or one render-blocking script usually repeats across every page built on that template, so a single fix can lift hundreds of URLs. That leverage is why template-level speed issues outrank almost every on-page tweak. Our technical SEO checklist for founders covers this layer in more depth.

Stage 4: On-page

On-page checks that every indexed page has one clear H1, a unique title tag under about 60 characters, a meta description that earns the click, and a heading structure that matches how the query is phrased. Export the crawl and sort for missing H1s, duplicate titles, and titles that do not contain the target term. Fix templates and top pages first.

The highest-value on-page finding is usually duplicate or missing title tags across a template, because it is one fix that corrects many pages. Rewriting a single low-traffic post’s meta description is real work for near-zero return, so it drops to the bottom of the queue no matter how easy it is.

Stage 5: Content

Content checks whether the page actually answers the query it ranks for. Pull the queries each page gets impressions for in GSC, then read the page as a searcher would. Flag intent mismatches (the page is a listicle, the query wants a how-to), thin coverage, and stale dates. Google’s helpful-content signals and E-E-A-T reward pages that satisfy the searcher, not pages that mention the keyword.

The pattern to hunt for is a page ranking on page two for a strong query it half-answers. Those are your fastest content wins: the authority already exists, so closing the intent gap can move it onto page one. See our guide to integrating SEO into your content for how to close those gaps without keyword stuffing.

Stage 6: Authority

Authority checks whether enough quality sites link to yours. Count referring domains (more telling than total links), scan the anchor-text spread for unnatural patterns, and note any obviously spammy links. You can pull a free snapshot from the Links report in Search Console; a backlink tool gives you competitor comparison. Referring-domain gaps against competitors are strategy inputs, not quick fixes.

Treat this stage as diagnosis, not a same-day to-do. Link building is a program that runs for months, so authority findings feed your roadmap rather than your fix queue. The one urgent item here is a sudden spike of toxic links, which may warrant a disavow. If you are weighing whether to hire this out, our SEO services buyer’s guide covers what good link work looks like.

Stage 7: AI-search readiness

AI-search readiness checks whether AI engines can lift and cite your page in AI Overviews, ChatGPT, and Perplexity. Validate that key pages carry correct schema (Article, FAQPage, Organization), confirm the author is named with real credentials, and check that each section leads with a self-contained answer an engine can quote. This layer decides whether you show up in AI answers, not just blue links.

The two signals that matter most are a clear answer in the first 40 to 75 words of each section and structured author identity, because both make a passage easy to lift and attribute. Roughly 60% of Google searches now end without a click, so citability is no longer optional. For the full playbook, see our guide on winning at generative engine optimization.

How to prioritize the fixes: the impact vs effort matrix

Once the seven stages are done you have a messy findings list. Rank it with two axes: business impact (how much traffic or revenue the fix protects or unlocks) and effort (how long it takes to ship). Do high-impact, low-effort first. The matrix below is the exact order I hand clients.

Two rules override the grid. First, triage by business impact before technical severity: a broken template on your top service page beats a broken template on a page nobody visits. Second, favor fixes that touch many URLs at once (template speed, sitewide schema, navigation) over one-off page edits, because the leverage is enormous. A single template fix can move hundreds of pages for the same effort as editing one.

A worked example: the 3-hour audit that found the real problem

Here is a first-hand pass I ran on a service business that had “tried everything” on content. Stage 1 crawl: clean. Stage 2 indexability: the GSC Pages report showed 40% of blog URLs excluded as “Duplicate, Google chose different canonical.” That was the whole story. A plugin had set a self-referencing canonical wrong after a migration, so half their content was pointing authority back at category pages.

We never reached the content stage. The fix was one canonical-tag correction at the template level, shipped the same afternoon (a P1). Indexed pages recovered over the next three weeks and the pages that had been “underperforming on content” started ranking, because Google could finally credit them. The lesson is the whole point of this guide: had we started at the content stage, where the client wanted to, we would have rewritten dozens of pages that were fine and never found the canonical. Order first, effort second.

How often to re-run the audit

Run a full seven-stage audit every quarter and a lightweight crawl-plus-index check monthly. After any major change, a redesign, a CMS migration, or a large content push, re-audit within 48 hours, because those are the events that reintroduce crawl and index errors. Re-run against your saved GSC baseline so you can prove movement.

The monthly light check is just Stages 1 and 2: crawl for new 404s and read the GSC Pages report for new exclusions. That fifteen-minute habit catches the errors that do the most damage before they compound. If you would rather hand the whole cycle off, our growth consulting team runs this cadence for clients, or you can book a consultation to walk through your own site.

Frequently asked questions

What order should I run an SEO audit in?

Run it top-down through the stack in seven stages: crawlability, indexability, technical health, on-page, content, authority, then AI-search readiness. Each layer depends on the one below it, so a crawl or index problem must be fixed before on-page or content work can take effect. Working out of order wastes effort on fixes that cannot help yet.

What tools do I need for an SEO audit?

You can run a solid audit with four free or low-cost tools: a crawler (Screaming Frog, free up to 500 URLs), Google Search Console for indexation and query data, PageSpeed Insights for Core Web Vitals field data, and a schema validator. A paid backlink tool like Ahrefs or Moz adds competitor link comparison, but the free stack covers stages one through five completely.

How do I decide which SEO fixes to do first?

Rank findings on two axes: business impact and effort. Ship critical blockers (indexation, robots, HTTPS, sitewide CWV failures) the same day, then high-impact low-effort template fixes within a week. Prioritize anything that touches many URLs at once, such as template speed or sitewide schema, over one-off page edits, because the leverage is far higher for the same work.

How long does an SEO audit take?

It depends on site size. A small site under 50 pages takes roughly two to five hours for a working audit; a 50 to 500 page site takes a few days to a couple of weeks; sites over 500 pages can take several weeks. The seven-stage run order keeps you efficient by stopping you from deep-diving stages that a higher-level blocker has already made irrelevant.

How often should I audit my site?

Run a full audit every quarter and a lightweight crawl-and-index check monthly. Always re-audit within 48 hours of a major change, a redesign, a CMS migration, or a large content push, because those events commonly reintroduce crawl and indexation errors. Re-running against a saved Search Console baseline lets you measure whether the fixes actually moved rankings and traffic.