A WordPress migration checklist keeps a site move from turning into a rankings drop. Moving to a new host, a new server or a new domain touches files, the database, URLs and search engines. Miss one step and pages go missing or visitors see errors.
This guide gives a step-by-step checklist, from the backup to the checks after launch. It uses advice from the WordPress documentation and from Google’s guidance on site moves.
Back up first and keep a copy off-site. Build and test the new site, map every old URL to a new one, then redirect permanently. After launch, submit a new sitemap, watch Search Console, and keep the redirects for at least a year. A change of address in Search Console is only for domain or subdomain moves.
⚡ Key Takeaways
- Back up the files and the database before you touch anything, and store the copy off-site.
- Prepare a URL mapping from every old URL to its new URL before the move.
- Google says 301 and other permanent redirects do not cause a loss in PageRank.
- Keep redirects for as long as possible, generally at least one year, according to Google.
- Use the Change of Address tool only when you move from one domain or subdomain to another.
Know What Type of WordPress Migration You Are Making
First, note that the checklist changes a little with the type of move. Google separates site moves into two groups: moves that change URLs, and moves that keep them the same. Moving to a new host with the same domain and the same URLs is the simplest case.
However, changing the domain name, switching from HTTP to HTTPS, or changing your URL structure all change URLs. Those moves need redirects and more monitoring. Decide which one you are doing before you start, because it sets how much work lies ahead.
Step 1: Back Up Before Any WordPress Migration
Take a full backup first. The WordPress documentation tells you to back up your database and save the copy off-site. Also copy your wp-content folder, your wp-config.php file and your .htaccess file.
Then, check that the backup works. A backup you cannot restore is not a backup. If you can, restore it on a test server before the real move.
Step 2: Record Your Current Site
Before you change anything, collect what you have. For example, export your list of URLs from your sitemap or a crawl. Note your page titles, your top landing pages and your current rankings.
Also, record plugins, theme settings, redirects and any custom code. This record lets you compare the old and new site later, and it saves time if something breaks.
Step 3: Build and Test the New WordPress Site
Set up the new hosting or server, then copy the site there. Google advises preparing the new site and testing it thoroughly before the move. Use a temporary address or a staging copy, and keep it out of search results while you test.
Check forms, checkout, search, menus and images. Test on a phone as well. So, fix problems now, because they are much harder to fix after launch.
Step 4: Map Old URLs to New URLs
If any URL will change, prepare a mapping from each current URL to its new format. Google lists this as a core step. For this, a simple spreadsheet with two columns, old URL and new URL, is enough.
Map each page to its closest match, not to the home page. In fact, sending everything to the home page confuses visitors and search engines. The WordPress permalinks guide explains how URL structure affects this step.
Step 5: Switch the Site and Set Up Redirects
When the new site passes your tests, switch the domain or DNS records to it. If you change the site address, the WordPress documentation says to update the WordPress and Site Address in Settings, General, and then update your permalinks and .htaccess file. Make a backup copy of .htaccess first.
Next, configure the server to redirect from old URLs to new ones. Google states that 301 and other permanent redirects do not cause a loss in PageRank. This matches the advice in this guide to 301 redirects for SEO.
Step 6: Use Change of Address Only When It Applies
Google says the Change of Address tool is for moves from one domain or subdomain to another, such as example.com to example.net. You do not need it for HTTP to HTTPS moves, for switching between www and non-www on the same domain, or for moving paths within the same domain.
If it applies, verify both the old and new sites in Search Console. Then, submit the request for the old site. Google also says to make sure you submit requests for all verified variants.
Step 7: Submit a New Sitemap and Check the Basics
Submit the new sitemap in Search Console. Google says this helps it learn about the new URLs. Then, crawl the new site yourself to find broken links, redirect chains and missing pages.
Also, check robots rules, canonical tags and page titles. For instance, a leftover noindex setting from the test site is a common and costly mistake.
Step 8: Monitor Your WordPress Migration and Be Patient
Watch both the old and new URLs. Google suggests verifying each property separately in Search Console and using the Index status and Sitemaps reports for a broad look. So, check errors, traffic and rankings every few days at first.
Google notes that a site move is complete only when Googlebot has visited every URL on the old and new sites, which takes time. Keep the redirects for as long as possible, generally at least one year. Google adds that you should consider keeping them indefinitely for users.
After the Move: Keep the Site Healthy
Once the move settles, return to normal upkeep. For example, update plugins, check backups and watch speed. This list of safe WordPress update steps helps.
If you would rather not handle moves and updates yourself, WordPress support and maintenance covers both.
Worked Example of a WordPress Migration (Made-Up)
Imagine a small law firm that moves its WordPress site to a faster host. The domain and URLs stay the same. The owner takes a backup, copies the site to the new host, and tests it on a temporary address. After the DNS change, the team crawls the live site and finds that the contact form fails.
Because the old host is still running for a few days, they can fix the form before the old account closes. This firm is made up. It shows why you keep the old site until the new one passes every check.
WordPress Migration Checklist
- Back up files and database, and store a copy off-site.
- Export your current URLs, titles and key pages.
- Build and test the new site on a staging address.
- Map each old URL to its closest new URL.
- Switch the site, then set up permanent redirects.
- Use Change of Address only for domain or subdomain moves.
- Submit the new sitemap and crawl for errors.
- Monitor Search Console and keep redirects for at least a year.
Conclusion
In short, a good migration is mostly preparation. Back up, test, map your URLs and redirect them permanently. Then watch the numbers for a few weeks and be patient while search engines catch up.
For a move between platforms, this walkthrough on moving from Webflow to WordPress covers the extra steps.
Frequently Asked Questions About WordPress Migration
How do I do a WordPress migration without losing SEO?
Keep your URLs the same if you can. If they must change, map every old URL to a new one and use permanent redirects. Then submit a new sitemap and monitor Search Console.
Do 301 redirects lose link value?
Google says 301 and other permanent redirects do not cause a loss in PageRank.
How long should I keep redirects after a site move?
Google says to keep redirects for as long as possible, generally at least one year, and to consider keeping them indefinitely for users.
When do I need the Change of Address tool?
Only when you move from one domain or subdomain to another. You do not need it for HTTP to HTTPS, for www and non-www changes, or for moving paths on the same domain.
What should I back up before a migration?
Back up your database and your files, including the wp-content folder, wp-config.php and .htaccess. Save a copy off-site and test that it can be restored.
