WordPress Migration Checklist: Move Your Site Without Losing SEO
Migrating a WordPress website is akin to performing open-heart surgery on your digital business. Whether you are moving to a new hosting provider, changing your domain name, or switching from HTTP to HTTPS, the stakes are incredibly high. A poorly executed migration doesn't just result in broken images or downtime; it can catastrophic SEO collapse. Years of hard-earned rankings, traffic, and domain authority can vanish overnight if Google’s crawlers encounter broken links or confused signals.
In my career, which I detail on my About Us page, I have rescued dozens of clients who attempted to migrate their sites using "one-click" plugins, only to find their traffic flatlining weeks later. The reality is that preserving SEO during a move requires a meticulous, manual strategy. It requires understanding how Google indexes content and how it reacts to changes in URL structure. This comprehensive WordPress migration checklist is designed to guide you through the process, ensuring that your site not only survives the move but thrives in its new home.
Article Navigation
1. Pre-Migration: The SEO Audit and Benchmark
Before you move a single file, you must understand exactly what you are moving. A common mistake is migrating "blind," assuming that if the files transfer, the SEO transfers. This is false. You need a baseline of your current performance to compare against after the move.
Crawl Your Current Site
Use a tool like Screaming Frog to crawl your existing website. You need a complete list of every URL, meta title, and H1 tag currently live. This list will be your "master map." If you lose a page during migration, this list is the only way you will know it is missing. In my services, I emphasize this audit phase because it often reveals pre-existing issues (like broken links) that should be fixed before migration, not after.
Backup Everything
While this seems obvious, standard host backups are often insufficient. You need a manual export of your MySQL database and your `/wp-content/` folder. Google explicitly warns that server errors (5xx) caused by failed migrations can lead to de-indexing. Having a local backup ensures you can restore the site to its original state within minutes if the migration fails.
2. The Staging Environment and Duplicate Content
Never migrate directly to a live server without testing. You should set up a "Staging Site"—a clone of your website on a temporary URL (e.g., `staging.yoursite.com`). This allows you to test functionality without risking your live traffic.
Blocking Search Engines
A critical SEO step during staging is ensuring Google does not index your testing site. If Google crawls your staging site and sees the same content as your live site, it may flag it as "Duplicate Content." To prevent this, you must use the `robots.txt` file to block crawlers or password-protect the directory. Google's documentation on duplicate content explains that they try to choose one "canonical" version, and you do not want them choosing your temporary staging site by mistake.
Official Source: Google Search Central - Duplicate Content3. URL Structure and Permalinks
The single most dangerous aspect of migration is changing your URL structure. If your current blog posts look like `site.com/2023/post-name`, and your new site changes them to `site.com/post-name`, every single link in Google's index will break (404 Error).
Maintain Consistency
Unless you are specifically doing a rebranding project that requires a structure change, keep your Permalinks exactly the same. Go to WordPress Settings > Permalinks and ensure the structure matches the old site perfectly. If you must change URLs, you are entering advanced migration territory, which requires complex mapping that I discuss in my portfolio of complex site moves.
4. The 301 Redirect Strategy (Crucial)
If you are changing your domain name (e.g., from `.net` to `.com`) or changing any URL structures, you must use 301 Redirects. A 301 status code tells Google: "This page has moved permanently to this new location. Please transfer all ranking power (PageRank) to the new URL."
One-to-One Mapping
Do not be lazy and redirect all old pages to the homepage. This is known as a "Soft 404" and Google treats it as an error. If a user clicks on a link about "Red Shoes," they expect to land on a page about "Red Shoes," not your homepage. You must create a map where `Old Page A` redirects to `New Page A`. This granular attention to detail is something I highlight in my experience handling enterprise migrations.
Avoiding Redirect Chains
Ensure that Page A redirects directly to Page B. Avoid chains where A redirects to B, and then B redirects to C. Chains slow down the crawler and dilute the PageRank passed to the final destination. Google's guides on redirection emphasize that 301s are the strongest signal for site moves.
Official Source: Google Search Central - Redirections and Search5. Post-Migration Technical Verification
Once the files are moved and the DNS is pointed to the new server, the site is live. Now, the real work begins. You must verify that the technical SEO elements are functioning correctly in the new environment.
Robots.txt and Noindex
The most common post-migration disaster I see is developers forgetting to remove the "Discourage search engines from indexing this site" setting in WordPress. Check your `robots.txt` file immediately. Ensure it allows Googlebot to crawl your site. If this file blocks the crawler, your site will disappear from search results within days. Google's robots.txt specifications are very strict; a single misplaced character can block the entire site.
Official Source: Google Search Central - Robots.txt IntroductionSSL (HTTPS) Verification
Ensure your SSL certificate is active on the new server. Use a tool to check for "Mixed Content" errors. This happens when the site is HTTPS, but some images or scripts are still loading over HTTP. This triggers security warnings in browsers and can hurt rankings.
6. Google Search Console: The Change of Address Tool
You need to tell Google explicitly that you have moved. Google Search Console (GSC) is the control center for this communication.
Change of Address Tool
If you have changed your domain name, use the "Change of Address" tool inside GSC. This alerts Google to prioritize crawling your 301 redirects and updates their index more quickly. Note that you must have ownership verified for both the old and new domains to use this tool.
Sitemap Submission
Generate a new XML Sitemap for the new site and submit it to GSC. This gives Google a roadmap of your new structure. Watch the "Coverage" report in GSC closely for the first few weeks. If you see a spike in 404 errors, check your redirect map immediately. Managing these technical nuances is a core skill listed in my resume.
Official Source: Google Search Console - Change of Address Tool7. Monitoring Traffic and Recovery
Even with a perfect migration, you may see a temporary fluctuation in rankings. This is normal as Google re-crawls and re-processes your pages. However, a permanent drop indicates a problem.
The 404 Monitor
Install a 404 monitor plugin or check your server logs daily. If real users are hitting "Page Not Found" errors, it means you missed a redirect. Fix these immediately. Recovering lost traffic is much harder than maintaining it.
Speed Performance
Often, a new server might have different configurations that affect speed. Run your new site through Google PageSpeed Insights. If your Core Web Vitals have dropped, you need to optimize your caching and server settings on the new host.
Conclusion: Diligence Pays Off
The WordPress migration checklist is your safety net. Moving a site without losing SEO requires a blend of technical precision and strategic planning. It is not something to be rushed. By following these steps—auditing content, mapping redirects, verifying technical signals, and communicating with Google—you ensure your digital business continues to grow in its new location.
If the prospect of handling database tables, 301 maps, and DNS propagation feels overwhelming, do not risk your search rankings. Professional assistance can ensure a seamless transition.
Did You Migrate and Crash?
A botched migration can be reversed, but time is critical. If your traffic dropped after moving hosts or domains, you likely have broken redirects or blocked crawlers. I offer an emergency "Migration Recovery Audit" where I identify the broken links, fix the redirect chains, and restore your site's visibility.
Don't let a technical error destroy years of work. Let's fix your migration today.
Recover My Traffic