How to Move Your Website Without Losing Traffic

Switching hosts, rebuilding on a new platform or moving to a new domain can give your business a faster, better website. Done carelessly, it can also wipe out the search traffic you spent years building. This guide walks you through a website migration step by step, so customers and search engines follow you to the new site.

A "website migration" covers several different projects. Each carries a different level of risk for your search traffic:

• Host move: same domain, same URLs, new server. Lowest risk if done carefully.
• Platform move: for example from a hosted builder to WordPress, or the other way around. URLs often change, so redirects become essential.
• Domain move: for example from an old brand name to a new one, or from a country domain to a .com. Highest risk, because search engines must transfer signals from one domain to another.
• Redesign with restructuring: new navigation, merged pages and new URL patterns. Often underestimated, because it feels like "just a redesign".

Some temporary fluctuation in rankings after a big move is common, even when everything is done right. The goal of this guide is to keep that dip small and short. Tools and settings change often, so check the current documentation from your host, platform and Google before you begin.

Step 1: Take stock of the old site

You cannot protect what you have not listed. Before touching anything, build a complete picture of your current website.

1. Crawl the site. Use a website crawler, a tool that follows every link on your site like a search engine does, and export the list of URLs. Many crawlers have free versions that are fine for small sites.
2. Add URLs the crawler might miss. Export your XML sitemap, the top pages from Search Console's Performance report and the most visited pages in your analytics. Old landing pages and PDFs linked from ads or emails often do not appear in a crawl.
3. Note your best performers. Mark the pages that bring the most search clicks, leads or sales. These deserve extra care.
4. Record page details. For important pages, save the title, meta description, main headings and any structured data, so you can check they survive the move.
5. Benchmark performance. Save screenshots or exports of Search Console clicks and impressions, plus analytics traffic, for the past few months. You will compare against these after launch.
6. Take a full backup. Back up files, database and email settings of the old site, and keep the old hosting active until the migration is confirmed stable.

Step 2: Map every old URL to a new one

The single most important rule: if you can keep your URLs exactly the same, do it. A host move with unchanged URLs avoids most risk. When URLs must change, create a redirect map, a simple spreadsheet with two columns: old URL and new URL.

• Map each old page to the most relevant new page, not to the home page. Sending everything to the home page confuses visitors and search engines alike.
• If you merge several old pages into one, redirect all of them to the merged page.
• If a page truly has no equivalent, it is acceptable to let it return a "not found" error, but think twice for pages that have links or traffic.
• Avoid redirect chains, where URL A redirects to B, which redirects to C. Point A straight to C.

What a 301 redirect is

A 301 redirect is a permanent redirect. It tells browsers and search engines that a page has moved for good, and search engines generally pass the old page's signals to the new address. Most platforms let you add redirects in the settings or with a redirect plugin. On Apache servers, which many shared hosts use, redirects can also go in a file called .htaccess. Here is a generic example using placeholder addresses:

# Single page moved to a new address
Redirect 301 /old-services.html https://www.example.com/services/

# Whole old domain to the new domain, keeping paths
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?old-example\.com$ [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

Server setups differ, so ask your host or developer which method fits yours, and test every redirect rather than assuming it works.

Step 3: Build and test the new site privately

Build the new site on a staging address or a temporary URL that search engines cannot index. Most hosts and builders offer password protection or a "coming soon" mode for this. Then check:

• Every important page from your inventory exists, with its content, title and meta description.
• Internal links point to the new URLs directly, not to old URLs that rely on redirects.
• Images, PDFs and downloads have moved and load correctly.
• Forms, checkout, booking tools and analytics tracking all work.
• The site loads fast and works well on phones. A slower new site can cancel out the benefits of the move.
• HTTPS is ready, with a valid SSL certificate for the domain you will use.

Step 4: Switch DNS and go live

DNS, the Domain Name System, is the internet's address book. It tells browsers which server your domain points to. When you move hosts, you change DNS records so your domain points to the new server.

Lower the TTL in advance

Each DNS record has a TTL, or "time to live", which tells other systems how long to remember the answer before checking again. A day or two before the move, lower the TTL on the records you will change, for example from several hours to a few minutes. When you switch, the change then spreads much faster. After the move settles, you can raise it again.

Launch day sequence

1. Pick a quiet time. Choose a low-traffic day and time, and avoid your busiest season.
2. Freeze changes on the old site. Stop publishing new content or taking changes that would need copying across.
3. Update the DNS records. Point your domain to the new host. Be careful not to delete email records, such as MX records, unless your email is moving too.
4. Remove any "noindex" setting. Staging sites often block search engines. Make sure the live site is indexable and that robots.txt does not block it.
5. Turn on redirects. Activate the redirect map, including HTTP to HTTPS and non-www to www, or the other way around, consistently.
6. Test a sample of old URLs. Paste old addresses into a browser or a redirect checker and confirm each one lands on the right new page in a single hop.

Step 5: Monitor and fix after launch

The work is not finished on launch day. The first few weeks matter most.

• Submit the new sitemap in Google Search Console and Bing Webmaster Tools.
• Use URL Inspection in Search Console on your most important pages to confirm Google can fetch and index them.
• Watch the Page indexing report for spikes in "Not found (404)" errors, then add missing redirects.
• Compare traffic in Search Console and analytics against your benchmark, page by page for your top performers.
• Re-crawl the new site to find broken internal links, missing titles or redirect chains.
• Update external profiles such as your Google Business Profile, social media bios and directory listings with the new URLs.

Extra steps for a domain change

If you moved to a new domain, verify both the old and new domains in Search Console, then use the Change of Address tool, which tells Google about the move. Keep the old domain registered and its redirects active for the long term. Letting the old domain expire breaks every old link and could let someone else buy it.

Frequently asked questions

The bottom line

Moving a website without losing traffic comes down to three habits: know exactly what you have before you start, give every old URL a clear new home with a 301 redirect, and watch Search Console closely after launch. Take your time on the inventory and the redirect map. They are the boring parts, and they are the parts that protect your traffic.