marumba insightsARTICLES & ANSWERS

Web Development

MIGRATE without losing your rankings

A redirect-first plan that carries your traffic to the new site.

Migrating a Website Without Losing Your Rankings

By Todd Sullivan · November 15, 2026 · 8 min read

The short answer: protect rankings by mapping every old URL to its best new equivalent with a permanent (301) redirect, keeping the content and on-page signals that earn traffic, testing on a staging site that search engines cannot index, and watching Search Console closely for weeks after launch. The single biggest cause of lost traffic in a redesign is missing or wrong redirects.

Why traffic drops after a redesign

  • Broken or missing redirects. Old URLs with links and rankings suddenly return errors or land on irrelevant pages.
  • Changed content and on-page signals. Titles, headings, copy and internal links that matched search intent were rewritten or dropped.
  • Technical mistakes. A staging noindex tag or robots.txt block shipped to production, canonical tags pointing at the wrong host, or a slow new template.
  • Structural changes. Pages merged, removed or buried deeper in navigation.

Some fluctuation is normal while search engines re-crawl and re-evaluate the new site. Practitioners commonly advise expecting a dip and monitoring for several weeks, and Google's John Mueller has been quoted as saying there is no way to guarantee against any loss. A good process keeps the dip small and short.

Step 1: capture a baseline

  • Crawl the existing site and export every URL, status code, title, heading and canonical.
  • Pull the top pages and queries from Search Console, and landing pages with conversions from your analytics.
  • Export your backlink list so you know which pages earn links.
  • Save the old sitemap, robots.txt and a full backup.

Step 1b: triage every URL

Before mapping, give each URL on the old site one of three labels:

  • Keep: the page continues to exist, ideally at the same address. The best redirect is the one you never need, so keep URLs unchanged wherever the new structure allows.
  • Merge: the content is being consolidated. Redirect to the single page that now holds it.
  • Retire: the content is gone with no real replacement. Let it return a proper not-found or gone response rather than redirecting everything to the home page.

This triage is also the moment to decide what you are not migrating. Thin, outdated pages with no traffic or links rarely earn their place in the new site.

Step 2: build the redirect map

Create a spreadsheet with one row per old URL: old URL, new URL, redirect type, and a note. Rules that keep it clean:

  • Redirect each old URL to the closest relevant new page, not to the home page. Blanket redirects to home are treated as soft errors and waste link value.
  • Use 301 (permanent) redirects.
  • Avoid chains: old URL should go directly to the final URL in one hop.
  • Include variations: with and without trailing slash, http and https, www and non-www, uppercase paths, and URLs with common query strings.
  • Redirect images, PDFs and other files that earn traffic or links.
  • Prioritize pages with traffic, links or conversions, but map everything.

A map can start as simple lines like these, which a developer can turn into server rules:

old_url,new_url,type,note
/services.html,/services,301,top landing page
/about-us.html,/about,301,
/blog/2019/seo-tips.html,/insights/seo-basics,301,merged into new article
/old-promo.html,,410,retired, no replacement

For whole sections that follow a pattern, such as every /blog/YYYY/slug.html becoming /insights/slug, a single pattern rule is cleaner than hundreds of lines. Handle the exceptions individually and test the pattern against real URLs from your crawl.

Step 3: keep what ranks

Carry over titles, meta descriptions, headings and the core copy of pages that perform, unless you have a reason to improve them. Preserve internal links to important pages. If you are consolidating several pages, merge the best content rather than discarding it. Redesign the look freely; change the substance deliberately.

Step 4: stage and test

  • Build on a staging address that is blocked from indexing, using password protection if possible.
  • Crawl staging and compare it to the baseline: missing pages, broken links, duplicate titles.
  • Test every redirect in the map against staging or a test server.
  • Verify canonical tags, structured data, sitemap.xml and robots.txt for the production host.
  • Check speed, mobile layout and accessibility.
  • Write down the exact steps to remove staging protections at launch. This is where noindex mistakes happen.

Step 5: implement redirects at the server level

Server-level redirects are faster and more reliable than page-level ones. On nginx, a map file keeps hundreds of redirects manageable:

map $request_uri $redirect_target {
    default "";
    /old-services.html   /services;
    /about-us.html       /about;
}

server {
if ($redirect_target) {
return 301 $redirect_target;
}
}

Whatever your server, keep the map in version control so changes are reviewed and reversible.

Step 5b: test the redirects in bulk

Do not spot-check a few pages and hope. Export the old URLs from the redirect map and test every one. A simple loop with curl reports the status code and the final destination for each:

while read url; do
curl -s -o /dev/null -L -w "%{http_code} %{num_redirects} %{url_effective} <- $url\n" "$url"
done < old-urls.txt

You are looking for a final status of 200, one redirect at most, and a destination that matches the map. Anything that ends in a 404, loops, passes through more than one hop or lands on the home page is a defect to fix before launch. Many crawling tools can run the same check in list mode.

Step 6: launch-day checklist

  • Remove staging noindex and password protection.
  • Confirm robots.txt allows crawling and points to the sitemap.
  • Switch DNS or server configuration, and confirm the HTTPS certificate.
  • Test a sample of old URLs, including top landing pages, and confirm each returns 301 then 200.
  • Check the canonical host: pick one version (for example, no-www over https) and redirect the others.
  • Verify analytics and conversion tracking fire on the new pages.
  • Test forms and email delivery end to end.
  • Submit the new sitemap in Search Console and Bing Webmaster Tools.

Step 7: monitor for four to eight weeks

  • Check Search Console daily for the first week: indexing, crawl errors and any spike in not found pages.
  • Compare organic traffic, impressions and conversions to the baseline by page group, not just in total.
  • Fix unexpected 404s by adding redirects.
  • Do not make large unrelated changes during this window; you will not know what caused what.
  • Keep redirects in place for at least a year, ideally indefinitely, as long as the old URLs still have links.

What to expect afterward

Even a flawless migration is processed gradually. Google says most moves involving URL changes take a few months for its systems to fully process, and recommends keeping redirects in place for at least a year (Search Engine Journal). Expect some movement in the first weeks while old URLs are swapped for new ones. The reason for the one-year guidance is that systems need to see the redirect repeatedly before treating the change as permanent. If you also use Search Console's Change of Address tool for a domain move, note that its help page cites a shorter minimum of 180 days. The longer figure is the safer one, and keeping redirects indefinitely is harmless for visitors who still have old links.

Your comparison should look at page groups: money pages, top informational pages, location pages. A small dip across the board is normal. A steep drop on one group usually points to a specific cause, such as a missed redirect pattern or a changed template.

Mistakes that cause most of the damage

  • Noindex or a blocking robots.txt left on from staging. Check this first on launch day.
  • Canonical tags pointing to the staging or old host.
  • Redirecting everything to the home page. It discards the relevance that old pages had earned.
  • Redirect chains and loops created when new rules stack on top of old ones.
  • Temporary (302) redirects used where permanent ones were intended.
  • An outdated sitemap that still lists old URLs.
  • Forgetting non-page files such as PDFs, images and downloadable price lists that other sites link to.
  • Broken tracking. If analytics stops recording after launch, you lose your ability to diagnose everything else.

Step 8: tidy the edges

Update your Google Business Profile, directory listings and social profiles to point to the new URLs, ask partners with important links to update them and refresh any printed or email materials. Request recrawls for key pages if needed.

When migration is part of a bigger move

If you are also changing domains, platforms or languages, split the work into stages where possible. Changing everything at once makes problems harder to diagnose. And if you run legacy sub-applications under the same domain, list them in the map and decide explicitly whether they stay at their existing paths.

Protecting AI visibility too

The same discipline protects how assistants see you. Keep every URL you reasonably can, make sure new templates serve real content in the page HTML, confirm your new host and firewall do not block the crawlers you want, and carry over the pages that answer customer questions. A migration that quietly removes your best explanatory content or blocks crawlers can cost you citations as well as rankings.

Quick answers

Should I change my domain and design at the same time?

Where you can, no. Google's own site-move guidance advises making changes one after another rather than all at once, so that if something goes wrong you can tell which change caused it.

Do I need the Change of Address tool?

Only for a move from one domain to another. It does not apply to moves between http and https, www and non-www on the same domain, or to a change of host with the same URLs.

Will I lose rankings no matter what?

No guarantee exists, and a short fluctuation is common. A complete redirect map, preserved content and careful monitoring keep losses small and usually temporary.

How long should I keep the old redirects?

At least a year, and longer if the old URLs still receive links or visits.

Sources

Want help with this?

Tell us what you are working on and we will point you in the right direction.

Call Get a quote