A WordPress domain migration redirect checklist

A domain migration needs more than a homepage redirect. Inventory the old URLs, map each useful page to its replacement, verify the destinations and retain control of the old domain so that visitors can reach the new one.

Before the move

Export the current URLs and identify important pages from your own traffic and backlink data. Include media and downloadable resources when their addresses will change. Separate pages with a direct replacement from pages that are being retired; a relevant mapping is more useful than sending everything to the new homepage.

Make an independent backup. Record where redirects will run: the old server, a CDN, WordPress or a combination. Do not assume a plugin installed only on the new domain can handle requests that still arrive at an unrelated old server.

Build and review the mapping

• Choose the final HTTPS hostname and consistent URL format.
• Map old paths to the actual new destination URLs.
• Confirm that each destination exists and is appropriate for the old content.
• Check wildcard rules against exceptions before relying on them in bulk.
• Preview the change and resolve duplicate sources or replacement conflicts.
• Keep the previous rule set and a clear rollback procedure.

RedirectNest Pro offers migration workspaces, mapping review and destination checks. Treat check results as observations at the time of the check. A destination can later change, and a successful HTTP response does not prove that the page content is the right replacement.

After switching

Test representative old URLs, including important landing pages, nested paths, parameters and retired content. Inspect the full redirect sequence and avoid unnecessary intermediate hops. Update internal links, canonical URLs and the sitemap to use the final destinations. Review search-engine migration tools separately where a domain move qualifies for them.

Monitor errors and real user reports after launch. Keep the old domain and redirects available for a planned transition period; do not remove the old infrastructure just because the new homepage loads.

Read migration workspaces, verification reports and monitoring. These are complementary checks, not a guarantee that search traffic will remain unchanged.