Moving a WordPress site to a new host or domain is one of the most stressful jobs in web development — not because the technical process is hard, but because one wrong step can wipe out months of SEO work. I’ve handled hundreds of site migrations over the past five years, and the mistakes I see repeated most often are completely avoidable. This guide walks you through exactly how to do it right.
Why WordPress Migrations Go Wrong
Before we get into the steps, it helps to understand what actually causes ranking drops after a migration. The most common culprits are broken internal links, missing redirects, changed URLs, lost meta data, and slower page speed on the new server. None of these are inevitable — they’re all preventable with a proper process.
Step 1: Run a Full Pre-Migration Audit
Before touching anything, document your current SEO baseline. Use Google Search Console to export your top-ranking pages and their average positions. Screenshot your current Core Web Vitals scores in PageSpeed Insights. Export a list of all your URLs using a tool like Screaming Frog or your sitemap. This data becomes your reference point after the migration — you’ll need it to confirm everything carried over correctly.
Also take note of your current backlink profile. Tools like Ahrefs or Google Search Console’s Links report will show you which pages have external links pointing to them. These are your most valuable pages, and they need extra attention during the move.
Step 2: Back Everything Up
This sounds obvious, but plenty of people skip a proper backup and rely on their host’s automatic snapshots. Don’t. Take a fresh, manual backup of both your database and all files immediately before migration. Plugins like All-in-One WP Migration or UpdraftPlus make this straightforward. Store the backup somewhere off-server — your local machine, Google Drive, or Dropbox.
Step 3: Set Up the New Environment First
Never migrate directly to a live server. Set up the new hosting environment and restore your site there first. Most hosts offer a staging environment or you can use a temporary subdomain. Once the site is running on the new server, test everything thoroughly — forms, checkout flows, internal links, images, speed — before you point your domain anywhere near it.
If you’re moving to a new domain (not just a new host), this stage is especially critical. You’ll need to update all internal links and absolute URLs in the database using a tool like Better Search Replace. Leaving old domain URLs in your content is one of the fastest ways to create broken links that hurt both users and crawlers.
Step 4: Set Up 301 Redirects
If your URL structure is changing at all — even slightly — 301 redirects are non-negotiable. A 301 tells search engines that a page has permanently moved, and it passes the majority of the original page’s ranking signals to the new URL. Without them, Google treats the new URLs as brand new pages with zero authority.
Map every old URL to its new equivalent in a spreadsheet. Then implement the redirects using a plugin like 301 Redirects or directly in your .htaccess file. If you’re staying on the same domain and keeping the same permalink structure, you may not need redirects at all — but verify this before assuming.
Step 5: Migrate and Update DNS
Once everything is verified on the new server, update your DNS records to point to the new hosting. DNS changes can take anywhere from a few minutes to 48 hours to fully propagate worldwide. During this window, some visitors will still see the old server. Don’t make any content changes until propagation is complete.
Keep the old server running until you’re fully confirmed on the new one. Shutting it down too early during propagation means some visitors will hit a dead server.
Step 6: Post-Migration SEO Checks
Once the migration is live, work through this checklist systematically:
- Resubmit your XML sitemap in Google Search Console
- Request re-indexing of your most important pages
- Run a crawl with Screaming Frog to catch any broken links or redirect chains
- Compare your new PageSpeed scores against your pre-migration baseline
- Check that canonical tags are pointing to the correct URLs
- Verify that noindex tags haven’t accidentally been applied site-wide (this happens more often than you’d think)
- Confirm your robots.txt is not blocking Googlebot
Step 7: Monitor for 2-4 Weeks
Ranking fluctuations in the first two weeks after a migration are normal. Google needs time to re-crawl and process the new server. Watch your Search Console data daily for any sudden drops in impressions or crawl errors. If you see specific pages dropping that weren’t expected to, check those redirect chains first — that’s usually where the problem lives.
A well-executed migration can actually improve your rankings if the new server is faster and more stable than the old one. I’ve seen sites pick up 15–20% in organic traffic within a month of moving to a better host, simply because Core Web Vitals scores improved significantly.
Common Mistakes to Avoid
- Migrating without a staging environment — always test before going live
- Forgetting to update the WordPress Address and Site Address URLs in Settings → General
- Skipping the database search-replace when changing domains
- Not testing on mobile — a layout that looks fine on desktop can break on mobile after a theme or host change
- Ignoring SSL — if your new server doesn’t have an SSL certificate installed, all your HTTPS URLs will break
Final Thoughts
A WordPress migration done properly is not something to fear. The process is methodical, and when you follow each step without cutting corners, your rankings should remain stable or even improve. The key is preparation: document your baseline, test thoroughly before going live, and monitor closely in the weeks that follow. If you’d rather have an experienced hand handle the migration for you, feel free to get in touch — it’s one of the services I do regularly for clients.