Domain Name Change SEO: Change Domains Without Losing Rankings

Changing your domain name without losing rankings comes down to four moves: 301-redirect every old URL to its exact new match, use Google's Change of Address tool, submit the new sitemap, and monitor reindexing for 4 to 8 weeks. Miss the redirects and you lose the traffic. Do them right and rankings transfer.

A domain change is riskier than a platform migration because the entire authority signal, every backlink and every ranking, is attached to a hostname you are retiring. Google needs a clear, permanent path from old to new. This guide covers the website migration service that keeps that path intact.

Why a domain change carries more risk than it looks

On the surface a domain change is a find-and-replace job. Under the surface it is a transfer of every trust signal you have earned. Backlinks point at the old hostname. Internal links point at the old hostname. Canonical tags, sitemap entries, and structured data all name the old hostname. Search engines have years of crawl history tied to it. When you retire that hostname, you are asking Google to move all of that to a name it has never ranked before.

Three failure points cause most of the damage. The first is an incomplete redirect map, where some old URLs have no new home. The second is redirect chains, where an old URL bounces through two or three stops before it lands. The third is mixed signals, where redirects point one way while canonical tags or internal links still point at the old domain. Each one dilutes the authority you are trying to move. Plan the change as a signal transfer, not a text swap, and the six steps below fall into place.

1. Map old URLs to new one for one

The core rule: every old URL maps to the same path on the new domain. Do not funnel everything to the homepage.

• Crawl the current site to capture every live URL.
• Export Search Console Pages data to see which URLs earn clicks and links.
• Build a spreadsheet with two columns: old URL, new URL.

A page-to-page map preserves the ranking of each individual page. Redirecting 400 pages to the homepage tells Google those 400 pages are gone, and their rankings go with them.

Cross-check two sources so no URL slips through. Your crawler finds pages linked internally. Search Console and your backlink tool find pages that earn traffic or links but may not be linked from the current menu. Old blog posts, landing pages from paused ad campaigns, and PDF assets often live outside the crawl but still pull traffic. Add every one to the map. A URL with even five backlinks is worth a redirect line.

2. Set up 301 redirects at the server

Use permanent 301 redirects, not 302 temporary ones or JavaScript redirects. A 301 passes ranking signal; a 302 tells Google the change is temporary.

• Configure redirects at the server or CDN level for speed and reliability.
• Redirect old-domain URLs to the identical path on the new domain.
• Avoid redirect chains: old URL to new URL in one hop, never through three stops.

Keep the old domain registered and the redirects live for at least 12 months. Backlinks and bookmarks keep sending traffic through the old domain long after launch. Full rules live in 301 redirect best practices.

Watch for the two chains that creep in without notice. The first is protocol: an old HTTP URL redirects to old HTTPS, which then redirects to the new domain, two hops where one would do. The second is trailing slashes, where one URL redirects to a slash version that then redirects again. Write each rule so the first request lands on the final HTTPS new-domain URL in a single 301.

3. Prepare the new domain before you flip

The new domain should be fully live and testable before you announce the change.

• Confirm the new site resolves on both www and non-www, pointing at one canonical version.
• Set canonical tags to the new domain across every page.
• Install an SSL certificate so the new domain serves over HTTPS from day one.

Test the redirects on staging by requesting old URLs and confirming they land on the right new pages with a 301 status. A redirect that returns 200 or 302 is a redirect that leaks ranking.

Run a full internal-link sweep before launch too. Any hardcoded link that still names the old domain forces an extra redirect hop on every click and wastes crawl budget. Update navigation, footers, in-content links, image sources, and canonical tags to the new hostname. The goal is a site where nothing internal points backward and every external pointer redirects forward in one step.

4. Use Google's Change of Address tool

Once redirects are live and both domains are verified in Search Console, tell Google directly.

• Verify both the old and new domain properties in Search Console.
• Confirm sitewide 301 redirects are in place before you start the tool.
• Run Change of Address on the old domain property and point it at the new one.

This tool speeds up the transfer of signals between the two domains. It works only for full domain moves, not partial ones, and it needs the redirects already firing.

Repeat the same signal at the platform level everywhere it exists. Update your Bing Webmaster Tools site move, point Google Business Profile at the new domain, and refresh the primary URL on major social profiles. These are not ranking factors on their own, but they cut the number of visitors who keep hitting the old domain and they feed a consistent picture of which hostname is now canonical.

5. Submit sitemaps and request indexing

Give Google the new map of the site.

• Submit the new domain's sitemap in its Search Console property.
• Use URL Inspection on your top 20 pages and request indexing.
• Leave the old sitemap accessible so Google can crawl the redirects.

Because DNS changes take time to spread, some visitors hit the old domain for a while. See how long does DNS propagation take for what to expect during the cutover window.

Keeping the old sitemap live is the step teams skip. Google needs to re-crawl each old URL to discover the 301, and a live old sitemap gives it the full list to work through. Pull that sitemap only after impressions on the old property have flattened near zero, which usually takes several weeks.

6. Monitor reindexing and fix gaps

The work is not done at launch. The first month tells you whether the transfer held.

• Watch the new domain's impressions climb as the old domain's fall.
• Track 404 errors daily and patch any URL that missed a redirect.
• Compare rankings for your top 20 keywords weekly against your pre-move baseline.

A domain move typically dips traffic 10 to 20 percent for 2 to 4 weeks, then recovers over 4 to 8 weeks. If recovery stalls past 8 weeks, audit for missed redirects, chains, or canonical tags still pointing at the old domain.

A worked domain-change timeline

A domain change has a natural order, and doing steps out of sequence is what causes ranking loss. Here is the sequence that holds.

When	Action
Week -1	Crawl the old site, export Search Console Pages, build the one-to-one URL map
Day -2	Stand up the new domain, confirm it resolves on www and non-www with SSL
Day -1	Lower DNS TTL, verify both domains in Search Console, test redirects on staging
Day 0	Point DNS, confirm sitewide 301s fire, submit the new sitemap
Day 0, +1 hour	Run Change of Address on the old domain property
Week 1	Request indexing on top 20 pages, track 404s daily
Weeks 2 to 8	Watch new-domain impressions rise, old-domain impressions fall, patch gaps

The order is the point. Running Change of Address before the redirects fire, or pointing DNS before the new site resolves cleanly, are the two mistakes that turn a routine move into a traffic drop.

Backlinks and how to protect them

Your backlinks point at the old domain, and every one of them is authority you cannot afford to strand.

• Keep the old domain registered and its redirects live for at least 12 months, ideally longer.
• Export your top linking pages from a backlink tool so you know which old URLs carry the most authority.
• Confirm those specific URLs redirect to their exact new match, not to the homepage.
• For your highest-value links, it is worth asking the referring site to update the URL directly.

A 301 passes most of the ranking signal from a backlink, but the redirect has to stay live to do it. Let the old domain expire and every backlink pointing to it becomes a dead link, which severs the authority the redirect was carrying. Renewing one domain for a few dollars a year protects link equity you spent years earning.

Keep the redirect map as a living reference

The spreadsheet that maps old URLs to new is not a launch-day artifact you throw away.

• Store it where the team can find it, because it answers 404 questions for years.
• Update it whenever you retire or move a page on the new domain.
• Use it to audit annually that the old-to-new redirects still return 301, not a broken chain.

Sites change after a move. A page you redirect today might itself move next year, which turns a clean one-hop redirect into a chain without warning. The map is how you catch that. Treat it as documentation, not a task you close, and the domain change keeps paying off long after the traffic recovers.

When a domain change is worth the risk

A domain change always carries a short-term traffic dip, so it should serve a real reason rather than a whim.

• A rebrand where the old name no longer fits the business is a sound reason.
• Merging two sites onto one stronger domain consolidates authority.
• Moving off a domain with a poor history or the wrong extension can help long term.
• A cosmetic preference for a slightly shorter name rarely justifies the reindexing cost.

If the reason is strong, the 4-to-8-week recovery is a fair price for a name that fits for years. If it is marginal, the safer move is often to keep the domain and improve the site on it. Weigh the lasting benefit against the temporary dip before you commit, because the redirect and monitoring work is the same whether the reason is big or small.

Related terms

You may see this topic described with related searches like change domain name, change domain name wordpress, change website domain name, change wordpress domain, and changing domain name. Those phrases are useful when they clarify what the reader needs next, but they should still point back to one clear plan.

Related searches such as does changing domain name affect seo, how to change domain name, how to change domain name in wordpress, move wordpress site to new domain, and wordpress change domain name are useful when they clarify what the reader needs next. They should support the same plan rather than pulling the page in several directions at once.

You may see this topic described with related searches like how to change your domain name. Those phrases are useful when they clarify what the reader needs next, but they should still point back to one clear plan.

Frequently asked questions

How much traffic will I lose changing domains?

Expect a temporary dip of 10 to 20 percent for 2 to 4 weeks, with recovery over 4 to 8 weeks. A clean one-to-one redirect map keeps the loss temporary. Missing redirects turn a dip into a permanent drop.

Do I need to keep the old domain after moving?

Yes. Keep the old domain registered with redirects live for at least 12 months, ideally longer. Backlinks and direct traffic keep flowing through the old domain, and letting it expire severs every one of those links.

Will Google penalize me for changing my domain?

No. A domain change is a normal, supported move. Google provides the Change of Address tool specifically for it. Rankings drop only when the technical transfer is incomplete, not because the change itself is penalized.

How long before rankings recover after a domain change?

Most sites recover within 4 to 8 weeks. Larger sites with more pages take longer to fully reindex. Track weekly against a pre-move baseline so you can tell normal reindexing noise from a real redirect problem.

Should I change my domain and redesign the site at the same time?

No. Change one variable at a time. If you move the domain and rework URLs, content, and templates together, you cannot tell which change caused a ranking drop. Move the domain first with pages unchanged, confirm the transfer held over 4 to 8 weeks, then redesign.

Does a domain change affect my email?

Yes, if your email runs on the same domain. Mailboxes, MX records, and sending reputation all live with the hostname, so plan the mailbox move alongside the site move. Handle it as a separate workstream with its own testing rather than assuming the web redirects cover it.

Does GoDaddy allow domain transfer?

Usually, yes, if the work supports a real business goal and someone checks the result after it goes live. If it does not help people find, trust, or convert through the site, it is probably not worth doing.

How long does a GoDaddy domain transfer take?

Transfer a domain by unlocking it, confirming admin email access, requesting the authorization code, starting the transfer with the new registrar, and checking DNS records before and after the move so the website and email keep working.

Is there a domain transfer fee?

Domain transfer fees are usually modest, but the real cost is the risk of downtime or broken redirects if DNS, email, analytics, and search settings are not checked. Budget for the transfer and for the technical review around it.

How much is the domain transfer fee?

Domain transfer fees are usually modest, but the real cost is the risk of downtime or broken redirects if DNS, email, analytics, and search settings are not checked. Budget for the transfer and for the technical review around it.

How much does GoDaddy charge for domain transfer?

Domain transfer fees are usually modest, but the real cost is the risk of downtime or broken redirects if DNS, email, analytics, and search settings are not checked. Budget for the transfer and for the technical review around it.

Get help with your domain change

A domain change puts your entire ranking history on one redirect map, so precision matters. Start with the website migration service. To plan the cutover timing, read how long does DNS propagation take, and to get the redirects right, see 301 redirect best practices.

Share this guide