Move a self-hosted WordPress site to a new domain

Changing a blog's domain affects more than the address in the browser. WordPress stores URLs in its database, visitors may have saved old links, and search engines need a clear route to the new pages. Plan the move while you still control the old domain.

This guide covers a self-hosted WordPress site staying with the same host. A host-specific migration tool may change the steps; consult your host before modifying a live site. WordPress also has a migration guide for broader moves.

Prepare a recoverable backup

Back up both the database and site files, including uploads, themes and plugins. Save the copies away from the server and confirm your host's restore procedure. A backup is most useful when you know which files and database it covers and how to restore both together.

Record the current domain settings, hosting configuration and WordPress URLs. Make an inventory of key pages, forms, images and integrations such as analytics, email services or payment providers. If the site accepts orders or comments, plan how to handle changes made while the migration is in progress.

Connect and secure the new domain

Add the new domain to your hosting account and configure the DNS records required by your host. DNS tells visitors where to find the site; the precise records depend on the hosting setup. Arrange a valid HTTPS certificate for the new hostname before directing visitors there. Check both the intended hostname and its secure address in the host's control panel.

DNS changes can take time to reach all visitors. Avoid deleting the old domain's configuration during this transition. If your host offers a staging copy, use it to rehearse the change and inspect the result before touching the live site.

Update WordPress URLs carefully

WordPress has both a WordPress Address and a Site Address, normally available under Settings → General. Review the WordPress address documentation and your host's instructions before changing either. Entering an incorrect address can make the dashboard inaccessible, so keep the recovery instructions and backup handy.

Existing content and plugin settings may still contain the old domain. Some database values use PHP serialized data, so a blind text replacement can corrupt them. Use a migration tool that understands serialized data and supports a dry run, or ask your host for its supported process. Review the proposed replacements before applying them, and avoid changing email addresses or third-party URLs unintentionally.

Redirect and verify

Configure permanent page-to-page redirects from the old URLs to their matching new URLs. Do not send every old article to the home page if its equivalent exists. Google's site-move guidance covers redirects, sitemaps and monitoring.

Open several old links and confirm each reaches the correct HTTPS page. Check images, navigation, forms, logins, canonical URLs and the sitemap on the new domain. Update external profiles and important integrations. Keep the old domain and redirects under your control while visitors and search engines transition, and monitor errors and search performance after the move.