Technical SEO: a website search engines can crawl, render and understand.
We carry out the technical fixes that keep your key pages from being found, then make sure they don’t come back with the next update.
A diagnosis isn’t enough. Fixes have to be made, then maintained.
A fix plan applied halfway rarely delivers half the result. And a website keeps evolving: new pages, plugins, theme updates. Every change can recreate a problem that was already solved.
Technical SEO covers the work that lets search engines reach, render, index and understand your pages. We start with the work affecting the pages tied to your business priorities.
Four questions, in this order.
There’s no point optimizing the speed of a page the search engine can’t reach. We follow this order.
Can crawlers reach the page?
A robots.txt file inherited from a test site, pages with no links at all, redirect chains.
Does the search engine see what the visitor sees?
Content loaded by script, a blocked resource, an element that only appears after an action.
Does it know which page answers what?
Pages competing for the same search, a poorly declared canonical page, language versions not properly linked.
Is the real-world experience good?
Heavy third-party scripts, unsized images, a slow server, especially on mobile.
The audit sets the order of the fixes. The technical mandate carries them out, verifies their effect and monitors for regressions.
The fixes, carried out and verified.
Each fix is clearly described: the page or file concerned, the expected behaviour and how to verify that it works.
- Crawling and indexing: sitemap, redirects, canonical pages, orphan pages.
- Pages built in JavaScript: checking what the search engine actually renders.
- Architecture and internal links: page depth, links between services.
- Structured data consistent with the visible content.
- Experience measured on real visits, on mobile as well as desktop.
- French and English versions properly linked, with no automatic redirect based on language.
A redesign is prepared before launch.
It’s the moment when a website most easily loses the visibility it had built. Four rules limit that risk.
A URL-by-URL mapping
Established before launch, based on the pages actually visited and found, not just the menu.
Direct redirects
Each old URL leads directly to its new destination, without going through a series of steps.
Redirects kept in place
They stay in place long after the switch, until search engines, bookmarks and external links catch up.
One change at a time
Changing the domain, design and content at the same time makes any drop hard to explain.
How we work on your website.
Baseline
The current state is recorded before any change, to compare and be able to roll back.
Prioritized fixes
Based on an existing audit or an initial review, according to the pages tied to your priorities.
Execution
Directly, or with your developer or provider. Your accounts stay in your name.
Verification
Each fix is checked after it goes live; those with no effect are flagged.
Surveillance
Updates and new pages are checked to prevent regressions.
Two ways of working, depending on your website.
| One-time audit | Ongoing technical mandate | |
|---|---|---|
| Goal | Establish the state of the website and the order of fixes | Carry out the fixes and prevent regressions |
| What’s delivered | Verified findings and a prioritized plan | Live changes, verified one by one |
| What’s needed on your side | Read access to your data | Publishing access or an available developer |
| What’s tracked | The findings retained and their priority | Indexed pages, searches won, leads received |
An ongoing mandate is justified for some websites only.
If your website is healthy and stable, an audit and a periodic review are often enough.
A website that changes or is complex
• Website built with a JavaScript framework
• Redesign or domain change planned
• Catalogue that generates URLs automatically
• Several people publish without technical review
• Bilingual or multi-regional website
A simple, stable website
• A few dozen pages that rarely change
• New pages crawled quickly
• The problem comes from content rather than technology
• Fixes from a previous audit haven’t been applied yet
Verifiable reports, not a ranking promise.
We compare each indicator with the baseline. The first visible effects are generally on the crawling and indexing side.
Pages crawled and indexed
Key pages kept by the search engine.
New pages picked up
The time between publishing a page and its being crawled.
Searches won
The distinct searches showing your priority pages.
Leads received
Contacts related to the targeted services.
Before and after the technical fixes.
SEO audit
Establish the state of the website and the order of fixes before carrying them out.
Search engine optimization (SEO)
See how technical SEO fits into the complete approach.
Frequently asked questions
The technical questions we’re asked most often.
What’s the difference between technical SEO and an SEO audit?
The audit diagnoses and ranks the fixes; it doesn’t fix anything. Technical SEO carries out those fixes and monitors the website over time.
Should we aim for a score of 90 or more in speed tools?
Not as a priority. Those scores come from simulations. What matters is the experience measured with your real visitors, especially on mobile.
My website is built in JavaScript. Is that a problem?
Not necessarily. Search engines can render JavaScript, but you need to check, page by page, that the important content really appears in what they see.
Should we block AI tools’ crawlers?
It depends on the crawler and your goal. Blocking those that feed AI answers can keep you from being cited in them. The decision is yours; we present the options and their effects.
Should visitors be redirected automatically based on their language?
No. It’s better to offer a visible choice and properly link the French and English versions of each page.
Key pages that search engines can’t find?
Tell us about your website, your platform and the planned changes. We’ll tell you whether a technical mandate is justified, or whether an audit is enough.
