A USB drive plugged into the side of a laptop, representing moving website files

Website Migration Checklist to Protect Your SEO

Teckohost earns a commission when you buy through some links on this page, at no extra cost to you. Prices were checked on November 6, 2026.

A website migration checklist has five phases: audit the old site, build and test the new site on a staging environment, map every old URL to a new one, launch, then watch search results for weeks. Skip the redirect mapping and you can lose the organic traffic you spent years earning.

This checklist works for a move to a new host, a new domain, a new content management system or a redesign. Where a step is specific to WordPress, it says so.

A successful site migration starts with a plan, not a file transfer

Website migration means changing something that search engines and visitors rely on: the host, the domain, the URL structure, the design or the platform. Copying files is the smallest part. The risk sits in what changes around the files, such as URLs, redirects and tracking.

Write a short migration plan before you touch anything. It should name what is changing, who owns each task, the launch date and a rollback plan. Pick a quiet week, not a sale or a launch.

Type of move What changes SEO risk
New host only Server and IP address Low, if URLs stay the same
New domain Every URL High, needs full redirects
New platform or CMS Templates, often URLs High
Redesign or new site structure Layout, navigation, internal links Medium to high
HTTP to HTTPS Protocol of every URL Medium

A move to a new host with the same URLs is the simplest kind. Our guide on how to transfer a website to a new host covers it step by step, and how to migrate a WordPress site covers the WordPress case.

Back up the entire site before you change anything

A full backup is your safety net. Take one of the files and one of the database, and store both away from the old host. Then test that you can restore it. A backup you have never restored is a guess.

  • Download all site files by SFTP or from your control panel.
  • Export the database.
  • Save a copy of your configuration files, such as the wp-config.php file on WordPress.
  • Note your current plugin and theme versions.
  • Keep the old site running until the new one is verified.

Our guide to backing up WordPress shows the options. Many hosts also keep their own copies, but do not rely on them alone.

Run a site crawl and record your current site baseline

You cannot prove a migration worked without a before picture. Run a full site crawl of the current site with a crawler such as Screaming Frog or a similar tool, and export the list of URLs, titles, meta descriptions, headings, status codes and canonical tags.

Also save these numbers from your analytics and search tools:

  • Organic traffic by page and by month, from Google Analytics.
  • Impressions, clicks and keyword rankings, from Google Search Console.
  • Your top performing pages and the pages that earn external links.
  • Core Web Vitals scores and load times for key pages.
  • Your current XML sitemap and robots.txt file.

This baseline is what you compare against after launch. A short SEO audit now saves guessing later.

Decide what changes in your site structure and URL structure

Every URL that changes needs a plan. Keep the same URL structure wherever you can, because the safest URL is one that does not move. Change URLs only when there is a clear reason, such as a new domain or a cleaner site architecture.

If the new site structure drops pages, decide for each one: keep it, merge it into a stronger page, or retire it. Do not delete pages that earn traffic or links. Internal links, navigation and breadcrumbs should follow the new site structure, so plan them now rather than after launch.

Keep titles, headings and body copy the same on pages that rank well, at least at first. Changing the move and the content at once makes it hard to tell what caused a drop.

Build the new site on a staging environment and keep it out of search

A staging site is a private copy of your site where you build and test. Build the new site there, not on the live domain. Many hosts offer one-click staging. Our guide to a WordPress staging site explains how it works.

Prevent search engines from indexing the test site. Use password protection, or a noindex tag, so Google does not find duplicate content. Block search engines on the staging environment only. A common launch mistake is leaving that block on after going live.

  • Check that every page, image and form works on the new site.
  • Test checkout, contact forms and logins if you have them.
  • Check the site on a phone as well as a desktop.
  • Review new pages for titles, meta descriptions and headings.
  • Confirm canonical tags point to the new URLs, not the old ones.

Redirect mapping: send every old URL to its closest new URL

Redirect mapping is the step that protects your rankings. Make a spreadsheet with two columns: old URLs and new URLs. Use your crawl, your sitemap and Google Search Console to find all the URLs, including old blog posts, images and PDF files.

Use 301 redirects, which tell search engines a page has moved permanently. Send each old URL to the most relevant new page, not to the homepage. Redirecting everything to the homepage looks like a soft 404 to search engines.

Redirect rule Why it matters
One hop only Redirect chains slow crawling and can dilute link signals
Match content, not just topic Keeps relevance and preserves link equity
Cover www and non-www, and HTTP and HTTPS Each version of a URL needs a path to the new one
Keep redirects for at least a year Old links and bookmarks keep arriving

Google’s own guidance on site moves recommends keeping redirects in place for as long as you can. Do not remove them after a few weeks.

Check DNS settings and lower the TTL before the move

When you change hosts, you also change where your domain points. That is a DNS change. DNS records tell browsers which server holds your site. Read what DNS is and what a nameserver is if the terms are new.

A day or two before launch, lower the TTL on your DNS records to a few minutes. TTL is how long servers cache the old answer. A low TTL means visitors reach the new server sooner after the switch. Raise it again once the move is stable.

Keep the old hosting account active during the switch. DNS changes spread over hours, so some visitors will still see the old site for a while. Also check your email records, such as MX records, so email keeps working.

Free migration help: what three hosts list on their own sites

Many hosting providers offer to move your site for you. These are the hosts’ own descriptions, checked on November 6, 2026, and we have not tested the quality of any of them.

  • Hostinger lists free automatic website migration and unlimited free migrations, started from a Migrate Website menu in its control panel.
  • SiteGround says its experts move a WordPress site for you, the first migration is free and the site stays live throughout. We earn nothing if you buy SiteGround.
  • Bluehost lists a free site migration tool on its plans.

A host’s migration service moves the files and database. It does not write your redirect map, update your tracking or check your SEO. Those steps are still yours. Read best WordPress hosting if you are still choosing where to move.

Pre launch checks: run one last test before you go live

On launch day, work through a short list before you flip the switch. Most migration mistakes happen in this hour.

  1. Confirm the latest backup of the old site exists and restores.
  2. Compare the new site’s page count with the crawl of the old site.
  3. Test the redirect map on a sample of old URLs.
  4. Check that internal links point to new URLs and not to the old domain.
  5. Confirm the SSL certificate is installed on the new site. See what an SSL certificate is.
  6. Remove the staging noindex block and any password protection.
  7. Check robots.txt does not block search engines.
  8. Confirm Google Analytics and any other tracking code is on the new pages.

Post launch monitoring: what to check in the first hour, week and month

After you launch, test the live site right away. Click through key pages, test forms and checkout, and visit old URLs to confirm each one redirects. Then keep checking. Post migration monitoring is where most problems get caught.

  • First hour: test pages, forms, redirects and SSL.
  • First day: crawl the new site and look for broken links, 404 errors and redirect chains.
  • First week: check Google Search Console for crawl errors and coverage problems.
  • First month: compare organic traffic, impressions and keyword rankings with your baseline.

Rankings often move around for a few weeks after a migration. Search engines need time to recrawl and process the changes. A temporary dip is normal. A drop that lasts is a sign something is wrong, and your baseline will help you find it.

Submit your sitemap and tell Google about a new domain

Submit your new XML sitemap in Google Search Console, and in Bing Webmaster Tools for other search engines. A sitemap helps search engine crawlers find all the new URLs faster. Keep the old sitemap available briefly so crawlers can see the old URLs redirect.

If you changed domains, Google Search Console has a Change of Address tool for moving a site to a new domain. Add the new domain as a property first, and keep the old property so you can watch it. This tool is only for a domain change, not a host change.

Update the links you control: your social profiles, email signatures, Google Business Profile and any directory listings. Also contact the sites that link to you most and ask them to update their links. That helps preserve link equity.

The SEO migration checklist in one view: a website migration guide by phase

This website migration guide boils the website migration process down to one table. Use it as an SEO migration checklist on launch week. A smooth migration is mostly about doing each phase in order and not skipping the dull ones.

Phase What to do Why it helps
Before Back up, crawl the current site, record traffic and rankings Gives you a baseline to judge the new site’s performance
Build Work on a staging site, block it from search Protects your organic visibility from duplicate content
Map Finish the redirect mapping process for every old URL Helps search engines find the new pages and keeps link equity
Launch Lower TTL, switch DNS, remove the noindex block Ensures search engines can crawl the live site
After Submit the sitemap, crawl, monitor Search Console Catches issues before they hurt search engine rankings

A successful website migration is one where visitors never notice the move and your site’s traffic holds steady. A successful migration does not guarantee the same search engine rankings, because algorithms and competitors move too. It does give you the best chance to keep them.

Your SEO strategy should stay stable through the move. Do not rewrite content, change keywords or rebuild navigation at the same time unless you must. If you do, expect your SEO performance to take longer to settle, and record each change so you can trace any drop.

Domain migration needs extra care because every URL changes

A domain migration is the highest-risk kind of site move. Every address on the old site changes, so redirect mapping, internal links and canonical tags all matter more. Tell Google through the Change of Address tool, and keep the old domain registered for years so the redirects keep working.

After the move, check Google search results for your brand and top pages. Searching your key terms shows whether the new URLs have replaced the old ones on the search engine results page. This can take weeks, and it is normal to see both for a while.

Also check how the new website performs. Compare load times and Core Web Vitals to your baseline, because a slower host or a heavier theme can hurt the new site’s performance and your rankings.

Common migration mistakes that cost search visibility

Most migration problems come from the same handful of mistakes. Knowing them is half the defense.

  • No redirect map, or redirects that all point to the homepage.
  • Leaving the noindex block from the staging site on the live site.
  • Changing URLs, content and design in one go.
  • Forgetting to move tracking codes and to keep Google Analytics running.
  • Shutting down the old host too soon.
  • Broken internal links that still point to the old domain.
  • Removing pages that had traffic or backlinks.

A slow new host can also hurt. See how to speed up WordPress and best CDN for WordPress if load time drops after the move.

Website migration checklist questions

How long does a website migration take?

A small site on a new host can move in a day. A new domain or platform with hundreds of pages can take weeks of planning. Allow time for testing and post-launch checks.

Will a website migration affect SEO?

It can. A move that keeps the same URLs carries less risk. Changes to URLs, content or structure carry more. Redirect mapping and monitoring reduce the risk, but no one can promise your rankings will stay the same.

Should I keep the old site online after the move?

Yes, for a short time. Keep the old hosting account active until DNS has fully switched and you have confirmed the new site works. Then keep redirects in place long after.

What is the safest day to migrate?

A quiet day for your traffic, with time to fix issues. Avoid sale periods, product launches and holidays. If you are moving to get a better price, see our Black Friday hosting deals first.

Can I migrate a site myself?

Yes, for a small site. Follow this checklist, use a staging site and keep a backup. For a large site, store or new domain, consider hiring help or asking your new host about its migration service. See our guide to web hosting for the basics.

Share your love
Tumisang Bogwasi
Tumisang Bogwasi