Migrating a Website Without Losing Your SEO
Migrating a website without losing your SEO rests on three pillars: keep the existing URLs as much as possible, set up 301 redirects for every page whose address changes, and check after migration that Google is properly indexing the new site. Done properly, a migration causes at worst a temporary dip of a few days to a few weeks, not a permanent loss.
Why migration is the riskiest moment for a website
A well-ranked site represents years of history, external links, indexed pages, and trust built up patiently in Google's eyes. That trust isn't attached to your design or even your host: it's attached to specific web addresses, the famous URLs. Changing site, CMS, or host without thinking about it is like asking Google to relearn everything from scratch.
That's why a poorly prepared redesign can cause organic traffic to drop by 30 to 50%, sometimes more, overnight. This isn't inevitable: it's almost always the result of a sloppy technical migration, not a content or design problem.
What triggers a migration
Several situations require migrating a site, with different levels of risk:
- Design redesign keeping the same URLs: low risk.
- CMS change (for example from a hand-coded site to WordPress, or vice versa): medium risk, since URL structures often change.
- Hosting change without content change: low risk if well executed.
- Domain name change: high risk, almost always accompanied by a temporary dip.
- Switching from HTTP to HTTPS: low risk today, this migration is well handled by search engines.
The common thread across all these situations: the more URLs change, the higher the risk of loss. This is the parameter to watch first, even before design or content.
The 8-step migration checklist
- List all existing URLs. A full map of the current site, page by page, with their exact address. Free site-crawling tools can generate this list automatically.
- Decide which pages are kept, merged, or removed. A redesign is also a chance to clean up outdated pages, but each removal should be deliberate, not accidental.
- Build the mapping table. For each old URL, note the new destination URL. This is the central document of the whole migration.
- Set up 301 redirects. One redirect per old page to its equivalent page on the new site, never a blanket redirect to the homepage.
- Keep the structure of titles and main content. Copy that worked well for SEO can be reused almost as-is, even with a new design.
- Check the robots.txt file and the XML sitemap. They must point to the new site and not block any important page.
- Submit the new sitemap in Search Console. This is the official signal sent to Google to speed up reindexing.
- Monitor traffic and 404 errors for the following 4 weeks. A temporary dip is normal, a worsening drop signals a redirect problem to fix quickly.
Page-by-page 301 redirects: why it's non-negotiable
The most common confusion is redirecting all old pages to the new homepage, thinking it's simpler. This is actually one of the worst practices in migration. Google interprets this as a loss of relevance: the page that talked about your consultation pricing, redirected to the homepage, no longer has anything to do with its original query.
Best practice is to redirect each old URL to the page closest in content on the new site. If a page has strictly no equivalent, it can stay as a clean 404 error rather than being artificially redirected — Google prefers an honest missing page to a misleading redirect.
Special case: changing your domain name
Changing domain (for example switching from "cabinet-dupont.fr" to "dupont-avocat.fr") is the trickiest migration. Even with perfect redirects, a temporary visibility dip is almost systematic, while Google associates accumulated trust with the new domain.
This migration should only be undertaken for a solid reason: company name change, legal requirement, business acquisition. A simple change of aesthetic taste doesn't justify this risk: it's possible to completely redo a site's design while keeping the same domain name and the same URLs.
How long the unsettled period lasts
| Type of migration | Expected traffic dip | Time to stabilize |
|---|---|---|
| Design redesign, URLs kept | Nearly none | A few days |
| CMS change, URLs modified with redirects | Slight, 5 to 15% | 2 to 4 weeks |
| Hosting change alone | None if done well | Immediate |
| HTTPS switch | None | A few days |
| Domain name change | 20 to 40% temporary | 4 to 8 weeks |
These figures are rough orders of magnitude generally observed, not a guarantee: each site reacts according to its history, its sector, and the quality of the migration's execution.
What to remember
- The main risk of a migration isn't the design, it's changing URLs without redirects.
- A 301 redirect should always point to the page closest in content, never to the homepage by default.
- Keeping the same URLs during a redesign reduces the risk of SEO loss to nearly zero.
- Changing your domain name is the riskiest migration: reserve it for genuinely justified cases.
- A traffic dip of a few days to a few weeks after migration is normal, a worsening dip signals a problem to fix.
- Submitting the new sitemap in Search Console speeds up reindexing by Google.
Frequently asked questions
How long does Google take to reindex a migrated site?
Generally between a few days and 4 to 6 weeks for most pages, if redirects are set up correctly. Some secondary pages can take longer. A temporary dip in the first 15 days is normal.
Do I always need 301 redirects?
Yes, as soon as URLs change. A 301 redirect tells Google and browsers that the page has permanently moved and passes on most of the accumulated SEO value to the new URL. Without it, every lost page starts from zero.
Can I migrate to a new domain name without losing my SEO?
It's possible but riskier than a standard technical migration. A domain change almost always causes a temporary dip, even when well executed. It's mainly justified in case of a company name change or a legal requirement.
What's the most common mistake during a migration?
Forgetting to recreate 301 redirects for every old URL, or changing URLs without a real need. A redesign that keeps the same page addresses considerably limits the risks, even if the design changes completely.
If you're preparing a redesign and want to avoid migration mistakes, check out the VeryAppi website plan, which includes the full technical setup, redirects included.
Frequently asked questions
›How long does Google take to reindex a migrated site?
Generally between a few days and 4 to 6 weeks for most pages, if redirects are set up correctly. Some secondary pages can take longer. A temporary dip in the first 15 days is normal.
›Do I always need 301 redirects?
Yes, as soon as URLs change. A 301 redirect tells Google and browsers that the page has permanently moved and passes on most of the accumulated SEO value to the new URL. Without it, every lost page starts from zero.
›Can I migrate to a new domain name without losing my SEO?
It's possible but riskier than a standard technical migration. A domain change almost always causes a temporary dip, even when well executed. It's mainly justified in case of a company name change or a legal requirement.
›What's the most common mistake during a migration?
Forgetting to recreate 301 redirects for every old URL, or changing URLs without a real need. A redesign that keeps the same page addresses considerably limits the risks, even if the design changes completely.