SERP Master Agency

Web development · 11 min read · Updated Nov 12, 2026

Website Migration Checklist: Moving Hosts or Domains Safely

A website migration checklist is the ordered list of tasks that moves your site to a new host or domain without losing traffic, rankings or leads. The core steps are a full backup, a crawl of every URL, a 301 redirect map, careful DNS changes, Search Console updates and a week of post-launch checks.

This guide covers both common moves for business owners: changing hosts with the same URLs, and changing domain names. You get the checklist in the order we work through it, the official Google guidance behind each step and a simple rule for keeping risk low.

Key takeaways

  • A safe website migration starts with a full backup, a crawl of every current URL and a benchmark of traffic and leads before anything moves.
  • Moving hosts without changing URLs is the lowest-risk migration because Google only has to notice a new server, so the main jobs are DNS, testing and keeping the old host running.
  • A domain change needs a one-to-one 301 redirect map, the Search Console Change of Address tool and redirects kept for at least a year, according to Google.
  • Google says it can take a few weeks or more for a medium-sized site to settle after a move with URL changes, so plan launches away from your busiest season.
  • Change one layer at a time: moving host, domain, design and URLs in one launch makes any traffic drop hard to diagnose and slow to fix.

What counts as a website migration, and which type is yours?

A website migration is any change that alters where your site lives or what its URLs are. The main types are a hosting move, a domain change, an HTTP to HTTPS switch, a platform change and a URL structure change. Each type carries a different level of search risk and needs different steps.

Before you build a plan, name the type of move. Google treats moves with URL changes differently from moves where only the server changes, and the Search Console steps differ too.

Migration typeDo URLs change?Change of Address tool?Relative risk
New host, same domainNoNoLow
HTTP to HTTPSYes (protocol only)NoLow to medium
www to non-www (or reverse)YesNoLow to medium
New domain nameYesYesMedium to high
New platform or CMSOftenOnly if the domain changesHigh
New URL structureYesNoHigh

The risk column is our working view from planning moves, and it rises with the number of URLs that change. Google’s own site move guide lists HTTP to HTTPS as a move with URL changes and says the Change of Address tool is not needed for it. If your move is purely a protocol change, our guide on fixing a website that says Not Secure covers the HTTPS side in detail.

What should you do before you move anything?

Before a website migration, back up all files and the database, crawl every live URL, record current traffic, rankings and lead numbers, and test the new setup on a staging copy. Lower your DNS time to live about a week ahead. These steps give you a safe rollback point and a baseline to compare against.

Most migration problems start before launch day. Work through this pre-move checklist in order:

  1. Take a full backup. Copy all files and export the database, and store the copy somewhere other than the old or new server. Keep it until the move is confirmed.
  2. Crawl and list every URL. Include pages, blog posts, images, PDFs and any URLs from your sitemap. Google recommends starting with your most important URLs and including images, video, JavaScript and CSS files.
  3. Record a benchmark. Export the last 3 to 6 months of Search Console clicks by page, GA4 sessions and key events, and a list of the pages that bring most leads.
  4. Build the new site on staging. Test forms, checkout, search, logins and page speed. Block staging from search engines, and write down that you did so.
  5. Lower the DNS TTL. Google suggests lowering the time to live to a conservative value, such as a few hours, at least a week before the move.
  6. Check capacity. Google notes crawling often increases after a move, so make sure the new server has the resources to handle it.
  7. Freeze big content changes. Publishing or deleting pages during the move makes the redirect map go stale.

If you are not sure what the current site has wrong, fix that first. A full site audit before the move stops you carrying old errors, such as redirect chains or broken links, to the new address.

How do you build a 301 redirect map?

A 301 redirect map is a spreadsheet that pairs every old URL with its closest new URL. Each old address should redirect permanently and directly to its final destination, with no chains. Content you are dropping should return a 404 or 410 status, and only pages with a true equivalent should redirect.

The redirect map is the single most important document in a migration with URL changes. Build it in a spreadsheet with three columns: old URL, new URL and status code.

  1. Paste every URL from your crawl and sitemap into the old URL column.
  2. Match each one to the most relevant new page. A service page maps to the same service page, and a blog post maps to the same post.
  3. Use permanent server-side redirects. Google recommends HTTP permanent redirects such as 301 or 308 where possible.
  4. Point every old URL straight to its final address. Google advises redirecting to the final destination directly instead of through a chain.
  5. Mark pages you are retiring with 404 or 410, as Google suggests, instead of sending them all to the homepage.
  6. Test a sample of redirects on staging, then test the full list after launch.

Sending everything to the homepage is the shortcut that costs the most. Visitors who clicked a specific result land on a page that does not answer their question, and search engines lose the signal that the old page had an equal replacement.

Our website migration service includes this redirect map as a sheet you keep, so you can check every rule yourself after launch.

Next step

Want the move done for you?

We back up your site, map every redirect, move it and run the post-launch checks, with a fixed scope and a published price.

Free consultation

Tell us about your business and we’ll recommend a plan or a few fixed-price tasks.

How do you move to a new host without changing URLs?

To move hosts without changing URLs, copy the site to the new server, test it with a temporary address or hosts file, then point DNS to the new server. Keep the old hosting running until its logs show zero visits. Google says a short dip in crawl rate after launch is normal.

A hosting move keeps every URL the same, so search engines only need to notice a new server. That makes it the safest migration type, as long as the switch itself is clean.

  1. Copy files and the database to the new host and confirm the site works there before DNS changes.
  2. Install an SSL certificate on the new server before switching, so visitors never see a security warning.
  3. Recreate email records (MX, SPF, DKIM and DMARC) at the new DNS provider if DNS is moving too. Missed email records are a common cause of lost enquiries after a move.
  4. Update the DNS A record, or nameservers, to the new server.
  5. Watch server logs on both old and new servers, as Google advises, and check DNS propagation with a public lookup tool.
  6. Shut down the old hosting only when its traffic reaches zero.

Google’s guide for moves without URL changes says it is normal to see a temporary drop in Googlebot’s crawl rate right after launch, followed by a recovery over the next days. If you only need the domain registration and hosting moved, the domain and hosting move product covers that scope, including email.

How do you change your domain name without losing SEO?

To change domains safely, redirect every old URL to its match on the new domain, verify both domains in Search Console, then use the Change of Address tool on the old property. Google says to keep redirects for as long as possible, generally at least one year. Update links you control everywhere.

A domain change asks Google to transfer what it knows about your old site to a new one. These are the steps that matter most:

  1. Verify both domains in Search Console. Google requires you to be an owner of both the old and new properties to use the Change of Address tool.
  2. Launch the 301 redirects from your redirect map at the moment the new domain goes live.
  3. Submit the Change of Address request from the old property. The tool works on domain-level properties only and does not move subdomains, including www. Google says to submit it for every variant of the old domain, such as www and non-www.
  4. Submit a sitemap listing the new URLs in the new Search Console property.
  5. Keep redirects live. The Change of Address help page says its effect continues for 180 days, while the site move guide recommends keeping redirects generally at least one year and ideally indefinitely.
  6. Update every link you control: your Google Business Profile website field, social profiles, ad final URLs, email signatures, directory listings and the best backlinks you can reach.

Keep the old domain registered and renewed. If it expires, the redirects stop working and anyone can buy it.

A domain change is the move where a second pair of eyes pays off. Our fixed-scope website migration covers the redirects, Search Console updates and Change of Address request for sites up to the page limit listed on the product page.

What should you check on launch day and in the first week?

On launch day, check that robots.txt and noindex tags no longer block the site, the SSL certificate works, forms send, analytics fires and a sample of redirects return 301 to the right page. Over the first week, monitor Search Console indexing, crawl errors, traffic and leads against your benchmark daily.

Use this post-launch checklist. Tick each item on launch day, then repeat the starred items daily for the first week.

CheckWhat good looks like
robots.txtNo leftover Disallow: / from staging
Noindex tagsLive pages are indexable; the WordPress option that discourages search engines is off
SSL and HTTPSPadlock shows on every page; HTTP redirects to HTTPS
Redirects*Old URLs return one 301 hop to the right page
Forms and calls*Test enquiries arrive in the inbox and CRM
Analytics*GA4 records page views and key events on the new site
SitemapNew sitemap submitted in Search Console, listing only new URLs
Canonical tagsPoint to the new URLs, never the old domain
Internal linksPoint to new URLs directly, not through redirects
Search Console*Pages report and crawl stats show no spike in errors

Broken tracking is easy to miss because the site looks fine. If GA4 or Tag Manager did not survive the move, a GA4 and Tag Manager install restores lead tracking so you can compare against your benchmark. Our technical SEO audit checklist lists the deeper checks to run in week two.

Should you change your host, domain and design at the same time?

Change one layer at a time where you can. A migration that combines a new host, domain, design and URL structure gives you no way to tell which change caused a traffic drop. We call this the one-layer rule: finish and stabilize one move before starting the next one.

Each layer of a website can change independently: the server, the domain, the URLs, the design and content, and the platform. Every layer you change adds new ways for something to break, and every extra layer makes a drop harder to diagnose.

The one-layer rule is a planning habit we use, not a Google requirement. Apply it like this:

  1. List the layers you want to change.
  2. Order them from lowest to highest risk, usually host first, then HTTPS, then design, then domain or URL structure.
  3. Launch the first change, then wait until traffic and leads match your benchmark for two to four weeks.
  4. Start the next change only after that.

Sometimes bundling is unavoidable, for example when a platform change forces new URLs. In that case the redirect map and benchmark carry even more weight. If a redesign is part of the plan, read our guide to a website redesign without losing SEO before you combine it with a move.

How long does a website migration take to settle?

A hosting move with the same URLs usually settles within days once DNS has propagated. Moves with URL changes take longer: Google says a medium-sized site can take a few weeks or more before the new URLs replace the old ones in search, and large sites can take longer still.

Google’s site move guide states that some temporary fluctuation in rankings is expected during a move with URL changes. Its guidance for medium-sized sites is that it can take a few weeks or more for Google to start showing the new URLs instead of the old ones.

During that window, track these signals weekly:

  • Clicks and impressions for the new property in Search Console, rising while the old property falls.
  • Indexed page counts in the Pages report for the new domain.
  • Leads and key events in GA4 compared with the same weeks in your benchmark.
  • 404 errors and redirect errors in server logs.

Treat a drop that keeps growing after a month, or a lead count that falls while traffic holds, as a signal to recheck redirects, canonicals and tracking. If you find issues you cannot fix in-house, a technical fix implementation order covers redirect and indexing repairs, and our web development services handle larger rebuilds.

FAQ

Website Migration Checklist FAQ

Can’t find your answer? Book a free consultation or email contact@serpmasteragency.com.

The hands-on work for a small business site usually takes a few days: backup, move, redirects and testing. DNS changes can take up to the length of the old TTL to reach every visitor. Search settling takes longer for moves with URL changes, and Google says a medium-sized site can take a few weeks or more.

A hosting move with the same URLs rarely causes lasting ranking changes if the site stays fast and online. Moves with URL changes often see temporary fluctuation, which Google describes as expected. Lasting losses usually trace back to missing redirects, redirects to the homepage, blocked crawling or pages removed without replacements.

Google’s site move guide recommends keeping redirects for as long as possible, generally at least one year, and considers keeping them indefinitely. The Change of Address help page asks for at least 180 days, longer if Google Search still sends traffic. Keeping the old domain registered is the simplest way to keep them working.

No. Google says the Change of Address tool is not needed for HTTP to HTTPS moves, www to non-www changes or moves within the same domain. Use it only when moving to a different domain or subdomain. For an HTTPS switch, set up 301 redirects and submit the new sitemap, as covered in our Not Secure fix guide.

A hosting move on a small site with one-click migration tools is a reasonable DIY job if you can test forms and DNS yourself. Domain changes, platform changes and sites that earn most leads from search carry more risk. Our website migration service lists its scope and current price, or book a free consultation for larger sites.

Pick a quiet period in your sales cycle and a weekday with low traffic, so the team can fix issues during working hours. Avoid launches just before peak season, a big campaign or a holiday. Leave at least two to four weeks of normal trading after launch to compare traffic and leads against your benchmark.

The bottom line

Start with the step most owners skip: write down your current traffic, top landing pages and monthly leads, and take a full backup. Then decide which migration type you are doing and follow the matching section of this checklist. If you would like a fixed-scope move with the redirect map, Search Console updates and post-launch checks handled for you, see current prices on the website migration page.

Sources

  1. Site moves with URL changes, Google Search Central, 2026-11
  2. Moving a site without URL changes, Google Search Central, 2026-11
  3. Change of Address tool, Google Search Console Help, 2026-11

Keep reading

Related guides

GA4 Key Events: How to Track Leads From Your Website

GA4 key events show which pages and channels bring you leads. Learn what to track, how to set up form and call tracking, and how to test it properly.

Read the guide →

Web Design vs Web Development: What's the Difference?

Web design vs web development for business owners: who does what, how each affects leads and SEO, and which specialist to hire for the job your site needs.

Read the guide →

Website Maintenance Cost: What to Budget Each Month

Website maintenance cost in 2026: monthly and yearly ranges by site type, what each line item covers, and a simple three-bucket method to set your budget.

Read the guide →

Get started

Move your site without losing your leads

Tell us where your site is going and we will plan the backup, redirects and checks. Talk it through with us first in a free consultation.