How to Redirect an Old Domain to a New Domain Without Losing Rankings
A domain move is the one redirect job where a shortcut costs you years of rankings. Same path to same path, permanent, and keep the old domain alive.
On this page
To redirect an old domain to a new domain without losing rankings, every old URL must send a 301 to its exact equivalent on the new domain, in one hop, for a long time. The shortcut that ruins moves is forwarding the whole old domain to the new homepage: search engines treat that as a soft 404 for every inner page, and the rankings those pages had evaporate. Here is the full sequence, from before the switch to the day you can stop thinking about it.
Before the switch
Decide the URL structure. If the new domain keeps the same paths, which a rename almost always does, the job is one rule. If paths change too, you need a mapping of old URL to new URL, and the move is really two jobs: a domain change and a restructure. Do them separately if you can.
Set up the new domain fully. SSL certificate, the site installed and tested, WordPress’s site URL and home settings pointing at the new domain, and a search-replace of the old domain in the database so no post content or option still carries old URLs.
Keep the old domain alive. Registration renewed, SSL still valid, because redirects from https on the old domain need a working certificate there too. The old domain can host a near-empty site whose only job is to redirect.
Sort out email. If addresses used the old domain, decide what happens to mail sent to them. This has nothing to do with the web redirect and is the thing people forget.
The redirect itself
Same-path forwarding. When paths are unchanged, one rule says: any request to old-domain.com/anything goes to new-domain.com/anything with a 301. DevDome Redirect Manager has same-path domain forwarding as a rule type, with per-rule click counts so you can see how much traffic the old domain still sends months later, and it is free with unlimited rules. We make it, so weigh that; any redirect tool or server rule that preserves the path does the job.
All four variants. http and https, www and non-www, on the old domain, each should land on the single canonical new URL in one hop. A chain of old-http to old-https to new is slower and dilutes the signal.
301, not 302. The move is permanent. A 302 tells search engines the old URL is still the real one.
Mapped redirects for changed paths. If some URLs changed, add individual rules for those before the same-path rule, so the specific match wins.
Clear caches. A cached copy of the old site will keep serving old pages. Redirect Manager purges ten cache plugins automatically when rules change; if you use a server cache or CDN on the old domain, purge those too.
Tell search engines and fix your own links
Search Console. Verify the new domain, submit its sitemap, then use the Change of Address tool on the old property. Bing has an equivalent.
Internal links. The search-replace handled post content, but check menus, widgets, theme options and hard-coded links in templates. An internal link to the old domain that bounces through the redirect is a wasted hop on every click.
Canonical tags and sitemaps. Both must reference the new domain only.
External profiles. Social accounts, directory listings, your email signature, any place you control that links to the old domain. Update them; they are the easy links to fix.
Email, images and the things that are not pages
A domain move breaks more than page URLs. Images embedded with absolute URLs in old posts keep pointing at the old domain; the search-replace fixes the database, and the same-path redirect catches anything missed, but each is a wasted hop, so check a few posts. Feeds and podcast enclosures that subscribers fetch from the old domain need the redirect to stay for years. Email that used the old domain needs its own plan: forward the addresses, update the sender in your newsletter tool, and change the SPF and DKIM records for the new domain before the first send, or deliverability drops on day one. OAuth and API callbacks registered with the old domain, for example in a payment provider or a social login, must be updated by hand; a redirect does not help a callback.
Choosing where the redirect runs
The redirect can live in three places: DNS-level forwarding at the registrar, a server rule on the old host, or a plugin on a minimal WordPress install at the old domain. Registrar forwarding is the simplest and often cannot preserve paths or serve https correctly, which rules it out for a site with inner pages. A server rule is fast and invisible, with no click counts and easy to lose when the old hosting is cancelled. A plugin rule needs the old site kept running but gives you per-rule click counts, which is the only way to know when the old domain has stopped mattering. Pick one, and make sure the other two are not also redirecting, or you get chains.
After the switch
Test with a redirect checker. Pick twenty old URLs, including the homepage, a deep post, an image and each of the four domain variants. Every one should show a single 301 to the right new URL. The free redirect checker on this site shows each hop and status.
Watch the 404 log on the new domain. URLs that 404 on the new site after the move are paths that changed without a rule. Add rules for the ones real visitors hit.
Watch rankings for a few weeks. Some movement is normal while search engines reprocess. A sustained drop on specific pages usually means those pages redirect somewhere wrong, or chain, or 404.
Keep the old domain for at least a year. Links from other sites will point at it for years, and the redirect is what carries their value. When the click count on the forwarding rule drops to almost nothing and Search Console shows the old URLs gone from the index, you can consider letting it go. Many sites simply never do; a domain renewal is cheap insurance.
A domain move done this way is boring, which is the goal. The exciting ones are the ones where someone pointed the old domain at the new homepage and watched a decade of rankings disappear.
Related reading: How to Set Up a 404 Monitor in WordPress and Turn Misses Into Redirects.
Disclosure: DevDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.
Key takeaways
- Redirect every old URL to its exact new equivalent with a 301. A blanket redirect to the new homepage throws away the rankings of every inner page.
- Same-path domain forwarding does this in one rule when the URL structure is unchanged, which is the normal case for a rename.
- Keep the old domain registered and the redirects running for at least a year; search engines and old links need time.
- Tell Google with the Change of Address tool, update your sitemap and internal links, and watch the 404 log on the new domain.
- Check email, SSL on both domains and any hard-coded old URLs in the database before the switch.
Sources
- Google Search Central: Site moves with URL changes : Google's own steps for a domain move
- Google Search Central: Change of Address tool : telling Search Console about the move
- WordPress.org: Changing the site URL : updating siteurl and home and the search-replace step
Links last checked October 17, 2026.
Frequently asked questions
Will I lose rankings when I change domains?
A properly executed move with page-to-page 301s usually keeps rankings after a short settling period. Losses come from blanket redirects to the homepage, redirect chains, or an old domain that goes dark before search engines have reprocessed the links.
Should the redirects be in WordPress or at the server?
Either works. A server or DNS-level forward is lighter if the old domain has no site any more. A WordPress rule on the old site is easy to manage and shows click counts. Avoid doing both, which creates chains.
How long should I keep the old domain?
At least a year, ideally indefinitely if it is cheap. Links from other sites will point at the old domain for years. The redirect is what carries their value to the new one.
Do I need to redirect www and non-www and http and https?
Yes, all four variants of the old domain should end at the one canonical version of the new domain, in a single hop each. Test each combination after the switch.