Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

SEO & AI search · Guide

How to Move a WordPress Site Without Losing SEO

Short answer

To move a WordPress site without losing SEO, copy the files and database to the new location, update the WordPress and site addresses, and redirect every old URL to its matching new URL with a permanent 301 redirect. Then update canonical tags, internal links and the sitemap, verify both sites in Search Console, and keep the redirects live for at least one year.

Key takeaways

  • Redirect every old URL to its matching new page with a 301 redirect, not to the home page.
  • Google says 301 and other permanent redirects do not cause a loss in PageRank, as of November 2026.
  • Keep site-move redirects live for at least one year, and keep paying for the old domain for at least one year.
  • The Search Console Change of Address tool works for 180 days and needs you to own both properties under one Google account.
  • Each new URL needs a self-referencing canonical tag, and the sitemap must list only new URLs.
  • For medium-sized sites, Google says it can take a few weeks or more before new URLs replace old ones in results.

What does moving a WordPress site without losing SEO mean?

It means every old URL still reaches the same page at its new address, so visitors and Google find the content without a dead end.

A site move changes URLs in several ways, and Google Search Central lists HTTP to HTTPS, a domain name change, and URL path changes as examples. The files, the database, the addresses and the redirects all have to change together.

SEO is lost when old pages return errors, redirect to the wrong page, or point Google at two versions of the same content. A clean move keeps one live version of each page and one clear path to it.

What should you do before you move?

Make a full backup, list every live URL, and test the new site before you point visitors at it.

Start with a backup of the files and the database, and keep a copy you can restore. Duplicator advises creating a complete backup before any migration to protect against data loss.

Next, export a list of your current URLs from your sitemap and Search Console. Note the pages with traffic, links, forms and payments, because those need a correct redirect first.

Then build the new site in a place Google and visitors cannot reach yet. Google advises preparing and testing the new site fully before the move, and changing only one thing at a time where you can.

  • Back up files and database, and test the backup.
  • List every URL, including posts, pages, categories and media pages.
  • Check the new host has a TLS certificate if the new address uses HTTPS.
  • Note login details for hosting, DNS, WordPress admin and Search Console.
  • Pick a low-traffic time for the switch, as Google suggests timing a move to coincide with lower traffic.

How do you move the files and database?

Use a migration plugin to copy the files and database, or copy them by hand and update the database connection.

A plugin move is the simplest route for most sites. With Duplicator, go to Duplicator » Backups » Add New in the dashboard, choose the Full Site preset, and download the archive. Duplicator documents this flow on its own migration guide.

Upload the archive and the installer file to the new server, create a new database there, then run the installer and enter the new database name, username, password and host. The installer also updates stored URLs for the new address.

All-in-One WP Migration works in a similar way, and ServMask documents the export and import steps on its own blog. Go to All-in-One WP Migration > Export, choose Export To > File, and save the .wpress file.

Then install WordPress and the same plugin on the new host, go to All-in-One WP Migration > Import, and upload the .wpress file. ServMask notes that the import replaces the destination site, so keep your backup safe.

After the import, log in with the old site username and password, because the database now holds the old accounts. Then go to Settings > Permalinks and click Save Changes to flush the rewrite rules.

For a host-only move with no URL change, the steps are shorter. The guide to changing hosting without losing SEO covers that case, where the domain and paths stay the same.

How do you change the WordPress address?

Change both address fields in Settings > General to the new address, with https and no trailing slash.

WordPress stores two addresses. The WordPress Address (URL) is where the core files live, and the Site Address (URL) is the address visitors type to reach the site. WordPress Developer Resources explains both fields in its guide to giving WordPress its own directory.

On a normal site the two values are the same. If WordPress lives in a subfolder while the site shows at the root, the values differ, so check before you save.

If the dashboard is locked out after a bad address change, add two lines to wp-config.php above the line that reads “That's all, stop editing! Happy publishing.”:

define( 'WP_HOME', 'https://www.example.com' );
define( 'WP_SITEURL', 'https://www.example.com' );

Those constants override the database values, and the General settings fields become greyed out while they are set. Remove them later if you want to edit the addresses in the dashboard again.

Changing the two addresses does not fix links and image paths inside posts. Those stored URLs still point at the old address until you run a search and replace that handles serialized data.

A plain find and replace can break widget and theme settings, because some values store the length of the URL. Use a migration plugin or a search-and-replace tool that updates those lengths for you.

How do you set up 301 redirects?

Redirect each old URL to the same page at its new address with a permanent server-side 301 redirect.

A 301 redirect tells browsers and Google that a page has moved for good. Google Search Central calls a permanent server-side redirect the best way to direct Google Search and people to the correct page.

Build a redirect map first, with one row per old URL and its matching new URL. Send a deleted page to the closest related page, not to the home page, and let a page with no match return a 404 or 410 status.

Move typeRedirect to useWhat to check
Domain change301 from each old URL to the same path on the new domainEvery path keeps its match
HTTP to HTTPS301 from each http URL to its https versionNo mixed http links remain
Path change301 from each old path to its new pathNo redirect chains form
Deleted pageClosest related page, or a 404 or 410No redirect to the home page

Google says 301 and other permanent redirects do not cause a loss in PageRank, as of November 2026. That statement comes from its site move guide, which also warns to expect temporary ranking fluctuation while Google recrawls the site.

Avoid chains, where one redirect points to another redirect. Googlebot follows up to 10 redirect hops, according to Google Search Central, but a direct redirect to the final URL is the safer choice.

If your host uses Apache, redirects often live in .htaccess. If it uses Nginx, they live in the server block. Ask your host which file to edit if you are unsure.

A redirect plugin can work for a small set of URLs. For a full domain move, a server-level redirect is more reliable, and the guide to using Yoast SEO redirects covers the plugin route for single URLs.

How do you tell Google about the move?

Verify both the old and new sites in Search Console, then use the Change of Address tool for a domain or subdomain move.

The Change of Address tool tells Google that your site has moved from one domain or subdomain to another. Search Console Help states that you must be an owner of both the old and new properties, using the same Google account for both.

The tool works only on domain-level properties. You cannot use it on a path-level property such as example.com/petstore/, and it does not move subdomains below the domain you name, including www.

Before you submit, put the 301 redirect from the old home page to the new home page in place. Search Console Help also recommends 301 redirects for the canonical pages on the old site.

The effects of a Change of Address request last 180 days from the start of the migration, according to Search Console Help. After that period Google no longer recognises a relationship between the old and new sites.

Do not use the tool for a host-only move, an HTTP to HTTPS switch, or a www to non-www change on the same domain. Those moves need redirects and updated canonicals, not a Change of Address request.

Point every canonical tag, internal link and sitemap entry at the new address, and submit the new sitemap in Search Console.

A canonical tag is a link element that names the preferred URL for a page. Google says each new URL should have a self-referencing rel=“canonical” tag, which means the tag points at the page itself.

Update internal links so they point straight at the new URLs instead of relying on redirects. Check menus, widgets, footers, image links and links inside posts.

If your pages use hreflang annotations for other languages or regions, update those to the new URLs too. Google lists this step in its site move guide, alongside updating annotations in the sitemap.

Then submit the new sitemap in Search Console, and remove the old sitemap once Google uses the new one. Google says a sitemap can help discovery go faster, and its Sitemaps report shows how many submitted URLs have been indexed.

Check the robots.txt file as well. Its Sitemap line should name the new sitemap address, and it must not block the old URLs before Google has followed their redirects.

How long does Google take to show the new URLs?

For a medium-sized site, expect a few weeks or more, and longer for a large site.

Google states this timing in its site move guide. The speed depends on the number of URLs and your server speed, because Googlebot must visit every URL on the old and new site at least once.

Keep the redirects live for at least one year, as Google recommends in the same guide. Search Console Help gives a shorter floor of at least 180 days, and says to keep them longer if Google Search still sends traffic to them.

Keep paying for the old domain for at least one year too. Search Console Help recommends this so nobody else can buy the abandoned domain and use it for harmful purposes.

DNS changes add their own wait. Duplicator notes that DNS propagation can take 24 to 48 hours, so do not delete the old hosting account until the new site is fully live. The guide on how long DNS propagation takes explains what to check while you wait.

How do you check the move worked?

Open old URLs, check their status codes and targets, then watch Search Console for the new URLs being indexed.

Start by clicking or pasting a sample of old URLs. Each one should return a 301 status and land on the matching new page, with no chain and no home page redirect.

Then check the new site page by page. Look for broken images, missing styles, login errors and forms that still post to the old address.

  • Every old URL returns 301 to its matching new URL.
  • New pages return 200 and show the correct canonical tag.
  • The new sitemap lists only new URLs and loads without errors.
  • Search Console shows the new property being crawled and indexed.
  • The old property shows indexed old URLs falling over time.
  • No staging address, password prompt or noindex tag leaks onto the live site.

In Search Console, compare the old and new sitemaps. Google says the new sitemap starts with zero pages indexed, while the old one has many, and over time the old count drops to zero as the new count rises.

Fix any 404 errors that appear in the Coverage or Pages report. A 404 means Google found a link to a URL that no longer exists, so add a redirect or restore the page.

What mistakes should you avoid?

Do not redirect everything to the home page, change the design at the same time, or drop the old domain too soon.

A blanket redirect to the home page gives visitors the wrong page and wastes the value of the old URLs. Map each old URL to its closest match instead.

Do not launch a redesign, a content rewrite and a URL change in one go. Google advises changing only one thing at a time, because too many changes at once make it hard to find what went wrong.

Do not block the old site with robots.txt before Google follows the redirects. The old URLs must stay reachable so Google can find the redirect and the canonical signal on the new page.

Do not forget the small places where the old address hides. Check the sitemap, robots.txt, canonical tags, hreflang, structured data, email signatures, social profiles and paid ads.

Do not skip the backup or the redirect map. Without them, a failed import or a missing redirect is hard to undo, and the detailed steps for migrating with Duplicator start with a backup for that reason.

The same applies to the other plugin route. The steps for migrating with All-in-One WP Migration also start with a backup, and its import replaces the destination site.

Frequently asked questions

Can I move a WordPress site to a new host without changing the domain?

Yes. If the domain and paths stay the same, you only need to copy the files and database to the new host and update wp-config.php with the new database details. No 301 redirects and no Change of Address request are needed, because no URL has changed. Still back up first, test the new copy, and check that pages, images and forms work before you switch DNS.

How long should I keep 301 redirects after a domain change?

Keep them for at least one year, following Google Search Central guidance. Search Console Help gives a floor of at least 180 days, and says to keep redirects longer if Google Search still sends traffic to them. Keep paying for the old domain for at least one year as well, so nobody else can register it and use it for harmful purposes.

Will my rankings drop after moving a WordPress site?

Google warns to expect temporary fluctuation in rankings during a move while it recrawls and reindexes the site. For medium-sized sites this can take a few weeks or more. A correct redirect map, updated canonicals and a submitted sitemap limit the damage, but Google does not give a fixed date by which rankings return to normal.

Do I need the Change of Address tool for an HTTP to HTTPS move?

No. The Change of Address tool is for moving from one domain or subdomain to another, and it does not apply to an HTTP to HTTPS switch or a www to non-www change on the same domain. For those moves, use 301 redirects from each old URL to its new version, update canonical tags and the sitemap, and verify the new HTTPS property in Search Console.

What should I do if an old URL has no matching page on the new site?

Redirect it to the closest related page with similar content, if one exists. If no related page exists, let the old URL return a 404 or 410 status instead of sending visitors to the home page. Check Search Console afterwards for 404 errors, and add redirects for any old URL that still receives traffic or links.

Sources

  1. Site Moves and Migrations Google Search Central
  2. Redirects and Google Search Google Search Central
  3. Change of Address tool Search Console Help
  4. Giving WordPress Its Own Directory WordPress Developer Resources
  5. How to Migrate a WordPress Site Duplicator
  6. How to Migrate WordPress to a New Host Without Breaking Anything ServMask

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test