Changing a WordPress Domain: Check Redirects, Search Signals, and Email

You have changed the brand name and registered a new domain. The next step is usually not to edit the WordPress site address immediately. Images in posts, old social posts, search results, form notifications, and work email may still point to the former name. Create a mapping so every old entry point has a defined destination.

Imagine a craft studio switching to a domain that is easier to remember while keeping its existing tutorials. A practical outcome is that an old article link opens the same article at its new address, editors can still log in, and someone receives customer inquiries sent to the old mailbox. The steps below follow those three paths.

Map old URLs to a destination for every page

Build an inventory from the sitemap, post list, common navigation, and pages people actually visit. Include images and downloadable files. If only the domain changes, retain the existing paths initially to simplify mapping. If you also reorganize categories or remove posts, record the new destination and reason for each item.

For example, the old /workshop/ page should lead to the new course page, rather than sending every old article to the home page. When combining several posts, redirect to a new page that truly covers their information. A deleted page without a reasonable replacement should return an appropriate not-found response. Whether readers can find what they came for is the test of a sound mapping.

1. List old URLs for posts, pages, media, downloads, and important external links.
2. Assign a new URL to each and record why it is retained, combined, or removed.
3. Sample the home page, popular inner pages, Chinese-character paths, and links with query parameters.

Back up first, then preview database URL replacement

The WordPress site address is only one setting. Post content, plugin options, and page builders may store absolute URLs elsewhere. Back up files and the database, then use a migration tool that understands WordPress data formats on a restricted copy. A plain text replacement of the domain throughout an SQL dump can damage serialized data.

If a technical operator uses WP-CLI, its official search-replace command handles serialized data and offers --dry-run to report changes without writing them. Verify the table scope and the old and new URLs, then examine the expected replacement count. Do not include every table automatically, especially when other sites share the same database.

Replace only site URLs that need to change. The bare domain might also occur in email addresses, historical records, or external-service settings, so do not rename every occurrence indiscriminately. Afterwards, inspect custom theme files, CSS, menus, and plugin caches to ensure the rendered site no longer fetches resources from the old address.

Keep HTTPS working on both the old and new domains

The new domain needs correct DNS records and a valid certificate. If the old domain used HTTPS, it also needs a valid connection throughout the redirect period. The browser establishes a secure connection before receiving a redirect response. If the old certificate expires, visitors may see a warning before they can reach the new site.

Have the host or site administrator configure permanent redirects from the approved mapping, then test each old URL’s response and final destination. Google recommends server-side permanent redirects, such as 301 or 308, that reach the final page as directly as possible. Avoid rules that bounce between the apex domain, www, HTTP, and HTTPS.

1. Choose one consistent canonical-address strategy for the new domain’s apex and www names.
2. Test whether each type of old URL reaches its intended new page, not merely whether it redirects.
3. Check images, downloads, and forms for loops, missing paths, or security warnings.

Update search signals and links you control

Canonical URLs, sitemaps, and internal links on new pages should point to the new domain. Before going public, remove any indexing blocks that were only for testing. The Search Console Change of Address tool has eligibility rules; for a true move between domains, verify both properties and complete the checks required by Google.

The tool does not create redirects and cannot update every search result instantly. Google recommends keeping redirects for as long as possible, generally at least a year. Business cards, bookmarks, and third-party links still in use may justify longer support. A site move can cause temporary fluctuations; do not promise that rankings will recover within a few days.

Schedule updates to entry points you can edit: social profiles, newsletter footers, business listings, partner sites, and QR Code images in documents. Prioritize heavily used or transaction-critical items, and record an owner and completion date. Direct links to the new domain spare readers an extra wait and simplify later maintenance even while old links redirect.

Treat email as a separate service to verify

A website redirect does not automatically turn an old.example mailbox into a new.example mailbox. Ask your mail provider how to add the new domain and manage accounts or aliases, then set the MX records and sender authentication it requires. Google Workspace, for example, has a separate process for changing the primary domain and retaining old-domain aliases; WordPress settings cannot replace it.

List everyday mailboxes, form senders, reply-to addresses, and account-recovery mailboxes. Arrange to keep receiving at old addresses, tell customers about the new ones, and send test messages from an external mailbox to both domains. Confirm receipt, replies, and displayed sender addresses. For forwarding, verify delivery to the destination inbox rather than merely a saved setting.

Do not change every employee login account on the same day without a handoff list. Some third-party services identify users by email; a renamed account may need reverification or administrator changes. Identify who relies on an old address so a successful website move does not lock administrators out.

Monitor the switch through real problems

After launch, check failed URLs, form notices, and old and new inboxes regularly, and connect each issue to the URL mapping. If a post loses traffic, first check that its old URL reaches the correct page, that the new page can be indexed, and that its images and content are complete before exploring other causes.

Keep someone responsible for renewing the old domain and its certificate, as well as maintaining the redirect service. If you must roll back, first preserve content and inquiries added on the new site, then choose which settings to restore. Do not overwrite all new data with an old backup. Keep the cutover log, account entry points, and verification results together so the next administrator knows which old services must stay active.

Moving hosts without changing the URL

Checking website backup and restoration

Managing domain and hosting renewals

• Tutorials
• Apps & software
• Websites & e-commerce
• WordPress