How to Migrate a WordPress Site Without Losing SEO Rankings

WordPress migration SEO is the discipline of moving a WordPress site to a new host, domain, or URL structure while keeping its search visibility intact. The rule that matters most is simple: every URL that earns traffic or links must either stay the same or permanently redirect to its closest equivalent. Google says a site move happens per URL, and it is complete only once Googlebot has visited every URL on the old and new site at least once, so some temporary ranking fluctuation is normal.

The stakes are broad. W3Techs-based reports put WordPress at roughly 42% of all websites, which means a very large number of businesses face a migration at some point. This guide walks through a safe sequence: benchmarking, URL structure preservation, 301 redirect mapping, staging site testing, launch, and a post-migration audit.

What Is WordPress Migration SEO?

WordPress migration SEO covers the technical and strategic steps that protect organic rankings when a WordPress site changes hosts, domains, protocols, or URL paths. Its goals are to keep URLs stable or redirect them correctly, keep content and metadata intact, keep search engines able to crawl the new site, and confirm the results afterward.

Not every migration carries the same risk. The type of move decides what you need:

Google’s Change of Address tool applies only to moves between domains or subdomains, and Google says not to use it for HTTP to HTTPS moves or for hosting changes where URLs stay the same.

How Do You Prepare for a WordPress Migration? (Domain Migration Checklist)

Start by recording how the site performs today, because without a baseline you cannot prove whether the move helped or hurt. Crawl every URL, export Search Console and analytics data, and note which pages drive clicks, conversions, and backlinks.

A practical pre-migration checklist:

• Crawl the full site and export every indexable URL, with status code, title, meta description, canonical, and headings.
• Export top pages from Search Console and analytics by clicks, impressions, and conversions.
• List pages with backlinks so you can protect them first.
• Save your XML sitemap and robots.txt as they stand today.
• Verify every property variant in Search Console. Google advises verifying www and non-www, and both HTTP and HTTPS if you use HTTPS, and confirming that verification will survive the move.
• Check for leftover removal requests, especially any site-wide URL removal in Search Console.
• Plan server capacity. Google notes it will crawl a newly moved site more heavily for a while.
• Take full backups of files and the database.

If you want an independent review of the old site before you touch it, a structured website audit is the right place to catch existing problems, so you do not carry them across and later mistake them for migration damage.

How Do You Preserve URL Structure in WordPress?

Keep your URLs identical wherever possible. In WordPress, confirm that the permalink structure, category base, tag base, trailing slashes, and capitalization on the new install match the old site exactly. A URL that does not change needs no redirect, so it carries no redirect risk.

Change URLs only when there is a clear reason. Mixing a new domain, a redesign, a new permalink structure, and new content in one launch makes any traffic drop nearly impossible to diagnose. Google’s own guidance says combining a move with a redesign of content and URL structure will probably cause some traffic loss, because Google may need to reassess individual pages. Where you can, separate the changes: move first, redesign later.

How Do You Map 301 Redirects for a Migration?

To map 301 redirects, list every old URL, pair each with the most relevant new URL, and implement permanent server-side redirects that go straight to the final destination. One old URL maps to one new URL. Pages with no equivalent should return a 404 or 410 rather than redirect to the homepage.

Build the map in a spreadsheet:

Rules that prevent most redirect damage:

• Match relevance. Redirect to the page a visitor would expect, not a generic substitute.
• Avoid chains. Old URL to final URL in one hop, never old to interim to final.
• Use 301 for permanent moves. A 302 signals a temporary change.
• Do not bulk-redirect to the homepage. It discards relevance and confuses users.
• Redirect everything that has value, including images, PDFs, and feeds with links or traffic.
• Keep redirects long enough. Google’s site-move guidance says to keep them as long as possible, generally at least one year, while the Change of Address page cites at least 180 days. Treat a year as the floor.

For large maps, server-level rules in Apache or Nginx are usually faster and easier to audit than a plugin that loads on every request. Small sites can use a reputable redirect plugin.

How Do You Test a WordPress Migration on a Staging Site?

Build the new site on a staging environment that Google cannot index, then test redirects, templates, metadata, and performance before launch. Protect staging with password authentication rather than relying only on robots.txt, since a blocked URL can still appear in results if other pages link to it.

Staging site testing checklist

• Crawl staging and compare it with your old crawl: titles, descriptions, canonicals, headings, hreflang, structured data, and internal links.
• Run your redirect map against the old URL list and confirm every row returns the right status and destination.
• Check that images, PDFs, and embedded media load and keep their alt text.
• Review mobile rendering and Core Web Vitals on key templates.
• Validate structured data with a schema markup validator before it goes live.

The mistake that quietly kills traffic

The most common WordPress launch error is carrying staging settings to production. Check that Settings > Reading > “Discourage search engines from indexing this site” is unticked, that no site-wide noindex header or tag remains, and that robots.txt is not blocking the site. A robots.txt generator helps you write a clean production file, and your SEO plugin or a sitemap generator can produce a fresh sitemap for the new site.

What Are the Steps to Launch a WordPress Migration?

Launch in a low-traffic window with the redirect rules ready. Copy files and the database, update URLs safely, enable HTTPS, turn on redirects, remove staging restrictions, submit the sitemap, and test immediately.

1. Freeze content so nothing changes between the final backup and the switch.
2. Back up files and the database one last time.
3. Migrate files and database, then update URLs using a serialization-safe method such as WP-CLI’s search-replace, since a plain text replace can corrupt serialized data.
4. Install SSL and confirm every URL resolves over HTTPS.
5. Enable the redirect map and spot-test your highest-value URLs.
6. Remove noindex and crawl blocks from the new site.
7. Submit the new XML sitemap in Search Console.
8. Use the Change of Address tool only if the domain changed, from the old property, and keep redirects live for at least 180 days after it.
9. Update internal links, canonicals, and schema so they point to new URLs, not through redirects.
10. Re-crawl the live site and compare it with your baseline.

Technical errors at this stage are where specialist help pays off. Search Savvy’s technical SEO services cover the crawl, indexing, and redirect checks that a migration depends on.

How Do You Run a Post-Migration SEO Audit?

A post-migration audit compares the new site with your baseline to confirm that URLs, redirects, indexing, and traffic behave as expected. Run it the day you launch, again after one week, and again at one month, since Google processes moved URLs gradually.

Google’s guidance says how long the process takes depends on the number of URLs and how fast your server responds, and that you should monitor traffic to both old and new URLs. If rankings fall sharply and do not recover after the fixes above, the cause is often indexing or redirect errors. Search Savvy’s search engine recovery service is built for that kind of diagnosis.

Common WordPress Migration SEO Mistakes

• Leaving “Discourage search engines” ticked after launch.
• Redirecting everything to the homepage instead of relevant pages.
• Creating redirect chains through old HTTP, www, and interim URLs.
• Changing too much at once, which hides the cause of any drop.
• Removing redirects early, before Google has finished processing the move.
• Forgetting images and PDFs that hold backlinks.
• Skipping the baseline, leaving no proof of what changed.

Frequently Asked Questions

Will migrating a WordPress site hurt SEO?

Not necessarily. A well-planned migration causes only temporary fluctuation, according to Google, while rushed moves with broken redirects or noindex errors can cause lasting losses. Preparation and testing decide the outcome.

How long should you keep 301 redirects after a migration?

At least one year according to Google’s site move guidance, and longer if old URLs still receive links or traffic. Keeping them indefinitely costs little.

Do you need the Change of Address tool for a WordPress migration?

Only when you move to a different domain or subdomain. You do not need it for a hosting change or an HTTP to HTTPS move.

How long does it take for rankings to recover after a migration?

It varies with site size and server speed. Google says to expect fluctuation while URLs are reprocessed, and larger sites generally take longer, so monitor over weeks rather than days.

Should you change your permalink structure when migrating?

Avoid it unless there is a strong reason. Keeping URLs identical removes the biggest source of risk. If you must change them, do it separately from the move and redirect every old URL.

What should you check right after launch?

Confirm the site is indexable, redirects return single-hop 301s, the sitemap is submitted, canonicals point to the new URLs, and analytics are tracking.

Bottom Line

Protecting rankings during a WordPress migration comes down to three habits: keep URLs the same wherever you can, redirect every valuable old URL to a relevant new one, and test before and after launch against a recorded baseline. Treat the first month as active monitoring, not as a finished project.

Before you schedule the move, crawl your current site and build the redirect map. If you want experienced eyes on the plan, Search Savvy’s SEO services are a practical place to start.