Changing a domain name is one of the riskiest things you can do to an established website’s search presence. Every ranking, every backlink and every bookmark points to the old address. If the move is done carelessly, search engines treat the new domain as a brand-new site, and traffic can drop sharply for months. If you need to change domain name in WordPress, the process below keeps the risk as low as possible.
Done carefully, a domain change can be almost invisible to search engines. Traffic may dip briefly, then recover within weeks. I’ve moved sites with years of history this way with little or no lasting loss.
The difference comes down to preparation, complete redirects and patient monitoring.
Reasons to change, and reasons to pause
Common reasons include rebranding, merging businesses, moving from a country domain to a global one or the other way round, or replacing an awkward early domain with a better one.
Before committing, be honest about the trade-off. A domain change always carries some risk. If the main motivation is a slightly nicer name, the cost may not be worth it. If it’s a full rebrand that the business depends on, it is.
Also avoid combining a domain change with other big changes, like a redesign, new URL structure or new content, all at the same time. Each change adds risk, and when something goes wrong, you won’t know which change caused it. If you can, move the domain with the site otherwise unchanged, then redesign later.
Step 1: Prepare the new domain
- Register the new domain well in advance.
- Check its history. Use the Wayback Machine and search for it to see whether it was previously used for spam. A domain with a bad history can bring problems with it.
- Set up DNS, hosting and an SSL certificate for the new domain.
- Add the new domain to Google Search Console and Bing Webmaster Tools as a new property, and verify it.
Step 2: Benchmark and inventory
Before touching anything, record where you are:
- Export top pages and queries from Search Console for the past few months.
- Record organic traffic in analytics.
- Crawl the entire old site with a tool like Screaming Frog and save the list of every URL.
- Export your backlink profile from an SEO tool, noting the most valuable linking domains and the pages they link to.
The crawl list is critical. It becomes your redirect map and your checklist.
Step 3: Map every URL
If URL paths stay the same and only the domain changes, mapping is simple: every old URL redirects to the same path on the new domain. That’s the safest kind of move.
If any paths change, create an explicit map of old URL to new URL. Every page that has traffic, rankings or backlinks must have a specific destination. Don’t redirect everything to the new homepage. That’s treated as a soft 404 and loses most of the value.
Step 4: Move WordPress to the new domain
On a staging copy or directly on the new hosting:
- Copy files and database to the new location.
- Update the site URL and home URL.
- Run a search-replace across the database to replace the old domain with the new one.
WP-CLI’s search-replace handles serialised data correctly, which is essential, because many plugins store URLs inside serialised arrays:
Run it with –dry-run first to see how many replacements will be made, then without it to apply. Also replace variations such as http:// versions and the www or non-www form, if they appear in the database.
Never use a plain text find-and-replace on a SQL export. It breaks serialised data and corrupts settings.
- Check hardcoded URLs in theme files, custom CSS and page builder data.
- Update email settings, so notifications come from the new domain, and set up email authentication records for the new domain if you send mail from it.
Step 5: Test the new site before launch
With the new domain not yet public, or protected by a password, check:
- Every page type loads correctly
- Images, CSS and JavaScript load from the new domain, not the old one
- Forms submit and emails arrive
- Checkout works for stores, including payment gateway return URLs and webhooks
- No links point to the old domain, which a crawl will reveal
- Canonical tags, sitemaps and structured data use the new domain
Step 6: Set up 301 redirects
On launch day, configure the old domain to redirect every request to the corresponding URL on the new domain with a 301 permanent redirect. Path-preserving redirects are best done at the server level.
On Nginx, for the old domain’s server block:
On Apache, in the old domain’s .htaccess:
The old domain needs a valid SSL certificate too, because many visitors and links will request the HTTPS version. Without it, browsers show an error before the redirect happens.
Redirect directly to the final URL. Avoid chains like old domain to new domain HTTP to new domain HTTPS to new domain with trailing slash.
If paths changed, add the specific mappings before the general rule.
Step 7: Tell Google with Change of Address
In Search Console, open the old domain’s property, go to Settings and use the Change of Address tool. It checks that redirects are in place and tells Google the site has moved. This speeds up the transition considerably.
The tool requires both properties to be verified and the homepage redirect to work. Bing Webmaster Tools has a similar site move feature.
Then submit the new domain’s XML sitemap in the new property.
Step 8: Update what you control
Redirects preserve most value, but direct links are better. Update:
- Google Business Profile and other business listings
- Social media profiles
- Email signatures and templates
- Paid advertising campaigns, whose destination URLs should point straight to the new domain
- Directory listings and partner sites where you can edit the link
- Your most valuable backlinks, by contacting the sites and asking for an update
You don’t need to chase every backlink. Focus on the ones that send traffic or come from highly authoritative sites.
Step 9: Monitor closely
For the first few weeks, check daily:
- Search Console for both properties: indexing in the new one should rise as the old one falls
- Crawl errors and 404s in the new property
- Organic traffic in analytics, compared with your benchmark
- Rankings for your most important queries
Some fluctuation is normal. A temporary dip of 10 to 30 percent in the first weeks isn’t unusual. If traffic falls much further, or doesn’t begin to recover within a month, check redirects, canonical tags and indexing carefully.
Step 10: Keep redirects forever
Keep the old domain registered and the redirects running for as long as possible, ideally permanently. Google recommends at least a year, but backlinks and bookmarks continue sending visitors for much longer. Letting the old domain expire also lets someone else buy it, which could be used to impersonate your business.
Renewing an old domain is a small annual cost. Losing it can be very expensive.
A realistic timeline
For a typical business site, a domain change might run like this. Two to four weeks before launch: register and check the new domain, set up hosting and Search Console, crawl the old site and build the redirect map. One week before: complete the move on staging, run the search-replace and test everything. Launch day: switch DNS or point the new domain at the live site, enable redirects on the old domain, run the Change of Address tool and submit the new sitemap. The first two weeks: daily monitoring, fixing any 404s or redirect gaps. The following two months: weekly monitoring and outreach to update important backlinks.
Plan launch for a quiet period in your business, not right before a busy season, and avoid Fridays, so there’s time to fix issues before a weekend.
Brand transition on the site itself
Visitors who arrive through old links may be confused to land on a site with a different name. For the first few months, a short note on the homepage or in the header, such as “Formerly OldBrand”, reassures them they’re in the right place. It also helps search engines connect the old and new names. Update your Organization schema with the new name and include the old name as an alternate name where appropriate. When you change domain name in WordPress this carefully, most visitors and search engines barely notice the move.
Frequently asked questions
How long does it take to recover rankings?
For well-executed moves, most traffic transfers within a few weeks, with full stabilisation in two to three months. Sites with complex changes may take longer.
Can I use the Change of Address tool for subdomains?
It’s designed for moving between domains. Moves between subdomains, such as blog.example.com to example.com/blog, use redirects and sitemaps but not the Change of Address tool in the same way.
Should I redirect old URLs to the new homepage?
Only the old homepage. Every other page should redirect to its specific equivalent. Blanket homepage redirects lose most of the old pages’ value.
What about email on the old domain?
Keep old email addresses working, or forwarding, for a long time. Customers and suppliers will keep using them for months.




