- Article
- Intermediate
- 2 minutes read
- Reviewed August 4, 2026
- WordPress maintenance and troubleshooting
Changing a domain affects WordPress configuration, stored URLs, DNS, TLS, email, redirects, analytics and search visibility.
Updating only the WordPress Address and Site Address is rarely the complete project.
Before the Change
Inventory:
- Old and new hostnames.
- DNS records.
- certificates.
- WordPress URLs.
- hard-coded links.
- media URLs.
- canonical tags.
- sitemaps.
- redirects.
- email sender domains.
- APIs and webhooks.
- analytics and Search Console.
- licence bindings.
Create a complete backup.
Update WordPress URLs
Change the intended home and siteurl values through administration, WP-CLI or controlled configuration.
Temporary WP_HOME and WP_SITEURL constants can help recover access during troubleshooting, but they do not replace a complete database and integration update.
Replace Stored URLs Safely
Use a serialization-aware tool and run a dry test first.
Review whether GUID values, third-party data and historical records should change rather than applying an unexamined global replacement.
Redirect the Old Domain
Preserve one-to-one paths with permanent redirects.
Keep control of the old domain and HTTPS certificate so redirected traffic remains secure.
Update External Systems
Review:
- CDN and cache.
- email authentication.
- payment callbacks.
- OAuth redirects.
- webhooks.
- API allowlists.
- analytics.
- Search Console.
- social profiles.
- documentation.
Verify and Monitor
Crawl the new domain, test old URLs, submit sitemaps and monitor errors, canonical selection, email and transactions.
Frequently Asked Questions
Should every old URL redirect to the new homepage?
No. Redirect each useful old path to its matching new destination.
Can the old domain be allowed to expire immediately?
Keep it under control for long-term redirects, user trust and account recovery.
Continue Learning
Previous: How to Migrate a WordPress Website