Site redesign: the 8 costly mistakes
· by the Agence Web Premium team, Guéliz Marrakech
Direct answer: the redesign is the moment when we lose the most SEO, and almost always for the same reason: forgotten 301 redirects. A 60-80% drop in traffic is common, and it's avoidable in a day's work.
We regularly recover sites whose traffic has collapsed after a redesign. In almost all cases, the cause is in this list.
Mistake 1 — Forgetting 301 Redirects
In short: Each old address must redirect to its new equivalent. Without this, you lose all the SEO acquired.
This is by far the most costly mistake. Your old pages are indexed by Google and receive inbound links. If their addresses change without redirection, all is lost.
The method: export the complete list of existing addresses before the redesign, then associate each one with its new destination. For deleted pages, redirect to the thematically closest page, not to the home page.
On a two hundred page site, this work takes a few hours. It avoids months of reconstruction.
Mistake 2 — Deleting unmatched content
In short: Pages that generated traffic should be retained or replaced with equivalent content, not deleted.
Before any redesign, pull out a list of your most visited pages over the last twelve months. These pages are assets.
Sometimes an old blog post generates half of a site's traffic without anyone knowing. Deleting it because it “looks old” is a serious mistake.
Mistake 3 — Leaving the development site indexable
In short: The pre-production site must be blocked. If it is indexed, it creates duplicate content with the actual site.
Common case: dev.mysite.ma ou mysite.netlify.app accessible and indexed. Google sees two identical sites and chooses which one to display — sometimes the wrong one.
Protection: password on the development environment, or explicit blocking in robots.txt. And verification after uploading that the old environment has been deindexed.
Mistake 4 — Forgetting to remove the index block
In short: The symmetry of the previous one: the new site is put online with the Disallow: / development still active.
The site is online, it looks good, it works — and Google doesn't see it. It can take weeks before anyone notices.
Verification in ten seconds: open yourdomain.my/robots.txt and search Disallow: /. Also check the presence of a beacon noindex in the source code.
Errors 5 to 8 — Common oversights
In short: Losing the title tags, breaking the internal link, forgetting the sitemap, and not monitoring after going live.
- 5. Lost titles and descriptions. The redesign often starts from a blank template and the optimized tags disappear. Export them first.
- 6. Broken internal mesh. Links between your pages point to old addresses. They work thanks to redirects, but it's a patch: fix them.
- 7. Sitemap not updated. The old sitemap references addresses that no longer exist. Regenerate it and submit it.
- 8. No post-launch monitoring. Problems appear within two weeks. Monitor Search Console daily for a month.
What if traffic has already collapsed?
In short: Identify old addresses that return a 404 error, place missing redirects, and request reindexing.
- Open Search Console, Indexing section, and list the pages with 404 errors.
- Recover your old addresses from a web archive or an old export if you have one.
- Apply 301 redirects missing to the equivalent pages.
- Submit the new sitemap and request indexing of the main pages.
- Wait. Recovery usually takes four to twelve weeks.
The good news: it's almost always recoverable. The bad: it takes months while prevention took a day.
The 8 errors, by severity
| # | Error | Impact on traffic | Prevention |
|---|---|---|---|
| 1 | Forgotten 301 redirects | −60 to −80% | Export addresses before |
| 2 | Deleted content without equivalent | −20 to −50% | List the most viewed pages |
| 3 | Indexed preproduction | duplicate content | Password or blocking |
| 4 | Disallow: / forgot | −100 % | Check robots.txt |
| 5 | Lost titles | −10 to −30% | Export front tags |
| 6 | Broken internal mesh | −5 to −15% | Fix internal links |
| 7 | Sitemap not updated | slow indexing | Regenerate and submit |
| 8 | No surveillance | detection delay | Search Console daily 1 month |
Orders of magnitude observed on poorly prepared overhauls, October 2026.
Frequently asked questions
Why did my traffic drop after the redesign?
In almost all cases: 301 redirects to old addresses have not been implemented.
What is a 301 redirect?
A permanent redirection which tells Google that the page has permanently moved, transferring its SEO.
Should it redirect to the home page?
No. Each old page should point to its thematic equivalent. Redirecting all to home is treated as a 404 error.
How long to recover traffic?
Four to twelve weeks after redirects are fixed.
How do I check my 404 errors?
In Search Console, Indexing section. It lists addresses known to Google that are no longer responding.
Should we keep the old URLs?
When possible, yes: it is the safest solution. Otherwise, redirect systematically.
How to prepare for a redesign correctly?
Export the list of addresses, titles and most visited pages before you start. Everything else follows from that.
Do you manage redesigns with migration?
Yes, including redirects. This is the step we deal with first, even before the design.
Redesign without losing your SEO
We export your addresses, we prepare the redirection plan, then we redo the site. In this order.
