How to perform an SEO audit: from data collection to action plan

You need to perform an SEO audit, or steer the one a team is running for you, without spending three weeks on it or producing four hundred alerts that nobody will act on. This page gives the order of operations: what you settle before starting, the four steps of the method, the grid for reading a variation and the short version when time is tight.

It lets you decide which pages to work on and in what order. The upstream framing (coverage, triggers, frequency, the impact × effort × risk grid) is set out in the reference SEO audit.

What you settle before starting

Two things are settled before opening a single export: what the audit has to demonstrate, and what it covers. Skipping them amounts to sorting anomalies as they come.

The objective the audit has to demonstrate

You do not run an audit to produce a checklist: you run it to answer an explicit, shared and measurable objective. Aiming at “position” is no longer enough. A usable objective looks more like this:

• increase organic clicks on a set of landing pages;
• improve CTR on queries with high impressions;
• strengthen conversions from organic, prioritizing the pages that already convert;
• secure the indexing of “business” pages: offers, categories, pillar content.

These objectives sort themselves into a hierarchy as soon as you look at where the clicks are. The first organic position captures 27.6% of clicks (Backlinko, 2026), while page 2 receives almost none. Moving a page from fifth to second place is therefore not worth the same as moving it up from page 2 to the bottom of page 1. The SEO statistics gather these benchmarks.

The scope and the access

To avoid the “titanic audit”, define the scope (domain, subdomains, directories, excluded pages such as the admin area or internal search) and the depth: a broad view, plus a focus on the key pages.

The most pragmatic approach is to select a shortlist of 20 to 50 high-stakes URLs first, then widen it if necessary. It brings together four groups:

• the main organic landing pages;
• the pages that convert best;
• the pages that have dropped the most;
• the strategic pages that are still invisible.

That last group is the one most often forgotten: a page that is blocked or deindexed appears in no performance export.

Without reliable data, the audit becomes an opinion. Search Console (performance, indexing, manual actions) and Google Analytics (landing pages, engagement, conversions) form the pre-diagnosis foundation. Prepare the exports before you start, over 28 days compared with the previous period: an extraction re-run mid-analysis loses comparability.

This foundation says what is going wrong, rarely why. You have to add at least:

• a crawl of the site, the only way to obtain the inventory of URLs, the statuses, the directives and the real internal linking;
• an inspection of the rendering, which shows what an engine sees once the JavaScript has run;
• inbound link data, when popularity is among the questions asked.

Step 1 — start from real performance, not from the list of anomalies

Start with real performance, not with a list of anomalies. Anomalies are counted in the hundreds, the pages that carry the value in dozens: it is the latter that decide what you look at.

Spot the pages that matter

In Search Console, export the pages and the queries that combine:

• high impressions, a sign of coverage and potential;
• significant clicks, which prove interest and intent;
• positions close to the top 10, where the gain is fastest;
• a contribution to conversions on the Analytics side, even at lower traffic volume.

Crossed with the framing shortlist, these filters give the working list for the whole audit. Strategic pages that are still invisible, absent from the reports, are added to it by hand from the crawl. A page that is not on the list will not be examined this time round: that choice protects the time available, and the list will justify the order of the actions at step 4.

The quick gaps and the testable hypothesis

The most profitable opportunities often sit on queries that are already visible: look for pages in positions 4 to 15 with high impressions, which call for work on structure, proof and internal linking, and pages with a low CTR at a stable position, where the problem frequently comes from the snippet or from a richer results page.

For each key page, write a testable hypothesis that connects a symptom to a likely cause, then to a measurable action:

• “impressions are falling because the page is excluded, canonicalized or redirected”;
• “the position is stalling because the content does not cover the intent”;
• “the CTR is low because the title is generic and does not promise a clear answer”.

A written hypothesis gets checked; an unwritten hunch turns into a project whose purpose nobody can state any more.

Step 2 — the checks that block visibility

The hypotheses from step 1 are confronted with what the site actually does, on the working list only. You record, you qualify, you fix nothing yet.

Indexing and coverage

In Search Console, examine the reasons for non-indexing and compare them with your shortlist of high-stakes pages. Not every URL is meant to be indexed, but an excluded “business” page has to trigger an action. Confirm the status with URL inspection, then request indexing after the fix.

When the finding calls for a rule (crawl directives, statuses, canonicalization, JavaScript rendering, orphan pages), it is the technical SEO audit that gives the procedure to follow.

Content and structure of the priority pages

On the pages in the working list, check what influences understanding and the click:

• an explicit, non-duplicated, intent-driven title;
• a readable structure in H2/H3, with a clear answer from the start;
• proof elements: examples, attributed figures, definitions.

Frequent faults (a title that describes the brand rather than the answer, an answer pushed three screens down, a promise the body does not keep) are noted with their URL, without writing the fix at this stage.

Internal linking, duplication and cannibalization

Internal linking serves both crawling and hierarchy. Look for high-stakes pages that are too deep, well-performing pages that do not redistribute towards your strategic pages, and vague or over-optimized anchors. Practical rule: a few contextual links, in the body text, to pages in positions 4 to 15, without forcing the anchors.

Two signals are recorded without being settled. Technical duplication means several versions of the same URL are accessible, which dilutes the signals. Editorial cannibalization shows when a query “changes” URL in Search Console. Designating the page that keeps the topic belongs to the semantic audit, which carries the rules for choosing between creating, optimizing and consolidating.

The following table sums up the step 2 checks and what each finding conditions:

Step 3 — interpret without picking the wrong fight

This is the step where an audit most often loses its way, through the temptation to treat everything at the same level. Interpreting means deciding what a piece of data proves, then what enters the action plan.

What Search Console confirms, and what it does not prove

Search Console confirms that a page is visible, that it gets clicks and that an indexing problem really affects strategic pages. On the other hand, on its own it does not “prove” the single cause of a drop: it shows a gap, not its origin.

A hypothesis from step 1 is therefore confirmed when the data and the field finding say the same thing: the page really is excluded, the title really is generic. When they diverge, the hypothesis stays open and does not become an action: built on an unestablished cause, it would produce fixes that nobody will be able to judge, six months later, as having served any purpose.

The false-positive filter and the cross-reading

Faced with hundreds of “noisy” points, the operational filter is simple: an anomaly is a priority if it affects at least one of the following:

• organic landing pages;
• pages that convert;
• a strategic page that is still invisible;
• a whole template, through sheer scale.

An anomaly that ticks no box does not enter this round's action plan, and that is the rule to invoke when the production team contests the order of the tickets.

The cross-reading then connects each variation to a family of likely causes:

Step 4 — from finding to prioritized action plan

The expected output: a few strong decisions, correctly ordered, rather than a massive unsorted backlog. Three moves lead there: score, order, write.

Score: impact, effort, risk

To prioritize without endless debate, assess each action with the impact × effort × risk grid from the reference SEO audit:

• impact: expected effect on crawling, indexing, ranking or CTR, and on leads, revenue or strategic pages;
• effort: time, dependencies, release cycle;
• risk: regression, side effect, traffic loss.

The assessment does not have to be precise; it is done in front of the people who will execute. A developer who assesses the effort will not contest it when the ticket comes; an acquisition manager who assesses the impact owns the order that comes out of it.

Order: quick wins, structural projects, continuous optimizations

The assessments translate into three batches, which do not run at the same pace:

• Quick wins: pages already close to the top 10, abnormally low CTR, internal linking to strengthen on a few hubs.
• Structural projects: content consolidation, rebuilding a template, global URL rules.
• Continuous optimizations: gradual enrichment, iterations on the editorial plan, tracking SERP changes.

The classic trap is to launch all three batches in the same week: structural projects affect whole templates and blur the measurement of the quick wins. Sequencing preserves the readability of the effects.

Write an executable action

A recommendation that does not become an action will not be executed. Each one states three elements:

• the scope: URL, template or directory;
• the owner: SEO, content or development;
• the validation criterion: the proof expected, for example an improvement in indexing in Search Console or a rise in clicks on a comparable group of queries.

Example: “On [URL], reword the title to reflect the main intent observed in Search Console, then measure CTR over 28 days against the previous period.” Other actions written end to end, with the recommendation table and its columns, appear in this SEO audit example.

The short audit: what you check when you have only an hour or two

When time is short, the sequence comes down to ten checks, which fit into one to two hours on a mid-sized site:

• 1. Identify the top 10 to 20 organic landing pages and their trends.
• 2. Compare clicks and impressions over 28 days against the previous period.
• 3. Spot 10 non-brand queries in positions 4 to 15 with high impressions.
• 4. Check the important pages excluded from the index.
• 5. Check the errors affecting high-stakes pages, or their internal links.
• 6. Spot the pages with a low CTR despite a decent position.
• 7. Check the consistency of the URL versions and the expected redirects.
• 8. Check 3 to 5 “money” pages: title, Hn hierarchy, direct answer, outbound internal linking.
• 9. Identify a likely cannibalization: a query that switches from one URL to another.
• 10. Produce a mini-backlog of 10 actions at most, prioritized.

With only an hour, drop checks 7 to 9 first: the most manual checking for the fewest decisions.

Beyond that, only two levels, and they do not change the sequence:

Whatever the level, the crawl and the inspection of the rendering remain necessary. The choice of SEO audit tools arises as soon as volume exceeds what can be checked by hand.

Four mistakes distort the diagnosis, whatever duration is chosen:

• Auditing without an objective: you pile up findings but no decision follows.
• Treating everything at the same level: a micro-anomaly must not block a structural fix.
• Confusing correlation with causation: a drop can come from a richer SERP, not from a problem “on the page”.
• Not planning the validation: without acceptance criteria, you declare “fixed” what is not.

How much time to spend, and what you deliver at the end

There is no single duration: it grows with the size of the site and the level of write-up expected. Break the work into four blocks:

• collection and exports, which depend on the number of sources and the state of the access;
• analysis focused on high-stakes pages, which grows with the number of distinct templates;
• prioritization, which varies little;
• write-up, which overruns most often.

It includes the coordination between content, development and marketing, often underestimated: plan for it at framing. When the audit is outsourced, the budget depends on the same factors; billing models are detailed in the article on the agency SEO audit, suggested at the end of the page.

At the end, three deliverables at a minimum: a summary (major problems, opportunities, risks), the export of the data analysed, so that the findings can be reread, and a prioritized backlog with owners, deadlines and expected proof. This backlog is only usable on three conditions:

• no recommendation without proof: a finding with no URL and no data cannot be checked;
• no action without an owner: it will stay in the document;
• no action without a validation criterion: you will declare “fixed” what is not, and the next audit will start from scratch.

These three refusals avoid the “black box” audit and the backlog that cannot be implemented.

Continue reading

Depending on what remains to be done once you have mastered the sequence:

• You are outsourcing the audit: the agency SEO audit sets out what to expect from a supplier, deliverables, billing and acceptance included.
• The actions are delivered: SEO tracking details KPIs, annotations and the monitoring of gains over time.
• Your visibility plays out in one area: the local SEO audit adds local signals, NAP consistency, reviews and business profile.

Replaying the sequence after every release, without redoing the collection by hand, is the task covered by the audit and mapping module.

FAQ: frequently asked questions about performing an SEO audit

Which practical steps should you follow so as not to forget anything?

An SEO audit follows four steps: start from real performance to choose the pages, check on those pages what is blocking visibility, interpret while filtering out false positives, then turn the findings into a prioritized backlog. Validation after implementation closes the cycle.

What can you check in one to two hours (quick analysis)?

In one to two hours, ten checks cover the essentials: landing pages and trends, clicks and impressions over 28 days, non-brand queries in positions 4 to 15, important pages excluded from the index, errors on high-stakes pages, low CTR. They lead to a mini-backlog of ten actions.

Which elements should be checked first in an audit?

Check first what can block the visibility of high-stakes pages: indexing, URL consistency, major errors, duplication and cannibalization, then internal linking, CTR and content structure. The order matters, because an unindexed page gains nothing from a better title.

Which free tools can you use with no software budget?

Search Console and Google Analytics form a free pre-diagnosis foundation that everyone already has. They replace neither a crawl, often available in a free version capped on the number of URLs, nor the inspection of the rendering, which URL inspection shows page by page.

How do you interpret the results without overreacting?

An alert is only a priority if it affects organic landing pages, pages that convert, a strategic page that is still invisible or a whole template. Search Console shows a gap, not its cause: as long as the data and the field finding diverge, the hypothesis stays open and does not become an action.

How do you prioritize the actions after the audit?

You prioritize each action on three criteria, impact, effort and risk, assessed with the people who will execute it. The actions are then grouped into quick wins, structural projects and continuous optimizations, launched in sequence. The goal is not “zero alerts”, but a few strong decisions, correctly ordered.

How long should it take, depending on my context?

The duration depends on the volume, the number of templates and the level of write-up expected. Count one to two hours for the short routine, a few days for a standard audit and several weeks for an in-depth audit, internal coordination included.

What do you do if everything “looks fine” but positions are not moving?

Go back to the pages and the queries: the match between the intent and the page, the depth and credibility of the content, the internal linking, then the CTR. If impressions and positions are stalling together, look for a coverage gap, that is, sub-topics expected and missing, or cannibalization between two of your pages.