Practical guide · 2026
A useful audit does not hand you a score and walk away. It locates the barriers, separates urgent work from improvements, and shows whether your website needs a focused fix, a structural change or a redesign.
The short answer
A website SEO audit examines three pillars: technical health, content and authority. It also checks whether traffic can turn into enquiries. Its purpose is to prioritise fixes by impact before work starts, instead of changing things at random.
Scope
Organic visibility never depends on one setting. A fast page can stay invisible when it answers the wrong question. An excellent article can stall when the site gives it no internal authority or leaves it isolated.
The audit therefore brings several readings into one diagnosis. It is not a search for theoretical perfection. It identifies the next changes most likely to improve Google visibility, answer-engine visibility and conversion.
| Pillar | Question | Checks | Output |
|---|---|---|---|
| Technical | Can search engines access and index the right pages? | Crawling, indexing, canonicals, redirects, sitemap, structure, Core Web Vitals and loading performance. | A short list of genuine blockers, kept separate from low-impact improvements. |
| Content | Does every page serve a clear search intent? | Titles, descriptions, H1s, topic depth, entities, missing pages, duplication, cannibalisation and freshness. | Page-level briefs with an angle, structure, evidence requirements and a measurable goal. |
| Authority | Does the site earn and distribute enough authority? | Backlinks, referring domains, anchors, internal links, orphan pages and consistency across topic clusters. | An internal-linking plan and, where needed, priorities for partnerships or digital PR. |
Decide before you build
Both. An audit should not simply confirm a decision that has already been made. It is the evidence used to choose between targeted corrections and a redesign.
Rebuilding without a baseline can remove pages that already earn impressions, break links and change URLs without redirects. Keeping an architecture that no longer makes sense can also trap a team in endless workarounds.
A focused correction is enough when the CMS remains usable, the structure still represents the offer, and the problems are concentrated in a few templates or pages.
A redesign becomes rational when every improvement needs a workaround, templates block clear information, or the architecture no longer represents the business.
The deliverable must make this choice explicit. If it recommends a redesign, it must also list the URLs to keep, merge or redirect. Otherwise the redesign is only a visual project with no SEO safety net.
Choose the right support
The best route depends less on website size than on available time, technical autonomy and the ability to implement recommendations.
For a team that can change its website and wants a structured reading before it starts work.
The cost is low, but the team must identify false positives and convert findings into useful tasks.
For teams keeping production in-house while getting help with order, briefs and difficult choices.
Progress depends on the internal team, but decisions stay documented and knowledge is transferred.
For businesses that want one team to own the diagnosis, implementation and measurement.
Useful access and approval points are still required, but responsibility for delivery is clear.
The three Atelier support levels start with the same diagnosis. They differ mainly in how much implementation is handled for you, not in whether the analysis is deliberately limited.
Compare support optionsSEO and answer engines
A traditional audit asks whether a page can rank. It should now also ask whether the information can be understood, attributed and reused in a concise answer.
This does not replace SEO. The same foundations still matter: accessible content, clear structure, explicit entities, evidence, sources and editorial consistency. The additional focus is on precise answers and on showing who is making each claim.
A page built from vague promises gives a system little to cite. A page that defines a concept, explains a method, dates its measurements and separates product limits from observed results is more useful to people and machines alike.
Expected output
A file containing one hundred alerts is not a plan. The deliverable should explain what is blocked, why it matters, what to change and how to verify that the change was actually deployed.
Crawl the website, read available Search Console data and record a baseline before any change.
Remove false positives, group symptoms that share a cause, and separate risks from opportunities.
Rank actions by impact, effort, dependencies and their proximity to the website’s commercial goal.
Confirm deployment, then compare impressions, clicks, position and business actions with the baseline.
Anonymised example
The preview below shows the shape of the deliverable: several dimensions, qualified issues and tracked progress. The figures are illustrative and the domain is anonymised.
A clear dashboard per site. Issues are ranked by impact so you know what to fix first.
Last audit 2 min ago · 214 pages analysed
Interface preview on a sample site. The percentages illustrate how an audit reads, they are not promised results. The score itself is recalculated on every new audit: fixing is what moves it, not an estimate.
Executive reading
Start with indicators that describe a loss or an actionable opportunity. The technical vocabulary can come second. A useful recommendation should make sense without opening the source code.
Check that important pages are known to Google and that unhelpful pages are not taking attention away from them.
Impressions show that a page is already entering the conversation. Queries show whether Google understands it as intended.
Read it by page and query, never on its own. A site-wide average mixes different intents and maturity levels.
A click validates the search result’s appeal. A booking, form or sale shows whether the page attracts the right audience.
Review sheet
This sheet summarises the questions to ask before accepting a diagnosis or starting a redesign. It fits on two pages and can be used in a meeting with your agency or technical team.
To continue, review the live results journal and the analyses published by the team. See measured SEO results · Read the blog · Explore the diagnosis
A small site can be analysed in a few hours, but qualifying causes and building the plan takes longer. A serious audit states its scope, limitations and data date.
Start with a baseline
Run the diagnosis to get an initial reading. The findings can then guide the right level of support, without assuming that a redesign is necessary.