Migrating a WordPress website can be straightforward technically, but it becomes much more complicated when SEO, rankings, traffic, backlinks, and indexed URLs are involved.
A website migration can mean moving your site to a new hosting provider, changing your domain name, switching from HTTP to HTTPS, restructuring URLs, moving from another platform to WordPress, or rebuilding your website while keeping the same domain.
If the migration is handled incorrectly, Google may suddenly encounter hundreds of broken URLs, missing pages, redirect chains, duplicate content, or inaccessible resources.
The result can be a significant loss of organic traffic.
The good news is that you can migrate a WordPress website without losing SEO if you plan the migration properly and verify every important URL before and after the change.
This guide explains exactly how to migrate a WordPress website while protecting your existing rankings, backlinks, indexed pages, metadata, internal links, and organic traffic.
What Is a WordPress Website Migration?
A WordPress migration is the process of moving a website from one environment, domain, platform, or URL structure to another.
Common examples include:
- Moving WordPress to a new hosting provider
- Changing your domain name
- Moving from HTTP to HTTPS
- Moving from another CMS to WordPress
- Changing the URL structure
- Rebuilding an existing WordPress website
- Moving from staging to production
- Migrating from one WordPress installation to another
- Moving from a subdomain to a primary domain
- Combining multiple websites into one
Not every migration has the same SEO risk.
For example, moving a WordPress website from one hosting provider to another while keeping the same domain and URLs is usually much less risky than changing both the domain and URL structure at the same time.
The more URLs, domains, and technical elements you change, the more carefully the migration needs to be planned.
Can You Migrate WordPress Without Losing Google Rankings?
Yes.
A properly executed migration can preserve most or all of your existing SEO value.
However, there is an important distinction between moving the website and changing the website.
If you move the site to a new server while keeping:
- The same domain
- The same URLs
- The same content
- The same internal links
- The same metadata
- The same indexability settings
the SEO risk is relatively low.
The risk increases when you change URLs, remove pages, rewrite content, change the domain, or alter your site’s architecture during the migration.
That’s why the safest approach is:
Migrate first. Optimize later.
Avoid making dozens of unrelated SEO changes during the same migration unless they are absolutely necessary.
Why WordPress Migrations Can Cause SEO Problems
There are several ways a migration can negatively affect organic search performance.
Common problems include:
- Pages returning 404 errors
- Missing 301 redirects
- Incorrect redirect destinations
- Changed URL structures
- Missing title tags
- Missing meta descriptions
- Incorrect canonical URLs
noindexaccidentally enabled- Robots.txt blocking important pages
- Broken internal links
- Missing images
- Lost structured data
- Incorrect XML sitemaps
- HTTPS configuration problems
- Domain redirects configured incorrectly
- Staging URLs accidentally indexed
- Google Search Console verification being lost
- Slow server response after migration
- Changes to WordPress settings
- Plugin or theme conflicts
Even a technically successful migration can become an SEO failure if these details are overlooked.
Before You Start: Create a WordPress Migration Backup
Before touching your production website, create a complete backup.
Your backup should include:
- WordPress files
- WordPress database
- Media uploads
- Themes
- Plugins
- Configuration files
- Important server settings
- Existing redirects
Ideally, keep at least one backup outside the hosting account you’re migrating from.
This gives you a recovery point if something goes wrong.
You should also verify that the backup actually works rather than assuming that a backup plugin successfully created a usable copy.
Step 1: Crawl Your Existing Website
Before migration, create a complete inventory of your current URLs.
This is one of the most important SEO steps.
You need to know which URLs currently exist so you can compare them with the migrated website.
Your crawl should identify:
- URLs
- Status codes
- Title tags
- Meta descriptions
- Canonical URLs
- H1 headings
- Internal links
- Images
- Indexability
- Redirects
Pay particular attention to URLs that already receive organic traffic or backlinks.
If you don’t know what exists before the migration, it becomes much harder to determine what went wrong afterward.
Step 2: Export Your Existing SEO Data
Before migrating, save your current SEO information.
Depending on the SEO plugin you use, this may include:
- SEO titles
- Meta descriptions
- Canonical URLs
- Robots directives
- Schema settings
- Open Graph information
- Redirects
- Sitemap configuration
If you’re using Rank Math, Yoast SEO, or another SEO plugin, make sure the relevant settings and metadata are preserved.
Don’t assume that installing the same plugin on the new website automatically means every SEO setting will be identical.
Step 3: Create a Complete URL Mapping
If URLs will change during the migration, create a URL mapping spreadsheet.
For example:
| Old URL | New URL | Redirect |
|---|---|---|
/old-page/ | /new-page/ | 301 |
/services/old-service/ | /services/new-service/ | 301 |
/blog/example-post/ | /blog/example-post/ | No redirect |
Every important old URL should have a clear destination.
The best redirect destination is usually the most relevant equivalent page, not simply the homepage.
For example:
/wordpress-speed-guide/
should not automatically redirect to:
/
if the new site contains a directly relevant speed optimization page.
A relevant redirect provides a much better user experience and preserves the relationship between the old and new content.
Step 4: Keep URLs the Same Whenever Possible
One of the easiest ways to reduce migration risk is to avoid changing URLs unnecessarily.
If your current page is:
example.com/wordpress-seo-guide/
and there is no compelling reason to change it, keep it exactly the same.
Changing URLs creates additional work because you now need to:
- Create redirects
- Update internal links
- Update canonical URLs
- Update sitemaps
- Check backlinks
- Verify redirects
- Monitor indexing
If you’re rebuilding the design but don’t need to change the URL structure, don’t change the URL structure.
This is particularly important for websites that already have established rankings and backlinks.
Step 5: Build and Test the New WordPress Website on Staging
Before changing your live website, build the new version on a staging environment.
A staging site allows you to test:
- WordPress
- Themes
- Plugins
- Forms
- Navigation
- Internal links
- SEO settings
- Redirects
- Images
- Performance
- Mobile responsiveness
It also allows you to identify problems without immediately affecting your production website.
For a detailed explanation of staging, see our guide:
How to Safely Update & Test WordPress Websites Using Staging Environments
Step 6: Prevent the Staging Website From Being Indexed
Your staging website should generally not appear in Google’s index.
Otherwise, you can accidentally create duplicate content or allow Google to discover URLs that were never intended to be public.
Common approaches include:
- HTTP authentication
- Password protection
noindex- Appropriate robots configuration
However, remember that robots.txt alone is not always the best method for preventing indexing because blocked URLs can still potentially appear in search results without their content being crawled.
The safest approach is to keep the staging environment protected from public access whenever possible.
Step 7: Migrate WordPress Files and Database
Once the staging website has been thoroughly tested, migrate the website.
A WordPress installation generally consists of:
- WordPress core files
- Themes
- Plugins
- Uploads
- Database
The database is particularly important because it contains much of the website’s content and configuration.
After migration, check:
- Site URL
- Home URL
- Database connections
- Permalinks
- Media URLs
- Plugin configuration
- Theme settings
- Custom post types
- Forms
- Widgets
- Menus
Be careful when performing search-and-replace operations in a WordPress database.
Some WordPress data is stored in serialized formats, so using tools that understand serialized data is important.
Step 8: Check WordPress Permalink Settings
After migration, go to:
Settings → Permalinks
Review your permalink structure.
If the URL structure should remain unchanged, make sure it matches the original website.
Even if nothing appears to have changed, saving the permalink settings can regenerate WordPress rewrite rules.
However, don’t use this as a substitute for properly configuring server redirects.
Step 9: Implement 301 Redirects
If URLs have changed, configure permanent redirects from the old URLs to the new URLs.
For example:
→
A 301 redirect tells browsers and search engines that the page has permanently moved.
Your redirects should:
- Point directly to the final URL
- Avoid unnecessary redirect chains
- Avoid redirect loops
- Preserve relevant page relationships
- Cover important old URLs
Avoid redirect chains
Don’t create:
Old URL → Temporary URL → Another URL → Final URL
Instead:
Old URL → Final URL
Direct redirects are cleaner and generally more efficient.
Step 10: Update Internal Links
Your website shouldn’t continue linking to old URLs after migration.
Search your website for links pointing to:
- Old domains
- Old URLs
- HTTP versions
- Staging URLs
- Deleted pages
Update internal links to point directly to the final URLs.
This is better than relying on redirects for every internal link.
For example, if your page currently links to:
http://example.com/old-page/
and the final URL is:
update the internal link directly.
Step 11: Check Canonical URLs
Canonical tags tell search engines which URL should be treated as the preferred version of a page.
After migration, verify that canonical URLs point to the correct live URLs.
Common mistakes include canonical URLs pointing to:
- The old domain
- HTTP instead of HTTPS
- Staging URLs
- Old URL structures
- Incorrect pages
This is especially important when migrating between domains or changing URL structures.
Step 12: Verify Your Robots.txt File
Check the live site’s robots.txt file after migration.
Make sure important sections of the website aren’t accidentally blocked.
A common migration mistake is moving a staging configuration to production.
For example, a development environment may have been configured to discourage search engines from crawling the site.
If that configuration remains after launch, your new website could experience serious indexing problems.
Step 13: Generate and Submit a New XML Sitemap
After migration, check your XML sitemap.
It should contain the correct live URLs.
Your sitemap shouldn’t contain:
- Staging URLs
- HTTP URLs when HTTPS is canonical
- Redirected URLs
- 404 pages
- Duplicate URLs
- Incorrect domains
If your website uses Rank Math, Yoast SEO, or another SEO plugin, the sitemap is usually generated automatically.
After confirming it is correct, submit it through Google Search Console.
Step 14: Verify Google Search Console
Make sure you can access the correct Google Search Console property after the migration.
Check:
- URL indexing
- Sitemap status
- Page indexing
- HTTPS status
- Core Web Vitals
- Crawl statistics
- Search performance
- Security issues
If you changed domains, you’ll also need to make sure the new domain is verified.
Step 15: Test Every Important Redirect
Don’t assume redirects work because you created them.
Test them.
Important URLs should return the expected response and ultimately resolve to the correct destination.
Test:
- Homepage
- Main service pages
- Blog posts
- High-traffic pages
- Pages with backlinks
- Old URLs
- Category pages
- Important media URLs where relevant
A redirect audit is particularly important after large migrations.
Step 16: Check for 404 Errors
After the migration, crawl the website again.
Compare the new crawl with your pre-migration crawl.
Look specifically for:
- 404 errors
- 5xx errors
- Redirect chains
- Redirect loops
- Broken internal links
- Missing images
- Incorrect canonical tags
- Noindex pages
- Incorrect URLs
If an important page returns a 404 after migration, fix it as soon as possible.
Step 17: Check Your Website’s SEO Metadata
Compare the old and new versions of important pages.
Check:
Title tags
Make sure important SEO titles were preserved.
Meta descriptions
Verify that your descriptions weren’t accidentally deleted.
Headings
Check that important H1 and H2 headings still exist.
Canonicals
Make sure canonical URLs are correct.
Robots directives
Confirm that important pages aren’t accidentally marked noindex.
Structured data
Verify that schema markup still exists and is valid.
A migration should not silently remove SEO elements that took months to implement.
Step 18: Check Images and Media
Image URLs can also break during a migration.
Test:
- Featured images
- Content images
- Logos
- SVG files
- PDFs
- Downloadable files
- Background images
- WebP files
Also check whether image paths have changed.
Broken images can damage user experience and may indicate that the migration did not correctly transfer the media library.
Step 19: Check WordPress Plugins and Themes
A migration can expose plugin and theme conflicts.
For example, a plugin may depend on a particular PHP version or server configuration.
After migration, test:
- Contact forms
- WooCommerce
- Payment gateways
- SEO plugins
- Caching plugins
- Security plugins
- SMTP
- Analytics
- Search
- Membership systems
- Custom functionality
If you encounter unexpected behavior, our guide on How to Diagnose and Resolve WordPress Plugin and Theme Conflicts can help you systematically identify the cause.
Step 20: Test Forms and Email Delivery
Forms are easy to overlook during a migration.
Submit every important form yourself.
Check that:
- The form submits successfully
- Validation works
- Confirmation messages appear
- Emails arrive
- Notifications reach the correct recipients
- Spam protection works
- Thank-you pages load correctly
If WordPress emails are unreliable after migration, SMTP can help improve email delivery.
See our guide:
How to Setup Free SMTP Email Delivery in WordPress (Fix Emails Going to Spam)
Step 21: Test WooCommerce Carefully
If you’re migrating an online store, the process requires additional testing.
Check:
- Products
- Product URLs
- Categories
- Variations
- Cart
- Checkout
- Payment gateways
- Shipping
- Taxes
- Customer accounts
- Order emails
- Coupons
- Inventory
- Transaction status
Even a migration that looks perfect from an SEO perspective can cause serious revenue problems if checkout or payments stop working.
For a deeper WooCommerce reference, see our WooCommerce From Beginner to Advanced: The Complete 2026 Guide.
Step 22: Verify SSL and HTTPS
If the website is moving to a new server, make sure SSL is correctly configured.
Your website should load securely over HTTPS.
Check:
and verify that:
- The certificate is valid
- HTTP redirects to HTTPS where appropriate
- Images load over HTTPS
- CSS loads over HTTPS
- JavaScript loads over HTTPS
- Internal links use HTTPS
- Canonical URLs use HTTPS
For a complete walkthrough, read:
SSL & HTTPS Setup for WordPress: Complete Guide to Secure Your Website
Step 23: Check Website Speed After Migration
Never assume that the new server will perform exactly like the old server.
Test your website after migration.
Compare:
- Server response time
- Page loading speed
- Core Web Vitals
- Largest Contentful Paint
- Cumulative Layout Shift
- Interaction to Next Paint
- Mobile performance
- Desktop performance
Run tests on several important page types rather than testing only the homepage.
For example:
- Homepage
- Blog post
- Service page
- Contact page
- WooCommerce product
- Category page
If the site becomes slower after migration, investigate caching, server resources, plugins, database performance, CDN configuration, and other infrastructure differences.
Step 24: Keep the Old Website Available Temporarily
Don’t immediately delete the old hosting account after migration.
Keep the previous environment available for a reasonable transition period if possible.
This gives you a fallback if you discover:
- Missing files
- Missing images
- Incorrect database data
- Broken redirects
- Missing content
- Configuration problems
However, don’t leave the old website publicly accessible on the same domain in a way that creates duplicate content.
The goal is to preserve a recovery option, not to operate two competing versions of the website.
Step 25: Monitor Organic Traffic After Migration
SEO monitoring doesn’t stop when the new website goes live.
Monitor the site closely during the following weeks.
Watch:
- Organic traffic
- Organic rankings
- Indexed pages
- Impressions
- Clicks
- Crawl errors
- 404 pages
- Server errors
- Redirects
- Search Console warnings
Don’t panic if rankings fluctuate slightly immediately after a major migration.
Search engines may need time to recrawl and process the changes.
However, a significant and sustained decline should trigger an investigation.
WordPress Migration SEO Checklist
Before launching your migrated website, use this checklist.
Before Migration
- Create a complete backup
- Crawl the existing website
- Export important SEO data
- Record important URLs
- Identify high-traffic pages
- Identify pages with valuable backlinks
- Record existing redirects
- Create a URL mapping if URLs will change
- Build the new website on staging
During Migration
- Transfer WordPress files
- Transfer the database
- Transfer media files
- Configure the new server
- Verify the domain
- Configure SSL
- Check WordPress URLs
- Configure redirects
- Update internal links
- Verify canonical URLs
Before Launch
- Check robots.txt
- Remove staging restrictions where necessary
- Check XML sitemap
- Check title tags
- Check meta descriptions
- Check schema
- Check indexability
- Test forms
- Test WooCommerce
- Test mobile performance
- Check broken links
- Check images
- Check 404 errors
After Launch
- Verify Google Search Console
- Submit the XML sitemap
- Crawl the live website
- Test 301 redirects
- Monitor 404 errors
- Monitor rankings
- Monitor organic traffic
- Monitor indexing
- Monitor server performance
- Keep backups available
Common WordPress Migration SEO Mistakes
1. Changing URLs Without Redirects
This is one of the biggest mistakes.
If an old URL has backlinks and rankings, simply deleting it can cause the website to lose valuable signals.
Use a relevant 301 redirect whenever the content has moved.
2. Redirecting Everything to the Homepage
Redirecting hundreds of unrelated pages to the homepage is not a proper replacement for mapping URLs to their relevant destinations.
Create redirects based on content relevance.
3. Forgetting the Noindex Setting
A staging website may intentionally use a noindex configuration.
If that setting is carried over to production, search engines may be prevented from indexing your pages.
Always verify indexability after launch.
4. Forgetting HTTPS
A migration can expose mixed-content problems or incorrect redirects.
Verify that the entire website works correctly over HTTPS.
5. Changing Everything at Once
A migration is already a major change.
If you simultaneously:
- Change the domain
- Change URLs
- Rewrite every article
- Change the navigation
- Change the theme
- Delete pages
- Change categories
- Change internal linking
it becomes much harder to determine why rankings changed.
When possible, separate major changes into controlled phases.
6. Not Crawling the Website After Migration
A website can look perfect to a human visitor while still containing hundreds of technical SEO problems.
Always crawl the live website after launch.
How Long Does It Take for SEO to Recover After a WordPress Migration?
There is no universal recovery time.
A simple hosting migration where the domain, URLs, content, and technical SEO configuration remain unchanged may have little noticeable SEO impact.
A domain migration or major URL restructuring can take longer because search engines need to discover, crawl, process, and understand the changes.
The most important factor is not simply waiting.
It’s making sure the migration is technically correct.
If rankings drop, investigate the cause rather than assuming that Google simply needs more time.
Should You Migrate WordPress During a Traffic Peak?
Ideally, schedule a migration during a period of relatively low traffic.
However, don’t obsess over finding a completely inactive period.
A well-prepared migration can be performed at almost any reasonable time.
The most important things are:
- Have a tested backup.
- Have the new website ready.
- Have your redirects prepared.
- Know how to roll back if necessary.
- Monitor the website immediately after launch.
For large websites, a carefully planned migration window is especially important.
Should You Change Your SEO Strategy During a Migration?
Generally, no.
A migration is not the best time to completely reinvent your SEO strategy.
If the existing website has valuable rankings, content, backlinks, and traffic, preserve those assets first.
Once the migration is stable, you can begin making improvements.
This creates a cleaner distinction between:
Migration problems
and
SEO strategy changes.
That distinction can save a huge amount of troubleshooting time.
Final Thoughts: How to Migrate WordPress Without Losing SEO
Migrating a WordPress website doesn’t have to mean losing rankings or organic traffic.
The key is preparation.
Before the migration, document your existing website, crawl important URLs, create backups, export SEO information, and prepare your redirect strategy.
During the migration, preserve URLs whenever possible and make sure your WordPress configuration, SEO settings, canonical URLs, internal links, SSL, and sitemap are correct.
After launch, crawl the new website, test redirects, verify Google Search Console, check indexing, and monitor organic traffic and rankings.
The safest WordPress migration strategy is simple:
Document → Backup → Test → Migrate → Redirect → Verify → Monitor
Don’t treat migration as simply moving WordPress files from one server to another. Treat it as an SEO-critical website project.
When properly planned, you can move your WordPress website to a new host, domain, platform, or structure while protecting the SEO value you’ve already built.
Ready to Build a Better WordPress Website?
A successful WordPress website requires more than installing a theme and publishing content. You also need the right approach to performance, SEO, security, maintenance, and optimization.
If you want to go deeper and learn how to build, optimize, and manage professional WordPress websites, check out the WP Flow Mastery WordPress eBook.
Get the WP Flow Mastery WordPress eBook →
Written by Nemanja Stosic
WordPress Developer & Website Optimization Specialist
Nemanja helps businesses and freelancers build, optimize, and maintain professional WordPress websites focused on performance, SEO, security, and usability.