SEO audit: what it covers, when to run it, what it delivers

What an SEO audit covers — and what it does not deliver

Analysing, in a structured way, every element that shapes a site's organic visibility — technical foundations, content, authority and experience: that is what an SEO audit covers in practice. The goal is not to produce an exhaustive list of alerts, but to understand why a site has plateaued, is losing rankings or fails to convert, then to turn that diagnosis into a prioritized action plan. The effects are usually gradual and are measured over several months, because they depend on crawling, indexing and the consolidation of relevance signals.

In operational terms, it is a deliverable that connects three things: (1) observable findings (crawling, indexing, performance, content), (2) evidence (Search Console and Analytics data, crawl extracts), and (3) a prioritized roadmap (what to do, where, in what order, against which validation criteria). An audit therefore starts with a decision, not with a tool: naming the objectives pursued and the pages that carry the value, then examining only what concerns them. The approach holds for a brochure site as much as for an online shop, whatever the technology in use.

It is justified by where the clicks concentrate. The click-through rate on the first organic position (desktop) is 34% (SEO.com, 2026), while the click-through rate on page 2 of the SERPs is 0.78% (Ahrefs, 2025): gaining a few places on queries already close to the first page can have a real effect on qualified traffic. At the same time, the share of searches ending without a click (zero-click) reaches 60% (Semrush, 2025): a diagnosis that looks only at traffic misses part of the visibility. The SEO statistics bring these benchmarks together with their source and their year.

What is measured, and what should not be over-interpreted

A reliable audit combines three families of signals:

• “Engine” signals: crawling, indexing, HTTP statuses, canonicals, internal linking, performance, mobile compatibility.
• “Content” signals: search intent, keyword-to-page alignment, topical coverage, duplication, cannibalization, editorial structure.
• “Outcome” signals: impressions, clicks, CTR, rankings, conversions, and how they move over time.

Conversely, avoid over-interpreting isolated alerts with no observable impact, or optimizing without validating the effect on indexing, ranking or conversion. The right reflex is to cross crawl data with Search Console data — impressions, indexed pages, queries — in order to separate noise from signal. It is also what lets you justify, in a steering meeting, why one anomaly comes first and another waits.

What is committed to, what is announced, what is never guaranteed

Three kinds of promise coexist in an audit, and confusing them is the first source of disappointment. Deliverables and deadlines are committed to: the scope audited, the delivery date, the report format, the roadmap and the acceptance criteria are contracted like any ordinary obligation. The expected gain is announced as a hypothesis with its conditions — search volumes, starting positions, real capacity to execute — then measured once the fixes are in production. A specific position on a specific keyword on a specific date, by contrast, is never guaranteed: that is the sole object of the reservation, and it extends neither to the deliverables nor to the measured trajectory. What should alert a buyer is therefore not a refusal to estimate a gain before the diagnosis — without enough data, that refusal can be a sign of seriousness — but a refusal to commit to deliverables and deadlines.

When an SEO audit is triggered, and how often it comes back

An audit is not decided by the calendar alone. Two logics overlap: an event that changes the way the site is crawled, understood or served, and which calls for a check without delay; and a return cadence in normal times, set by the size of the site and by its publishing pace. The criterion that moves you from one to the other fits in a sentence: as soon as something has moved URLs, changed directives or rewritten page templates, you do not wait for the next scheduled slot.

The events that call for a check without delay

These situations have one thing in common: they move or rewrite what the crawlers had already recorded. The check they call for is not a full audit every time, but a targeted reading of what the event may have broken, with a short deadline and a named owner.

In every one of these cases, the question to settle remains the same: is the traffic and are the impressions that existed before still there, on the same pages, with the same indexing status? Until the answer is documented, the event is not closed.

The return cadence in normal times

Outside such events, the cadence depends on context. For a modest site with few publications, a half-yearly analysis may be enough; for a fast-moving e-commerce site or a high-output editorial site, favour monthly KPI monitoring (indexing, errors, impressions) and an in-depth quarterly analysis. Size is not the only criterion: even a small site needs an immediate audit after a migration or a CMS change. Two markers help settle the matter when hesitation persists — the number of pages created or modified since the last reading, and the number of technical releases shipped in the meantime. A site that does not move does not need re-auditing; a site that publishes and deploys every week is monitored continuously and audited in cycles. Writing that cadence into the workload plan, rather than triggering it on an alert, avoids the crisis audit: the one you launch when the loss has already been taken.

Auditing before a redesign or a migration

This is when an audit is most often decided, and when it is most often launched too late. Before redesigning, check one simple condition: can Google crawl and index the pages that matter correctly? If crawling or indexability are already degraded, rebuilding on top does not fix the problem and will make the period after go-live unreadable, for want of knowing what was broken before.

What you record before amounts to a point of comparison, and that point is built while the old site is still live: the inventory of URLs that carry impressions, clicks and conversions; their indexing status; average positions on a basket of queries defined in advance; and the page-by-page mapping between what exists and the target. That inventory is the one thing that cannot be reconstructed after the fact: without it, any variation observed after go-live will remain an impression, not a finding.

What you replay after is exactly the same reading, on the same reference dates: do the inventory URLs respond, do they point where they should point, have they returned to the index, and have the basket queries recovered their level? You replay it twice — first in the days following go-live, to intercept what is blocking, then after a few weeks, once crawling and indexing have settled.

That leaves the trade-off, which is a matter of organization more than of technique. A redesign schedule is rarely negotiable; audit findings are even less so. The rule that holds is to separate, before the project starts, the blocking findings — those that prevent go-live until they are cleared — from those that can be fixed afterwards, and to have that short list approved by the project sponsor. The trade-off is then made once, calmly, on a written list, rather than in the heat of the evening before release.

Technical, semantic, generative: the three angles and what each one determines

An SEO audit is read along three angles, and each one determines something different. Handling them out of order produces recommendations that cannot be applied: improving content the engine does not crawl changes nothing, and working on the citability of a page absent from the index changes even less. The order below is the order of dependencies, not the order of importance.

The technical angle: what crawling and indexing determine

This is the angle that decides everything else: if the pages that matter are neither crawled nor indexed, no editorial work will produce an effect, and the measurement itself becomes misleading — a page absent from the index generates no impressions, which reads wrongly as a relevance problem. At overview level, remember what the angle settles: which pages the engine sees, how often it comes back to them, and which ones it has chosen to leave out. The detail of the checks and the order in which to run them belong to the technical SEO audit, which covers crawling, indexing, statuses, canonicalization, rendering and orphan pages.

The semantic angle: what the page-to-query match determines

Once access is secured, the question becomes one of correspondence: does each page target a clear intent, and does a single page target it? This is the angle that determines the most expensive decision in an action plan — create a page, optimize an existing one, or consolidate several. The most visible symptom is cannibalization: several pages compete for the same query, the signals are diluted and the engine chooses in your place, often badly. Spotting it is one thing, settling it is another; the detection signals and the arbitration rules are handled by the semantic audit.

The generative angle: what citability determines

Generated answers move part of the visibility away from the click: a brand can be cited without being visited. Two markers frame the trade-off. AI Overviews citing the organic top 10 account for 99% of cases (Squid Impact, 2025): the organic base remains the entry condition, not a competing channel. And the click-through rate for the first position in the presence of an AI Overview falls to 2.6% (Squid Impact, 2025): the return on a ranking gain changes with the type of query, which feeds straight into prioritization. The GEO statistics give the other benchmarks, and the measurement itself — being cited, by which engine, on which questions — belongs to the AI GEO audit.

Reading an audit report: evidence, prioritization, acceptance criteria

A report is judged on its ability to turn findings into decisions: what to do, why, on which pages or templates, at what level of priority, and how to verify success. Every recommendation must systematically carry evidence — a crawl extract, a Search Console figure, an example URL — and an expected outcome: indexing, fewer errors, CTR gain, ranking improvement. Length matters less than clarity: findings, evidence, recommendations, prioritization, owners, risks and acceptance criteria. A document that lists anomalies with no hierarchy and no evidence is not an audit, it is a formatted tool export.

The impact × effort × risk grid

Most crawlers surface thousands of items, a large share of which have no measurable impact. The risk is twofold: tying up IT teams on low-value tickets, and delaying the actions that actually change rankings. Effective prioritization therefore connects three axes: potential impact (on crawling, indexing, ranking, CTR, conversion), implementation effort (time, dependencies, release cycle) and risk (regression, side effects, traffic loss). Add a business filter: the same anomaly does not weigh the same on a page that generates leads as on a secondary page. That is what brings a raw list of hundreds of anomalies down to a roadmap of around fifteen defensible actions.

What crawlers often flag, but which rarely changes rankings

Without falling into technical denial, it helps to identify the “noise” alerts: micro-optimizations on pages that are not indexed, tag variations on pages with no traffic, or marginal performance improvements on pages few people visit. Handle them if they pile up on a critical template, otherwise keep them for a later phase. The point is to preserve the teams' bandwidth for the work that actually changes rankings. A report that does not do this sorting passes it on to you, and the sorting then happens without method, as availability allows.

From report to ticket: acceptance criteria and testing

A recommendation that is not turned into a ticket will not be executed. To avoid back-and-forth, every technical recommendation must come with acceptance criteria: expected HTTP status, presence or absence of a tag, redirect behaviour, indexing rules. Testing means re-crawling and checking in Search Console that the change has been taken into account as re-crawls and re-indexing happen. Require these criteria at delivery, not at deployment: written after the fact, they describe what was done rather than what should have been done.

Who runs it: in-house, tool-assisted, or outsourced

The trade-off is rarely about skill and almost always about bandwidth, schedule and independence of view. Two decision lines are enough to settle it, and they are not mutually exclusive: most organizations end up outsourcing the diagnosis and running the execution in-house, or the reverse.

What is done in-house, what calls for a third party

Running the work in-house suits short iteration cycles and the capacity to execute continuously — content, internal linking, technical fixes: the diagnosis then becomes a routine, not an event. Outsourcing the audit becomes relevant in three cases: you lack bandwidth, you are preparing a redesign or a migration, or you need a view independent of those who built the site. That last case is the most underestimated: a team auditing its own work rarely uncovers the decisions it made itself. The CMS, for its part, plays no part in the trade-off: the diagnostic method does not depend on the platform, only the implementation of the fixes varies.

What to require, whoever runs it

The same requirements apply to an in-house team and to a supplier, and they are set before the work starts: the scope audited and what is explicitly excluded from it; the data sources that will serve as evidence; the format of the deliverable and its date; the acceptance criteria attached to each recommendation; and the named owner for each item on the roadmap. Require as well that every fix states how to roll it back if it degrades something else. An audit that does not say who does what, nor how it will be verified, produces a document nobody will open a second time.

Checking that the fixes have produced an effect

Without measurement after deployment, an audit remains a snapshot. Verification answers a precise question, and it is not “has traffic gone up?” but “has the finding that justified the fix disappeared?”. Both can be measured, but not at the same moment nor on the same indicators. The disappearance of the finding is verified straight away, through a re-crawl and through the indexing reports: it is a technical fact, binary. The effect on visibility is read over several weeks — impressions, clicks, CTR, rankings on a basket of queries defined before the fix, conversions — and that delay has to be accepted rather than concluded on too early.

Two precautions make that reading usable. Annotating deployment dates lets you connect a variation to a specific change; without it, any inflection lends itself to every explanation. And avoiding the deployment of several major workstreams in the same week preserves attribution: an architecture change run alongside editorial fixes makes both unreadable. Centralizing crawl findings, Search Console data and Analytics data in a single prioritized reading is precisely the task covered by the audit and mapping module.

FAQ on SEO audits and organic search

What is the difference between an SEO audit and a GEO analysis?

An SEO audit analyses how Google crawls, indexes and ranks your pages in organic results. A GEO analysis assesses the likelihood that your content is cited as a source in answers generated by AI. The technical fundamentals are the same, with additional criteria of extractability and verifiability. AI Overviews citing the organic top 10 account for 99% of cases (Squid Impact, 2025): SEO remains the base.

Should GEO be built into an SEO audit?

Yes, if your objective goes beyond the click and includes visibility in generated answers. In practice, that means adding citability criteria to the classic checks: a structure that is easy to extract, sharp definitions, verifiable and sourced data, editorial neutrality and content freshness. The point is to maximize the likelihood of being picked up as a source, while keeping SEO as the base.

What is an SEO audit for, in practice?

It serves to understand why a site has plateaued, is losing rankings or fails to convert, then to turn that diagnosis into a prioritized action plan. It connects visibility and business performance: visible pages that generate no leads, pages that convert but remain under-exposed, signals that hold conversion back. It helps secure the pages that support revenue.

What does the scope of an SEO audit cover (technical, content, authority, UX)?

An organic search audit analyses in a structured way the elements that shape organic visibility: technical (crawling, rendering, indexing), content (intent, keyword-to-page alignment, quality), authority and links (off-site signals) and user experience, particularly where it weighs on conversion. The excluded scope is named explicitly at framing, just like the covered scope.

What is an “operational” SEO audit (the expected deliverable)?

It is a deliverable that connects: (1) observable findings (crawling, indexing, performance, content), (2) evidence (Search Console, Analytics, crawl extracts), and (3) a prioritized roadmap — what to do, where, in what order, against which validation criteria. The aim is to arrive at executable decisions, not generic recommendations.

What is the difference between an organic search audit and a Google-centred analysis?

The two overlap heavily, because Google concentrates the bulk of usage. A Google-centred analysis leans more on proprietary signals — impressions, clicks, positions and indexing in Search Console. An organic search audit can bring in off-site signals (authority, links) and user experience considerations more explicitly.

Which indicators (KPIs) are measured in an SEO audit?

A reliable audit combines three families of signals: engine (crawling, indexing, HTTP statuses, canonicals, internal linking, performance, mobile), content (intent, topical coverage, duplication, cannibalization, structure), and outcomes (impressions, clicks, CTR, rankings, conversions, movement over time). None of these families can be read on its own.

Which interpretation errors should be avoided during an SEO analysis?

Avoid over-interpreting isolated alerts with no observable impact, or optimizing without validating the effect on indexing, ranking or conversion. The right reflex is to cross crawl data with Search Console data — indexed pages, queries, impressions — in order to separate noise from signal. Avoid as well concluding on an unannotated variation: without a deployment date, attribution is lost.

Why is an SEO audit essential before producing content or redesigning a site?

Before publishing or redesigning, check one simple condition: can Google crawl and index the pages that matter correctly? If crawling or indexability are degraded, publishing more does not fix the problem. Before a redesign, the audit also provides the point of comparison — URL inventory, rankings, indexing status — that can no longer be reconstructed after go-live.

What is the difference between a technical SEO audit and a semantic audit?

The technical audit answers: “Is the site readable and usable by crawlers, quickly and without ambiguity?” The semantic audit answers: “Does each page target a clear intent, with unique, complete and well-structured content?” The first determines the second: working on the relevance of a page the engine does not index produces no measurable effect.

What roles do the crawl and Search Console play in an SEO audit?

The crawl gives a “machine” snapshot of the site: titles, depth, internal links, indexability, statuses, canonicals. Search Console connects pages and queries to metrics — impressions, clicks, CTR, average position — and lets you check whether a technical anomaly has a real effect on indexing. Both serve as evidence in the report; no recommendation should be without them.

How should fixes be prioritized after an SEO audit?

Use an impact × effort × risk logic, with a business filter on the pages that generate leads or revenue. Handle first what prevents the site from existing in the index, then what improves understanding (internal linking, structure, intent-to-page alignment), then the marginal optimizations on the pages that matter. This sequence allocates limited resources where the effect is measurable.

What comes up often in crawlers, but rarely changes rankings?

Often micro-optimizations on pages that are not indexed, tag variations on pages with no traffic, or marginal performance improvements on pages few people visit. Handle them if they pile up on a critical template; otherwise keep them for a later phase, so as to preserve resources for the work that has impact.

Where should you start to audit a website?

Clarify the objectives first — leads, sales, brand awareness — and the pages that carry the value. Then run a crawl for an exhaustive view, and cross it with Search Console and Analytics to connect anomalies and performance. This sequence limits false positives and allows prioritization from the start, instead of sorting thousands of alerts after the fact.

How often should an SEO audit be run, given the size and the stakes of the site?

After any creation, redesign, migration, structural change or change of directives, without delay. Beyond that, the cadence depends on context: a half-yearly analysis may be enough for a modest site; a fast-moving e-commerce site or a high-output editorial site justifies monthly KPI monitoring and an in-depth quarterly analysis. Even a small site is audited immediately after a CMS change.

Does the audit depend on the CMS in use (WordPress, Shopify, PrestaShop)?

No, the basic methodology does not depend on the CMS: an external crawl analyses pages as a robot sees them — URLs, internal links, statuses, tags, rendered content, directives and indexability. Solutions differ on the implementation of the fixes, but the diagnosis and the priorities remain comparable from one platform to another.

Which deliverables should you expect at the end of an SEO audit?

A structured report and a roadmap: findings, evidence, recommendations, prioritization, owners, risks and acceptance criteria. Length matters less than clarity and actionability. These deliverables and their date are contractually committed to, just like the scope audited.

How do you measure impact once the SEO fixes are implemented?

First check that the finding has disappeared, through a re-crawl and through the indexing reports. Then track indexed pages, crawl errors, impressions, clicks, CTR, rankings on a basket of queries and conversions. Annotate deployment dates to connect a variation to a change, and let several weeks pass before drawing conclusions on visibility.

Continue reading

• You have decided to audit and you want the order of operations, from framing to delivery: see how to perform an SEO audit step by step.
• You want to see the deliverable before ordering it: an SEO audit example run from end to end, with its reusable checklist.
• You execute in-house and need to equip yourself without multiplying sources: choosing and assembling SEO audit tools.
• You are outsourcing the audit and need to frame the contract: what to require from a supplier during an agency SEO audit, deliverables and acceptance included.
• Your site is a shop and the catalogue changes the checks: the e-commerce SEO audit covers categories, product pages, facets, variants and stock-outs.
• Your visibility plays out in one area rather than across a whole country: the local SEO audit covers local signals, NAP consistency, reviews and the business listing.
• External authority is the brake you suspect, not the site itself: the link building audit examines the inbound link profile and its quality.
• The fixes are shipped and you have to prove their effect over time: SEO tracking details KPIs, annotations and the control of gains.
• You are looking for a broader picture than a search diagnosis: the website analysis looks beyond SEO alone.
• The traffic is there and does not convert: the CRO audit tackles the conversion rate rather than visibility.
• The problem lies with the brand's image and not with its ranking: the e-reputation analysis examines what the SERP and the platforms say about it.