To migrate your website without losing SEO rankings, map every old URL to its new equivalent with a permanent 301 redirect, keep the same content and heading structure, launch during low-traffic hours, and monitor indexing in Search Console for the following weeks. A clean migration loses 5% to 15% of traffic temporarily and recovers the previous level within 2 to 4 weeks. A bad migration can erase 50% of your organic traffic permanently. The difference almost always comes down to the redirect map.
At Deepyze we migrate sites for LATAM SMBs and startups every week: redesigns, platform changes (WordPress to Next.js, Wix to something custom), domain changes, and consolidations. This guide is the actual checklist we use.
Why sites lose rankings during a migration (and when they shouldn't)
Your rankings don't live on your server: they live in Google's index, tied to specific URLs. When you change something that affects those URLs without telling Google how to connect the old to the new, Google has to relearn your site from scratch. During that relearning, you lose visibility.
The most common causes of a drop aren't mysterious:
| Cause | Typical impact | Avoidable |
|---|---|---|
| URLs changed without a 301 redirect | 30-60% drop, permanent | Yes, 100% |
| Redirect chains (A→B→C) | Lost authority and speed | Yes |
| Content trimmed or rewritten in the migration | Drop from lost relevance | Yes |
| Accidental robots.txt block or noindex | Full deindexing | Yes |
| Old sitemap left unchanged | Slow reindexing | Yes |
| Speed / Core Web Vitals regression | Gradual ranking decline | Yes |
Notice the last column says "Yes" on every row. Losing SEO during a migration is not an unavoidable risk: it's the result of skipping steps.
Step by step: how to migrate your site without losing SEO
1. Build a complete inventory of your current URLs
Before you touch anything, you need to know what you have. Export:
- Every indexed URL (Search Console → Pages, or a crawl with Screaming Frog).
- The URLs that receive organic traffic (Search Console → Performance, last 12 months).
- The URLs with external backlinks (Ahrefs, Semrush, or the Search Console links report).
The pages that appear on all three lists are your SEO assets. Those are the ones you cannot afford to lose.
2. Define the redirect map (old URL → new URL)
This is the heart of the migration. A spreadsheet with two columns: each old URL pointing to its most relevant new URL. Not the homepage: the equivalent page. If an old page has no equivalent, redirect it to the closest parent category, never to a 404.
3. Implement 301 (permanent) redirects, not 302s
A 301 tells Google "this moved for good" and passes the authority. A 302 says "this is temporary" and won't consolidate the signals as fast. Always use 301 for permanent migrations.
Avoid redirect chains: if URL A redirects to B and B to C, fix A so it points straight to C.
Is your migration touching hundreds of URLs, e-commerce, or a domain change? A bad redirect map costs months of traffic. Book a free intro call and we'll review your case before you launch.
4. Preserve your on-page elements
On the new site, replicate for each migrated page:
- The same title and meta description (or better, but with the same keywords).
- The same H1/H2 heading structure.
- The full content: don't trim text "to make it look cleaner." Google rewards depth.
- Images with their alt text.
- Any structured data (schema) you already had.
5. Check the technical setup before publishing
Deployment checklist:
robots.txtdoesn't block anything important.- No key page has a stray
noindextag (the #1 mistake when going from staging to production). - Canonical tags point to the correct new URLs.
- The sitemap.xml is updated with the new URLs.
- HTTPS works and there's no mixed content.
- hreflang tags (if you run ES/EN) point to the new URLs.
If your new site is built on a modern architecture, some of this is handled for you. That's how we build our web development projects: sitemap, canonicals, and hreflang generated at build time, not by hand.
6. Launch, submit the sitemap, and monitor
Publish during low-traffic hours. As soon as it's live:
- Submit the new sitemap in Search Console.
- Use URL Inspection on your 10-20 most important pages and request indexing.
- Keep the old domain (if you changed domains) with active redirects for at least 6 months, ideally a year.
The first 4 weeks: what to monitor
The migration doesn't end when you publish. It ends when you confirm Google has consolidated the change.
| Week | What to check | Warning sign |
|---|---|---|
| Days 1-3 | Crawl errors, 404s, coverage in Search Console | Spike in 404s or "excluded" |
| Week 1 | Indexed pages vs. submitted | Under 70% indexed |
| Week 2 | Organic traffic and top positions | Drop greater than 20% |
| Week 4 | Traffic recovery | No recovery = check redirects |
A 10-15% drop in the first two weeks is normal and expected. If traffic hasn't recovered after 4 weeks, the problem is almost always a broken redirect, a page stuck on noindex, or a block of unmapped URLs.
When migrating your site does NOT make sense
Not every change justifies a migration and its associated risk:
- You just want a nicer design and your URLs already rank well. Redesign while keeping the exact same URLs. That's not an SEO migration, it's a template change, and the risk is minimal.
- Your site is 3 months old with almost no organic traffic. You have little to lose and lots of room to start right. Go for it, but prioritize building it well from the start.
- You want a new domain "because it sounds better." A domain change always carries a temporary SEO cost. Without a strong business reason (rebranding, merger, legal issue), don't do it for aesthetics alone.
- You're in peak sales season. Never migrate an e-commerce site a week before Black Friday or a big sale. Wait for the slow season.
If your case is a redesign that also needs new logic (catalog, bookings, an internal dashboard), it often makes sense to frame it as a custom software or e-commerce project where the SEO migration is planned from day one, not patched in at the end.
The mistake we see over and over
The most expensive pattern we find in LATAM SMBs: they hire a redesign from a designer or agency that doesn't think about SEO, launch the new site with different URLs and not a single 301 redirect, and two months later the owner notices the phone stopped ringing. By then Google has deindexed the old URLs and the new ones still don't rank. Recovering from that takes 3 to 6 months.
The golden rule: the redirect map is built BEFORE you launch, not after you notice the drop.
Conclusion
Migrating without losing rankings is entirely possible and, done right, it's even a chance to improve speed and structure. It comes down to three things: inventory your URLs, redirect each one with a 301 to its equivalent, and monitor indexing through the first month.
At Deepyze we plan the SEO migration from the design phase, not as a rushed final step. We build the redirect map, preserve your content, and watch reindexing until recovery is confirmed. If you're about to redesign or switch platforms and don't want to lose what you worked so hard to rank, start your project with us and we'll plan it together before you touch a single URL.
Frequently asked questions
How much traffic do you lose during a website migration?+
In a well-executed migration, the temporary drop is 5% to 15% over 2 to 4 weeks, then traffic recovers or exceeds the previous level. If you skip 301 redirects or change your URL structure without mapping it, the drop can reach 40-60% and become permanent.
Do 301 redirects pass all the SEO value?+
A 301 redirect passes virtually all of a URL's link equity to the new URL. Google has confirmed there is no longer any PageRank loss from 301 redirects. What you do lose is time: Google takes weeks to recrawl and consolidate the signals.
How long does Google take to reindex after a migration?+
For a small site (under 500 URLs), 1 to 2 weeks. For sites with thousands of URLs, 4 to 8 weeks. You can speed it up by submitting the new sitemap in Search Console and using URL Inspection to request indexing for your most important pages.
Do I have to keep my old URLs when migrating?+
If your current URLs already rank well and are clean, keep the same structure: that is the safest migration. Only change URLs when you have a strong reason (chaotic structure, wrong language, tracking parameters). In that case, every old URL needs a 301 to its most relevant equivalent.
Should I move from HTTP to HTTPS or change domains at the same time as a redesign?+
No. Make one big change at a time. Combining a domain change, a redesign, and an HTTPS migration in a single deploy makes it impossible to diagnose what caused a drop. Separate major changes by at least 2 to 4 weeks.
Do I need professional help to migrate my site without losing SEO?+
For sites under 50 pages keeping the same URL structure, you can do it carefully yourself. For e-commerce, sites with hundreds of URLs, domain changes, or full redesigns, you want a team that builds the redirect map and monitors indexing. A mistake there costs months of traffic.
Want this working in your company?
At Deepyze we turn manual processes into systems that work on their own: AI automation, web and mobile apps, and custom software. Tell us your case and you will have a concrete proposal within 24 hours.
Sin compromiso · Respuesta en 24 hs · Equipo en tu mismo huso horario