Baisse de trafic google : solutions après une refonte de site
- A drop in traffic after a redesign is common, but it's not inevitable: some are normal and temporary, while others reveal serious errors that need to be dealt with urgently.
- The absence of 301 redirects on old URLs is, by far, the most devastating cause of post-redesign traffic loss.
- A site launched in production with a blocking robots.txt file or active noindex tags can disappear from Google in a matter of days: this is the first thing to check.
- Google Search Console and Screaming Frog are the two essential tools for accurately diagnosing the origin of the drop.
- The first 48 hours after the drop is detected are decisive: every hour of inaction worsens the situation.
- The best protection against a post-redesign SEO disaster is an SEO audit carried out before launch, not after.
- Traffic recovery can take from a few weeks to several months, depending on the nature and extent of the errors made.
I'm going to describe a situation I'm unfortunately very familiar with: you've invested time, energy and often a substantial budget in redesigning your website. The new design is beautiful, the navigation more fluid, you're proud of the result. And then, a few days or weeks after the launch, you open Google Analytics and see the traffic curve plummet. Sometimes abruptly. Sometimes gradually, but inexorably. That moment, I can tell you, is particularly unsettling, especially when you don't understand why.
Redesigning a website is one of the riskiest operations from an SEO point of view. Not because it's bad in itself, but because it concentrates in a very short time a multitude of changes that can, if certain precautions aren't taken, profoundly disorientate Google and bring down years of accumulated SEO work. In this article, I'm going to explain why this happens, how to diagnose the problem, what to do urgently, and above all how to prevent it from happening again. Hang on: we're going to go fast, because in your situation, time is against you.
Is a drop in traffic after a redesign normal?
This is the first question most people in your situation ask themselves. And I understand the need for a clear answer before deciding what level of alarm to trigger. The truth is, there's no binary answer to this question: it depends on the amplitude of the decline, its speed, and what really changed during the redesign.
The algorithmic «digestion» period
When Google discovers that a site has changed radically, it needs a period of adaptation to re-evaluate the content, structure and quality signals of the new site. This is what I call the algorithmic digestion period. During this phase, which can last from a few days to several weeks, Google recrawls pages, reassesses their relevance, and recalculates positions. It is therefore normal to observe a certain volatility in positions, even a slight temporary drop, in the two to four weeks following a launch.
My opinion on this is nuanced: a 10 to 20 % drop in organic traffic in the first two weeks post-redesign, with no other anomalies detected, is often within the normal fluctuation range. It's not pleasant, but it's not catastrophic. On the other hand, a drop of 40, 50 or 80 % in traffic in the space of a few days is a sign of one or more serious technical errors requiring immediate action.
How much of a drop is acceptable, and how much is cause for alarm?
Here are the thresholds I personally use to assess the level of urgency of a post-rework situation:
After a redesign, a drop in Google traffic can be confirmed by Google Analytics, then we have to act fast.
| Depreciation amplitude | Alert level | Probable interpretation |
|---|---|---|
| Less than 15 % | 🟢 Normal | Fluctuating algorithmic digestion, to be monitored |
| 15 % to 30 % | 🟡 Vigilance | Possible technical error or modified content, to be diagnosed |
| 30 % to 60 % | 🟠 Urgent | Significant SEO errors, likely missing redirects |
| Over 60 % | 🔴 review | Major error: noindex, robots.txt blocking, or no redirects at all |
Expected time to stabilization by type of redesign
A purely graphic redesign, with no changes to URLs or content, rarely generates more than a few weeks' fluctuation. On the other hand, a redesign with changes to domain, CMS, URL structure and content can take several months before Google has fully reassessed and restabilized positions. The duration of stabilization is directly proportional to the extent of the changes made.
A drop in traffic after a redesign may mean that your site is penalized by Google, requiring immediate verification.
The types of redesign that do the most damage to SEO
In descending order of danger, here are the types of redesign that present the greatest risks for SEO: domain name change, migration to a new CMS with complete URL restructuring, massive editorial redesign with deletion or rewriting of positioned content, and finally graphic redesign with a change of theme that degrades technical performance. Each of these scenarios has its own specific risks, which I'll detail in the next section.
The most common SEO mistakes made during a redesign
Now that you've assessed the severity of your situation, let's get into the causes. In my experience, the most severe post-redesign traffic drops are almost always attributable to a small number of recurring errors. Here they are, in order of the impact they can have on your traffic.
To analyze a drop in Google traffic after a redesign, Google Analytics is essential to identify problems.
Changing URLs without 301 redirects: the No. 1 cause of post-redesign disasters
This is by far the most frequent and devastating mistake. When you modify the structure of your URLs during a redesign (which happens in almost all cases), the old URLs continue to exist in Google's index, in the backlinks pointing to your site, and in your visitors« bookmarks. If you haven't set up 301 redirects (»permanent redirects") that automatically send visitors and Google to the corresponding new URLs, all these old addresses will return a 404 error, i.e. a non-existent page.
If your Google traffic has dropped after a redesign, it's essential to understand quickly why your site has lost Google traffic.
The result is brutal: Google progressively de-indexes the pages in error, you lose the «SEO juice» accumulated on your old URLs, and your backlinks become inoperative. It's like moving house without leaving a forwarding address with the Post Office: everything that was intended for you disappears into nothingness.
Mass modification of title and meta description tags
When redesigning a site, it's tempting to rethink everything, including the SEO tags on the pages. And this is often a good idea in principle. But if this rewriting is carried out en masse, without prior analysis of the pages that were generating traffic thanks to their existing tags, you run the risk of deposting pages that were working perfectly well. Google takes time to re-evaluate new tags, and during this transition period, your positions can fluctuate significantly.
Deleting or rewriting well-positioned content
It's a mistake I see regularly, and it saddens me every time. In the enthusiasm of a redesign, people decide to «clean up» the site, deleting old articles deemed obsolete, merging pages, or completely rewriting content without looking to see if it was generating traffic. The result is the outright destruction of SEO capital, sometimes built up over several years. Before deleting or rewriting anything, systematically check the organic traffic of each page in Google Search Console.
Changes to navigation structure and internal meshing
Internal linking is the set of links that link your pages together. It plays a crucial role in the way Google distributes authority within your site, and in the ease with which Googlebot crawls your content. A redesign that radically alters navigation, removes important internal links, or creates orphan pages (with no inbound links from the rest of the site), can significantly disrupt Google's exploration and evaluation of your site.
HTTP to HTTPS migration poorly executed
If your redesign was also an opportunity to move your site to HTTPS (which is a good decision in itself), a poorly executed migration can create additional problems. HTTP and HTTPS URLs are technically different for Google. If HTTP to HTTPS redirects aren't set up correctly, you could end up with duplicate content between the two versions, or with backlinks still pointing to unredirected HTTP URLs.
A drop in traffic after a redesign may be due to a Google penalty, so you need to know how to get out of a penalized site.
Changing CMS or front-end technology
Migrating from WordPress to another platform, or adopting a JavaScript framework such as React or Vue.js for the front-end, can create indexability problems if not done with care. Google has varying difficulties crawling and indexing sites built entirely in client-side JavaScript, especially those that rely on client-side rendering (CSR) without a server-side rendering (SSR) solution. This is a technical issue, but it can have major consequences for your site's visibility.
Changing domain names without a migration strategy
This is the riskiest scenario of all. In Google's eyes, a domain name change is the creation of a completely new site. All the history, authority and SEO capital of the old domain must be transferred to the new one via an exhaustive redirect plan and a change of address declaration in Google Search Console. Without these steps, you're starting from scratch, and recovery can take months or even years.
| Mistakes made | SEO impact | Severity level |
|---|---|---|
| No 301 redirects | Loss of positions and backlinks on all modified URLs | 🔴 review |
| Site launched with noindex or robots.txt blocking | Partial or total de-indexing of the new site | 🔴 review |
| Domain change without migration | Total loss of accumulated SEO capital | 🔴 review |
| Deleting positioned content | Loss of traffic proportional to pages deleted | 🟠 Urgent |
| Massive rewriting of title tags | Position volatility during revaluation | 🟠 Urgent |
| Disorganized internal network | Decreased exploration and distribution of authority | 🟡 Important |
| Incomplete HTTPS migration | Duplicate content, ineffective backlinks | 🟡 Important |
| Changing CMS with non-indexable JavaScript | Partial or no indexing of new pages | 🟠 Urgent |
Post-launch technical errors that exacerbate the downturn
Beyond the conceptual mistakes made during the redesign, there are a series of technical problems that frequently occur at the time of the launch itself, and which can turn a moderate decline into an SEO disaster. These errors are often the easiest to correct, but it's important to catch them early.
Site launched in production with «noindex» or robots.txt mode blocked
This is the mistake I call «the silent time bomb». During the development of a new site in staging (test environment), it's common practice to block indexing to prevent Google from crawling a site under construction. The problem is that this restriction is often not deactivated before the site goes live. The site is launched, it seems to work perfectly from the user's point of view, but Google can't index it.
In WordPress, this option is found in Settings > Reading > «Discourage search engines from indexing this site». A simple checkbox, which can destroy months of SEO work if you forget to uncheck it at launch. Check this as an absolute priority.
XML sitemap not updated or not submitted after redesign
The XML sitemap is the document that lists all the URLs on your site, and which you submit to Google for easy crawling. After a redesign, this sitemap must be regenerated to reflect the new site structure, and resubmitted to Google Search Console. An obsolete sitemap listing URLs that no longer exist is useless, even counter-productive. Make sure your sitemap is up to date and submitted to Search Console immediately after launch.
Orphan pages: content no longer accessible
An orphan page is a page that exists on your site, but is not accessible via any internal link. It may be indexed by Google if it was included in your old sitemap, but with no internal links pointing to it, it will receive no authority from the rest of the site, and will be progressively de-prioritized in Googlebot's crawl. Redesigns often create dozens of orphan pages, particularly when the navigation is redesigned without prior auditing of the existing internal mesh.
404 errors generated by old, non-redirected URLs
I've already talked about this in the context of 301 redirects, but I want to emphasize the cumulative impact of 404 errors. Each URL in 404 error means a page that Google will progressively de-index, a backlink that becomes inoperative, and a visitor who lands on a blank page instead of the content they were looking for. On a medium-sized site, a redesign without a redirect plan can generate hundreds, if not thousands, of 404 errors. Search Console lists them all in its «Coverage» report: this is your first destination when you notice a drop in traffic.
Core Web Vitals deteriorate with the new design
A new theme, new animations, heavier images, custom fonts loaded from external CDNs, a homepage slider: all visually appealing elements that can significantly degrade a site's technical performance and therefore its Core Web Vitals. Since 2021, these metrics have been an official ranking factor. A site that was «Good» on PageSpeed Insights before the redesign and drops to «Needs Improvement» or «Poor» afterwards may lose positions, particularly on mobile. Test your new site on PageSpeed Insights right from the start.
Misconfigured canonical tags
Canonical tags tell Google which is the reference version of a page when several URLs point to similar content. Misconfiguration of these tags, which is common in CMS migrations, can create duplicate content situations that disrupt indexing and dilute the authority of your pages. Check that your new site's canonicals point to the right URLs, and not to old URLs or to the staging version of the site.
How to accurately diagnose the origin of the decline
You now have a good overview of potential problems. Let's move on to the actual diagnosis. I'm going to give you the protocol I personally apply during a post-redesign analysis, with the tools to be used at each stage. Order counts: start with the quickest and most critical checks.
Data to consult in Google Search Console
Open Google Search Console and consult, in this order: the «Coverage» report to identify pages in 404 error, excluded pages, and any crawl errors; the «Performance» report, comparing the periods before and after launch to identify the pages and queries most affected; and the «Page Experience» report to check the evolution of your Core Web Vitals. These three reports already give you a precise mapping of the situation in less than an hour.
Identify the most affected pages and keywords
In the Search Console «Performance» report, activate period comparison (before and after launch), sort by click difference, and identify the 20 pages that have lost the most. For each of these pages, check if the URL has changed, if the content has been modified, and if a redirect is in place from the old URL. This granularity work is essential to prioritize corrections.
Auditing redirects with Screaming Frog
Screaming Frog is SEO auditing software (free for up to 500 URLs) that crawls your site in exactly the same way as Googlebot. Once the crawl is complete, export the list of 404 errors and check for each one whether a 301 redirect to the corresponding new URL is in place. At the same time, import your list of old URLs (which you should have saved before the redesign) and check their status: 200 (OK), 301 (redirected), or 404 (error). Every 404 on an old indexed URL is a priority for correction.
Check the actual indexing of the new site vs. the old one
Type «site:votredomaine.fr» into Google and compare the number of indexed pages to what you had before the redesign. If the number has dropped drastically, it's the signal of a major indexing problem: blocking robots.txt, noindex tags, or mass orphan pages. A drop of 30 % or more in the number of indexed pages warrants immediate investigation in Search Console.
Compare Core Web Vitals before and after the redesign
If you've thought of doing a PageSpeed Insights test before launching (which I always recommend), compare the scores obtained on the site's main pages before and after. A significant deterioration in LCP, CLS or INP is a signal to be dealt with, even if it's not the main cause of the drop. These metrics affect rankings on a cumulative basis.
Cross-reference launch date with traffic curve
In Google Analytics, pinpoint the day when traffic began to fall, and cross-reference this date with the launch date of the new site. If the drop coincides with the launch, the causal link is almost certain. If the drop began a few days later, this may indicate that Google took some time to crawl the new site before detecting the problems.
The emergency action plan: what to do in the first 48 hours
The diagnosis is made. Now it's time for action. I'm going to give you the steps in exact order of priority. Don't spread yourself too thinly: deal with the most critical problems first, before tackling the finer points of optimization.
Check and correct robots.txt and noindex tags as a top priority
This is the first check you need to make, before anything else. Open your robots.txt file (votresite.fr/robots.txt) and check that it doesn't contain a «Disallow: /» directive that would block the entire site. In WordPress, check that the «Discourage search engines» option is deactivated in Settings > Reading. And check via the «URL Inspection» tool in Search Console that your main pages are indeed declared as indexable. If you find any of these blockages, correct them immediately: it's an absolute emergency.
Audit and correct missing redirects on strategic URLs
Using your Screaming Frog audit and Search Console analysis, draw up a list of the old strategic URLs (those that generated the most traffic) that return a 404 error. For each one, set up a 301 redirect to the corresponding new URL. Start with the pages that generated the most traffic and the most backlinks. If you're using WordPress, plugins like Redirection or Yoast SEO Premium can handle this without touching the code.
Submit new sitemap to Google Search Console
Generate a fresh XML sitemap that reflects your site's new structure, and submit it to Google Search Console («Sitemaps» section). This invites Google to recrawl your site with the new URLs as soon as possible. It's a quick and easy action, which can significantly speed up the reindexing of your new site.
Request reindexing of priority pages
For your most important pages (home page, service pages, category pages, most traffic-generating articles), use the «URL Inspection» tool in Search Console to manually request their reindexation. Google will give these requests priority over the organic crawl. Please note: this tool is limited to a few dozen requests per day, so reserve it for really high-priority pages.
Identify and correct critical 404 errors
Once the redirections of strategic pages are in place, tackle the 404 errors found in Search Console. Sort them by decreasing number of impressions, and redirect as a priority those that had the most visibility in Google. 404 errors on pages that had no impressions before the redesign are less urgent and can be dealt with at a later date.
Notify Google of migration if domain change
If your redesign has included a change of domain name, use the «Change of address» tool available in Google Search Console (in the old domain's ownership settings). This tool officially informs Google that your site has migrated to a new domain, and speeds up the transfer of SEO authority between the two. It's a step that's often overlooked, yet crucial to the speed of recovery.
What to anticipate before any redesign to protect your SEO
I'm now going to address two types of readers simultaneously: those who are currently experiencing a post-redesign downturn, and who will find in this section the basics to never experience this situation again, and those who are planning a future redesign and are fortunate enough to be able to protect themselves in advance. In my opinion, this is the most valuable section of the article.
The SEO pre-foundation audit: mapping what works
Before you touch anything on your existing site, carry out a complete SEO audit that documents the current state: list of all indexed URLs, current positions on strategic keywords, pages that generate the most traffic, most important backlinks, and internal mesh structure. This document is your compass for the duration of the redesign. It lets you know what absolutely must be preserved, and what can be modified without risk.
Save the complete list of indexed URLs
Export from Google Search Console the complete list of all your indexed URLs, with their associated clicks and impressions. This file is essential for building the redirect plan. Each URL that appears in this list and that will change during the redesign must have its 301 redirect planned before launch. Without this list, you'll be working in the dark, and you risk forgetting important pages.
Prepare redirection plan before launch, not after
The redirect plan is a document that maps each old URL to its new equivalent URL. It must be prepared, validated and tested before the launch of the new site, not in reaction to a drop in traffic observed afterwards. It's a technical document, yes, but it's one of the most important pieces of SEO capital preservation during a redesign.
Staging the site before going live
The staging environment is the test version of your new site, inaccessible to the public and to Google. This is where you need to carry out all the SEO checks before launching: check noindex tags (which must be active in staging and deactivated in production), test redirects, audit title tags, check internal linking, and test Core Web Vitals. A launch without staging validation is a leap in the dark.
A 90-day post-launch monitoring plan
The launch is not the end of the process, it's the beginning of a period of active monitoring. For the first 90 days after a redesign, I recommend consulting Search Console at least twice a week, monitoring the positions of the most strategic pages on a daily basis via a rank-tracking tool (such as SE Ranking or Semrush), and regularly checking for new 404 errors or indexing problems.
Involve an SEO consultant in the design phase
This is the advice I would give first and foremost to anyone planning a redesign with significant SEO stakes. An SEO consultant involved right from the design phase can avoid almost all the mistakes I've just described. His role is not to do the developer's or designer's work, but to define the SEO constraints to be respected and to validate that the new architecture, new URLs and new content don't run counter to existing gains. It's a preventive expense that's far less worthwhile than a curative post-disaster intervention.
Traffic recovery: what to expect and when?
Once the emergency corrections have been made, the question on everyone's lips is inevitable: when will I get my traffic back? I'll give you an honest answer, without false optimism or unnecessary pessimism.
Rapid recovery scenarios
Recovery in less than two months is possible, and even likely, in the following cases: the decline was mainly caused by a simple technical block (noindex or robots.txt), which was quickly corrected; missing redirects were implemented within the first few days after launch; and content and SEO tags were substantially preserved. In these scenarios, once the corrections have been made and the site recrawled by Google, positions gradually return to their pre-redesign levels.
Long recovery scenarios
A recovery of 6 months to 1 year, or more, is to be anticipated when errors have been significant and have lasted several weeks before being corrected, when content has been massively rewritten or deleted, or when a domain change has been poorly executed. In these cases, recovery is not automatic: it requires active editorial work (enriching content, creating new articles), a netlinking strategy to reconstitute the link profile, and rigorous monitoring of progress indicators.
Cases where traffic never returns without major intervention
I'm going to be straight with you: in certain cases, particularly when a domain change has been carried out without any migration strategy and several months have passed, the SEO capital of the old domain can be considered lost. Recovery then becomes reconstruction, not restoration. It's a painful situation, but it's not a dead end: with sustained, methodical work, it's possible to rebuild solid visibility, but you have to accept that it takes time.
How to speed up recovery
Several levers can speed up the recovery of traffic after a redesign. Regularly publishing new quality content signals to Google that the site is active and dynamic. Relaunch a link building strategy to reconstitute the lost link profile. Optimize the pages that have lost the most by enriching their content and strengthening their internal links. And regularly request the reindexing of priority pages via Search Console, at the rate authorized by the tool.
Indicators to watch out for to know if recovery is underway
The positive signs I'm seeing to confirm that a recovery is underway are: a gradual increase in the number of impressions in Search Console, even before an increase in clicks; a decrease in the number of 404 errors in the Coverage report; a gradual return to positions on strategic queries, first on the second page of Google, then on the first; and an increase in the number of indexed pages that is approaching the level before the redesign.
Redesign and SEO: best practices to ensure you never go through this again
For those who have experienced a loss of traffic post-redesign, there is often a before and an after. A before when SEO wasn't thought of as a design constraint, and an after when you can't imagine launching a new site without checking off every point on a rigorous checklist. Here are the practices I consider non-negotiable.
Integrate SEO into redesign specifications from the outset
SEO shouldn't be an afterthought. It should be a design constraint, just like accessibility or performance. When you draw up the specifications for your redesign, explicitly include SEO requirements: preservation of existing URLs or redirect plan, maintenance or improvement of Core Web Vitals, tag structure respected, XML sitemap automatically generated, etc.
Choose an agency or service provider that understands SEO issues
Not all web agencies are equal when it comes to SEO sensitivity. Some excel in design and development, but treat SEO as a secondary option. Before entrusting your redesign to a provider, ask them explicitly about their process for preserving SEO during migrations. If they can't give you a detailed and convincing answer, that's a red flag.
10 SEO checkpoints to validate before any launch
- The robots.txt file is correctly configured and does not block Googlebot.
- Noindex tags are disabled on all production pages.
- The XML sitemap is generated, up to date and accessible.
- All planned 301 redirects are in place and tested.
- Title and meta description tags are included on all important pages.
- Canonical tags point to the right URLs.
- The HTTPS certificate is active and HTTP > HTTPS redirects work.
- Core Web Vitals are in the «Good» thresholds on mobile and desktop.
- The internal linkage is coherent, and no strategic page is orphaned.
- The sitemap is submitted to Google Search Console immediately after launch.
Set up continuous monitoring after the launch
Once the site has been launched and the initial checks carried out, don't relax your monitoring. Set up alerts in Google Search Console to be notified of any sudden increase in crawl errors. Track your positions on strategic queries daily for the first 30 days. And schedule a full audit at 30 days, then at 90 days, to check that everything's in order.
When to call in an SEO consultant after a failed redesign?
I'll answer this question with all the frankness you deserve. There are situations where self-diagnosis and self-correction are quite sufficient. And there are situations where persisting alone is a mistake that costs you visitors, contacts and sales every week.
Situations where self-diagnosis reaches its limits
If you've carried out the basic checks described in this article and can't find the cause of the drop, if the fall exceeds 50 % in traffic and obvious fixes haven't been enough to reverse the trend, or if your redesign has involved a change of domain, a complex CMS migration, or a switch to JavaScript technology: in all these cases, the expertise of an experienced SEO consultant can make a decisive difference.
What a consultant can do for you
An SEO consultant with experience of post-redesign audits will be able to identify problems in a matter of hours that would have taken you weeks to find on your own. He brings not only the technical expertise to diagnose the root causes, but also the experience of similar scenarios to propose a structured and prioritized recovery plan. In a situation where every week of downtime has a measurable cost, this time-saving can represent a substantial saving.
How to choose the right profile according to the seriousness of the situation
For an emergency post-redesign situation, look for a consultant with specific experience of SEO migrations and technical audits, not just an expert in content or editorial strategy. Ask for concrete examples of similar situations they've dealt with, the recovery times they've achieved, and their intervention process. A good consultant will be able to give you a clear vision of the situation and a realistic action plan from the very first hour of the audit.
If you feel that your situation requires an expert eye. I'll be able to offer you a precise diagnosis and an action plan tailored to your specific case, as quickly as possible.
Things to remember before closing this article
A drop in traffic after a redesign is an ordeal, I'm not going to hide it from you. But it's also, very often, a formative experience that permanently transforms the way we approach web projects. In my experience, the professionals who have experienced a post-redesign SEO disaster are the ones who become the most rigorous in their future processes.
analyze the causes of traffic decline
There are five key points to keep in mind: first, check that your site is not blocked for indexing; audit your 301 redirects immediately; submit your new sitemap without delay; diagnose precisely which pages and queries are affected before making corrections in all directions; and measure the impact of each correction to know whether you're going in the right direction. Here, more than anywhere else, method is your best ally.
Personalized, no-obligation analysis, response within 24/48 hours with 3-5 concrete quick wins.
150 entrepreneurs have already put their trust in us
🔒 Your data is never shared with third parties
