WordPress
WordPress domain change: how to update URLs safely
A WordPress domain change is different from moving the same hostname to another server. The public address itself changes, so WordPress configuration, stored absolute URLs, TLS, redirects, third-party integrations, and search-engine discovery all need a deliberate transition.
Prepare the new domain before changing WordPress
Confirm ownership, DNS control, the intended canonical hostname, and a valid HTTPS path for the new domain. Keep the old domain under your control so it can redirect visitors and search engines after the change.
Update WordPress URLs with application-aware tooling
The WordPress Address and Site Address are only part of the change. Themes, plugins, widgets, page builders, and content can store absolute URLs, including serialized values that should be updated with WordPress-aware search-and-replace tools rather than blind database text replacement.
Redirect the old hostname to matching new URLs
Use permanent redirects from old pages to their closest equivalents on the new domain instead of sending every request to the homepage. Update internal links, canonical output, sitemaps, analytics, integrations, and any application callback URLs that depend on the hostname.
Verify HTTPS, login, forms, email, and search discovery
Test the new public domain from outside the server, including administrator login, cookies, forms, checkout, images, mixed content, outbound email, scheduled jobs, and APIs. Keep the old-domain redirects working while search engines and users learn the new address.