Migrate a website without losing rankings

Migrating a website without losing rankings requires method, not just publishing a new version and waiting for Google to understand it. The key is mapping all old URLs to their new equivalents with 301 redirects, keeping a clear correspondence between content, updating sitemap.xml, and reviewing indexing in Search Console for the weeks afterward. If you are changing domain, CMS, architecture, or design, the biggest risk is usually not the visual change, but breaking signals that already worked: internal links, metadata, ranking content, and authoritative paths. A redesign without losing SEO starts before launch, with a full inventory and technical validation. If your site already generates organic traffic or leads, treating the migration as an independent SEO project is the most sensible way to protect what you have built.

Why so many migrations fail (it is not the design)

"301 redirects" in Spain means .htaccess tutorials and WordPress plugins. An SEO migration is not writing one rule. It is deciding, URL by URL, which signal the new page inherits. If the URL that brought bookings or inquiries disappears, returns 404, or lands on the homepage, Google loses equivalence and so does the user.

Domain change, CMS change, folder change, or a full redesign: the risk is the same. First, whether you really need to rebuild: signs you need a redesign. Then this plan. Do not improvise equivalences on go-live day.

Inventory before the new architecture

Cross crawl, sitemap, Search Console impressions, analytics, and backlinks. What is not in the menu may still bring clicks. Each row: URL, status, traffic, links, conversions, title, and planned destination. Classify: keep, redirect 1:1, merge, retire.

Prioritize business and authority, not "all URLs equal." A page with few visits and strong links is more delicate than a dead news post. If you change CMS, compare maintenance and weight: Framer or WordPress.

The 301 map: intent, not slug similarity

Permanent 301, equivalent destination, no chains (old → intermediate → new). Revenue URLs go one by one, reviewed by hand. Pattern rules work on large catalogs; test them with a real sample (accents, parameters, exceptions). Sending the whole archive to the homepage dilutes the signal and frustrates anyone looking for a specific service.

302 or meta refresh do not replace a 301 when the change is final. Search Central treats it as a permanent move. The technical bridge is part of the migration's SEO work, not a designer extra.

Launch day: checklist, not debate

200s on the new URLs, 301s on the old ones, robots and noindex without over-blocking, canonical to the final URL, menu and internal links already in production (not staging). Sitemap only with final crawled URLs. If there is a new domain, the correct Search Console property and the address change when it applies.

Block hours the same day. Google crawls errors if you leave them published. Block the test environment so it does not get indexed.

Afterward: recovery is not "wait two days"

The first weeks: coverage, 404s, queries, and pages that used to convert. A small global drop can hide a service that went to zero. If the old URL does not redirect or the new one does not index: indexing problems.

Isolate technical (301, canonical, noindex) from editorial (the ranking content was cut). One measurable change at a time. Document URL, cause, action, and date. The channel timeline, not this go-live: how long SEO takes.

Technical data and signals that affect crawling and indexing

Google recommends planning site changes, keeping clear redirects, and using Search Console to make tracking easier when there is a domain change. The most important technical signal is that each relevant old URL has a 301 redirect to an equivalent, indexable, accessible new URL. If you migrate a catalog, a blog, or a corporate site, also review sitemap.xml, canonicals, internal links, status codes, and crawl blocks. I would treat this phase as a short technical audit, with tests before and after launch.

Conclusion

Launch-day checklist: confirm 301 redirects, crawl the new site, review sitemap.xml, check Search Console, validate canonicals, and watch the URLs that previously generated traffic or business. Migrating a website without losing rankings is not about avoiding any swing, but about reducing risk and responding quickly when an anomalous signal appears. If your restaurant, ecommerce, or services site depends on organic traffic, the migration must have an owner, a calendar, and a checklist. I would not publish a new site without knowing exactly what happens to every important old URL.

Frequently asked questions about migrating a website without losing rankings

How much traffic is normal to lose when migrating a website?

There is no universal percentage that can be considered normal, because it depends on site size, accumulated authority, mapping quality, and the type of change made. A migration with complete 301 redirects, equivalent content, and an updated sitemap should minimize swings. If the drop concentrates on specific pages, it usually points to redirect, indexing, or content-change problems. Compare priority URLs before and after, not only the global organic traffic chart.

How long does Google take to absorb redirects?

Google can detect redirects quickly, but consolidating signals between old and new URLs can take longer depending on crawl frequency, site size, and each page's importance. URLs with more internal links, traffic, and authority are usually processed before deep or weakly linked pages. In the following weeks, review Search Console, 404 errors, indexed pages, and impressions. If redirects are clear and stable, the process is usually more orderly than when there are chains, loops, or repeated changes.

Should I keep the same URLs when changing CMS?

If you can keep the same URLs and the structure remains logical, that is usually the safest option because it reduces the number of redirects needed. Even so, changing CMS can be an opportunity to clean old paths, remove duplicates, or simplify categories. When you change URLs, each important page must have a 301 redirect to its new equivalent. The decision should be based on SEO value, clarity for the user, and ease of maintenance, not only on the new CMS default settings.

What should I do if I lose rankings after the migration?

Start by identifying which URLs and queries have dropped, instead of applying general changes without diagnosis. Check whether old URLs redirect correctly, whether the new ones are indexable, whether the main content is preserved, and whether internal linking points to the final paths. Also review canonicals, sitemap.xml, robots.txt, and Search Console errors. Then prioritize pages with the highest commercial impact and apply measurable fixes. Avoid changing titles, content, and architecture at once if you still do not know the cause.

Need a marketing team?

Let’s talk and grow your business