Crawlability & indexing
Robots, sitemaps, HTTP status, canonicals, depth and the pages Google can actually discover.
The starting point
The Atelier analyses your website across more than 90 checks, shows the affected pages and turns findings into priorities. Your workspace can then connect competitors, AI visibility and Google data.
Short answer
The audit runs your website through more than 90 checks. They fall into four families: crawlability and indexing, on-page and structured data, performance and experience, priorities and evidence. It returns problems ranked by impact, each tied to the affected URLs and to an action. It is written for the owner who has to decide what to fix first.
What is actually checked
Each family answers a precise question and keeps the evidence needed to verify the finding.
Robots, sitemaps, HTTP status, canonicals, depth and the pages Google can actually discover.
Titles, descriptions, hierarchy, content, internal links and Schema.org markup.
Core Web Vitals, resource weight, images, visual stability and issues observed across templates.
Severity, affected URLs, risk explanation and a correction order instead of a raw problem list.
The checks in detail
The points below are verified by the audit on your own website. They show the level of detail returned, not a result announced in advance.
The audit reads your robots.txt, your sitemap and the response returned by every address it visits.
What a detected problem reveals
A blockage here does not cost positions. It costs indexing: the page never enters the race.
The audit compares the title shown in Google, the title visible on the page and the subject actually covered.
What a detected problem reveals
A duplicated or truncated title shows up in the click-through rate before it shows up in the position.
The audit measures the real weight of your pages, then compares that measurement with your visitors' own when Google provides it.
What a detected problem reveals
A slow page does not only lose rankings. It loses the visitor before being read at all.
A finding never arrives alone. It comes with its severity, the affected addresses and the order in which to handle it.
What a detected problem reveals
A list of problems is read in an hour. A correction order is put to work the next day.
Decide before you build
The audit should not confirm a decision that has already been made. It uses verifiable evidence to choose between targeted corrections and a redesign.
Fix
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.
Redesign
A redesign becomes rational when every improvement needs a workaround, templates block clear information, or the architecture no longer represents the business.
The threshold
Three criteria can be observed without technical expertise. Place your website on each row, then look at the column that comes back most often.
| Observable criterion | FixThe foundation still holds | Tipping zoneBoth cases stand up | RebuildThe website is the ceiling |
|---|---|---|---|
| Major technical blockers | One or two, on identified templates. | Three to five, each one still workable around. | More than five, or a single one rooted in the CMS itself. |
| Age of the technical foundation | Under three years, the CMS still keeps up. | Three to six years, every update takes time. | Over six years, or a CMS nobody maintains any more. |
| Ability to carry a new offer | A new page ships without a developer. | A developer is needed, not a rebuild. | Every addition goes through a workaround. |
| What the audit shows month after month | Corrections hold once they are applied. | Corrections hold, but the list never gets shorter. | The same problems return without the cause being removed. |
Two rows out of three on the same side are enough to decide. When the right-hand column wins, the formula with a redesign included becomes the logical next step rather than a run of corrections.
If a redesign is recommended, the plan must list the URLs to keep, merge or redirect. Otherwise the redesign remains a visual project with no SEO safety net.
To go further: compare the three formulas, see how a redesign unfolds, prepare the SEO migration URL by URL, the 12 points to check before rebuilding a website, choose between in-house work, an agency and a rebuild.
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.
After the diagnostic
Iris can then connect the findings with your competitors, Google and AI-engine visibility, plus Search Console and Analytics data when connected.
Iris isn't a generic chatbot. She's connected to your audit: your pages, your competitors, your performance and your history. Her answers are grounded in your data.
Sample conversation on a fictional site. It shows the format of Iris answers, the figures announce no gain.
See exactly what your competitors do better than you: the keywords they capture and you don't, their content, their structure and the gaps to close.
SEO alone no longer cuts it. Atelier SEO also measures your GEO are you cited by ChatGPT, Perplexity and Google's AI Overviews? If not, we tell you how to get there.
Iris turns the audit into a roadmap: technical fixes, content to create, priorities by impact. Then you watch your scores move month after month.
Connect Google Search Console and Analytics: the audit picks up your actual traffic and performance.
Made for everyone whether you run one site or a hundred.
Review sheet
Two pages for checking a diagnosis before accepting its recommendations or starting a redesign.
Yes. The first technical diagnostic starts without a payment card or account. Paid offers cover ongoing access with support and the human work delivered by La Refonte.
Your baseline
Run the first audit, then explore the findings in your own workspace.