BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
TLD Migration Decisions: When to Move Your Domain to a New Extension, and How to Do It Without Losing SEO
A TLD migration is the decision to move a live site from one top-level domain to another, for example from a .net to a .com, from a country-code extension to a global one, or off an extension that no longer fits the brand. It is two questions stacked together: whether the move is worth the disruption, and how to execute it without bleeding the rankings the old domain already holds.
The honest position is this. Done well, with a full redirect map, the old domain kept live, and the right replacement signals in place, a TLD migration transfers the equity and the temporary dip recovers. Done badly, with wildcard redirects, a dropped old domain, or a geo-signal silently lost, it sheds traffic that does not come back. This guide teaches both reads and does not tell you which way to jump.
It also fills the gap every migration guide leaves open. The TLD string itself is rarely the SEO problem. The decision of which extension to land on, and the domain you migrate onto, is what carries or poisons the move. SEO Domains operates the curated marketplace where aged and expired domains on the extension you want are screened before they are priced, so a brand changing TLD can land on a clean name instead of an unvetted one.
What a TLD migration decision actually is
A TLD migration decision is the choice to move a live website from its current top-level domain to a different extension, then to execute that move without losing the ranking equity the old domain holds. The TLD is the part after the final dot, such as .com, .net, .org, or a country code like .de. Migrating it changes the address every search engine has indexed, which is why the decision is half strategy and half technical execution.
The four situations that trigger the question
The decision rarely starts from a blank page. It starts from a pressure that makes the current extension feel wrong. Four situations account for the bulk of real migrations:
- The .com became available. A brand on a .net or .co finally secures the matching .com and wants the trust and recall that the .com carries.
- A rebrand forces it. A company name change leaves the old domain stranded, and a new extension comes bundled with the new name.
- Going global, or going local. A site outgrows a country-code extension and wants international reach, or the reverse, a global brand wants a country-code domain to anchor a single market.
- Escaping a tainted or limiting extension. An extension carries spam association, registry restrictions, or a price hike the brand wants to leave behind.
Each situation has a different risk profile, which is the reason a single yes-or-no answer fails. The geo cases in particular carry a consequence the others do not, covered in its own section below.
What a TLD migration is not
Changing only the path of a URL, switching from HTTP to HTTPS, or moving from a subdomain to a subfolder are migrations too, but they are not TLD migrations. A TLD migration specifically swaps the extension, which means the whole host changes and Google treats the new address as a separate site that has to inherit the old one’s signals through redirects.
It is also distinct from buying a defensive domain you never point anywhere. Registering the .org of your .com to keep it off the market is asset protection. A migration is the live move of the running site onto the new name.
Does changing your TLD hurt SEO? The honest answer
For a generic TLD, the extension string itself carries no direct ranking weight, so changing it does not penalize a site for the dot alone. The risk lives in the migration, not the TLD. A clean page-by-page move with permanent redirects transfers the equity; a careless one loses it. The honest read is that the move is neutral by design and dangerous by execution.
Google treats generic extensions the same
Google’s documentation on managing multi-regional sites is explicit that generic top-level domains such as .com, .org, and .edu do not tie a site to a country, and there is no published evidence that one generic extension ranks better than another for the string alone. The .com advantage that brands chase is real, but it is a trust and click-through effect with users, not a ranking multiplier inside the algorithm.
That distinction matters for the decision. If a brand expects a .com to lift rankings on its own, the migration will disappoint. If it wants the recall and trust a .com signals to humans, that benefit is documented and durable.
Where the equity actually goes
The authority a site holds lives in its backlinks, its history, and the signals Google has attached to its URLs. A migration succeeds when every one of those URLs forwards to its exact counterpart on the new extension with a permanent redirect, so the inherited authority flows to the new address. It fails when the mapping is incomplete, when redirects chain or break, or when the old domain is dropped before the signals transfer.
This is why two migrations off the same .net to the same .com can end in opposite places. One brand maps every page and keeps the old domain live for years; the other points the homepage at the homepage and lets the rest 404. The extension was identical. The execution was not.
What carries the move (done well)
A complete page-by-page 301 map, the old domain kept live and renewed, internal links rewritten to the new host, a fresh sitemap submitted, and the Change of Address tool filed. The equity transfers and the dip recovers.
What sinks the move (done badly)
Wildcard redirects to the homepage, redirect chains, a dropped old domain, lost internal links, a missing sitemap, and a geo-signal silently abandoned. The equity leaks and the dip becomes permanent.
When a TLD migration is worth it, and when to stay put
A TLD migration is worth the disruption when a forcing event, a rebrand, a reclaimed .com, a reach change, or escape from a tainted extension, delivers a durable gain that outlasts the recovery window. It is not worth it when the motive is a vanity upgrade with no functional payoff, because the guaranteed traffic dip buys nothing. The deciding test is whether the upside survives 6 to 12 months of recovery.
A scored decision framework
The bulk of guides describe how to migrate and skip the prior question of whether to. The framework below scores the trigger against the cost, so the decision rests on the payoff and not the impulse. Read each row as a situation, the strength of its case, and the verdict it points to.
| Trigger situation | Strength of the case | Verdict |
|---|---|---|
| Forced rebrand or company name change | High. The old domain no longer matches the brand, so the migration is unavoidable rather than optional | Migrate, and execute carefully |
| Reclaimed the matching .com | Medium to high. Real trust and click-through gain with users, durable beyond the recovery window | Migrate if the brand is long-term |
| Going global from a country-code extension | Medium. Frees the brand from one-country targeting, but the auto geo-signal has to be rebuilt | Migrate with hreflang planned in |
| Escaping a spam-tainted or restricted extension | Medium to high. Removes a real liability, provided the new name is clean | Migrate onto a vetted domain |
| Vanity upgrade with no functional gain | Low. The dip is guaranteed; the payoff is cosmetic | Stay put, or wait |
| Chasing a ranking boost from the extension alone | None. Generic TLDs do not rank differently for the string | Stay put |
The case for staying put
Inertia is an underrated strategy. A site that already ranks on a .net or a .co with a clean profile and earned links carries an asset that a migration puts at risk for a benefit that is sometimes cosmetic. When the trigger is taste and not a forcing event, the disciplined answer is usually to keep the equity where it sits and register the better extension defensively without pointing the live site at it yet.
The bundling trap
A frequent error at the decision stage is to bundle the TLD change with a platform move, a redesign, and a content overhaul in one launch. Joost de Valk names this directly, warning against bundling a redesign, a platform move, and a content overhaul into one launch without confidence in execution. When traffic drops after a bundled launch, the cause is impossible to isolate, and the fix becomes guesswork. The disciplined decision migrates the TLD as a clean, single variable.
The ccTLD geo-targeting consequence most guides skip
Moving between a country-code TLD and a generic one changes the geo-targeting signal Google reads, and the migration field routinely ignores it. A country-code extension automatically tells Google the site targets that country. A generic extension does not, so a move off a country-code domain loses that signal and it has to be rebuilt with hreflang and locale URLs. Skip this and a global migration can quietly tank one market.
What a country-code extension signals automatically
Google’s multi-regional documentation states that country-code top-level domains provide a strong signal to both users and search engines that a site is explicitly intended for a certain country. A .de domain reads as German, a .fr as French, with no extra configuration. That automatic targeting is an asset for a single-market brand and a constraint for one that wants global reach.
Generic extensions carry no such signal. A .com targets nowhere by default, which is why a global brand prefers one, and why a brand serving a single country leans toward the country code.
The three migration directions and their geo-consequence
The geo-effect depends entirely on the direction of the move. The table below states what each direction does to the country signal and the work it forces.
| Migration direction | What happens to the geo-signal | The work it forces |
|---|---|---|
| Country-code to generic (.de to .com) | The automatic country signal is lost | Rebuild targeting with hreflang and locale URLs before launch |
| Generic to country-code (.com to .de) | The site narrows to one country target | Confirm the brand truly serves only that market |
| Generic to generic (.net to .com) | No change; both are geo-neutral | Standard migration, no geo step required |
| Country-code to country-code (.co.uk to .de) | The target country changes outright | Expect a market shift, not a like-for-like move |
The fake country-code trap
A set of extensions look like country codes but are treated as generic by Google. The documentation lists .io, .co, .me, and .tv among the codes that users and Google read as generic instead of country-targeted, because the marketing market repurposed them. A brand migrating to a .io for a tech feel gains no country targeting from it, and a brand leaving one loses none. Treating these as country codes in a migration plan is a planning error that the gTLD-vs-ccTLD distinction makes clear; the full split is mapped in gTLD vs ccTLD: How the two domain extension families differ on eligibility, geo-targeting, and aftermarket value.
What it costs: the traffic dip, the recovery window, the odds
A TLD migration carries a predictable temporary cost and a real failure rate. Joost de Valk budgets a 30 to 40 percent traffic loss for 3 to 6 months and 6 to 12 months for full recovery in search. Elcom reports that 301 redirects preserve 90 to 99 percent of link equity, yet cites research that 42 percent of domain migrations do not fully recover. The dip is normal; a permanent loss signals a flawed move.
The expected dip and recovery curve
The temporary drop is the cost of admission. Joost de Valk, the founder of Yoast, frames a workable expectation as a 30 to 40 percent traffic loss for three to six months, after which a well-executed site returns to baseline. He budgets one to three months to plan, then six to twelve months for the migration to come through in search. Elcom’s timeline aligns, with first visible recovery 2 to 4 weeks after launch, partial recovery in 1 to 3 months, and full recovery in 3 to 6 months for a clean move, stretching toward 12 for large sites.
Google’s own guidance sets the same expectation in calmer language, noting that a small to medium-sized site can take weeks for the bulk of its pages to move, that larger sites take longer, and that visibility can fluctuate temporarily during the move. A dip is the documented norm, not a sign of failure.
The failure rate, and what separates the two outcomes
The downside is documented in named cases. Joost de Valk contrasts The Guardian, which recovered within months of its migration, with Topshop, which never recovered from an 80 percent visibility drop. Elcom cites research that 42 percent of domain migrations do not fully recover their original traffic. The split between the two camps is not luck. It is whether the preparation, the redirect mapping, the retained old domain, and the rebuilt signals, was done before launch.
| Cost dimension | Cited figure | Source |
|---|---|---|
| Expected traffic dip | 30 to 40 percent for 3 to 6 months | Joost de Valk (Yoast founder) |
| Full search recovery window | 6 to 12 months | Joost de Valk |
| Link equity preserved by 301 | 90 to 99 percent | Elcom |
| First visible recovery | 2 to 4 weeks after launch | Elcom |
| Migrations that never fully recover | 42 percent | Elcom (cited research) |
| Worst-case documented loss | 80 percent visibility, no recovery (Topshop) | Joost de Valk |
How to migrate a TLD without losing equity, step by step
A TLD migration runs in seven stages: confirm the new domain, map every URL one to one, set permanent 301 redirects, rewrite internal links and submit a new sitemap, file the Change of Address tool, rebuild any lost geo-signal, then keep the old domain live and monitor. Each stage pairs the done-right move with the specific mistake that loses equity. This is the execution sequence the decision unlocks.
The process below combines Google’s own site-move guidance with the operational detail from Joost de Valk and the migration field. Every stage states the disciplined move and the footprint that turns a recoverable dip into a permanent loss.
-
Confirm and prepare the new domain
Secure the target extension, verify the brand owns it outright, and stage the new site fully before any redirect goes live. The done-right move is to land on a clean name with no toxic history, screened before purchase. Read the diligence that separates a clean aged name from a junk one in TLDs and aged-domain value: Which extensions retain SEO equity, then browse screened inventory on the SEO Domains marketplace.
The mistake: migrating onto an unvetted or previously spammed domain on the new extension. A toxic inherited profile poisons the move before a single redirect fires.
-
Map every URL one to one
Build a spreadsheet matching each old URL to its exact counterpart on the new domain, page by page. The done-right move is a complete map crawled from the old site and tested in staging.
The mistake: a wildcard redirect that points every old URL at the new homepage. It throws away the page-level equity Google attached to deep pages, and it is the leading cause of a migration that never recovers.
-
Set permanent 301 redirects
Configure server-side permanent redirects from every old URL to its mapped new one. Google recommends a permanent redirect such as 301 or 308 and confirms it does not cause a loss in PageRank. The done-right move is a server-side 301, always, with no client-side fallback.
The mistake: a 302 temporary redirect, a JavaScript or meta-refresh redirect, or a chain of hops. Each one slows the signal transfer or fails to pass it, and redirect chains dilute the equity at every hop.
-
Rewrite internal links and submit a new sitemap
Update every internal link, menu, footer, and canonical tag to point at the new host directly, then generate a fresh sitemap of the new URLs and submit it in Search Console. The done-right move is direct internal links with no internal redirect hops.
The mistake: leaving internal links pointing at old URLs so every internal click bounces through a redirect, and forgetting the new sitemap so Google discovers the new pages slowly.
-
File the Change of Address tool
Verify both the old and new domains in Search Console, including www, non-www, and subdomain variants, then submit the Change of Address tool for the old site. The done-right move is to file it once the redirects are live and verified.
The mistake: skipping the tool or filing it before the redirects work. Google needs the explicit signal and a working redirect to process the move at full speed.
-
Rebuild any lost geo-signal
If the move left a country-code extension for a generic one, replace the automatic country signal with hreflang annotations and locale URLs, the method Google recommends for targeting a generic TLD to a country. The done-right move is to have hreflang live at launch, not added weeks later.
The mistake: abandoning a country-code domain for a .com and leaving no geo-targeting behind. The home market reads as untargeted and rankings there slip with no obvious cause.
-
Keep the old domain live and monitor
Renew the old domain and keep its redirects active for as long as possible. Google advises keeping redirects generally at least one year, and Joost de Valk keeps the old domain indefinitely, calling the cost a rounding error against the risk. The done-right move is to monitor traffic and crawl errors daily for the first two weeks, then weekly for months.
The mistake: dropping or letting the old domain expire too soon. The moment the redirects die, every signal still in transit is lost, and any inbound link to the old URL goes dark.
Common TLD migration mistakes: the consolidated checklist
The mistakes that turn a recoverable dip into a permanent loss are a short, repeatable list. Each one is a footprint of a rushed move, and each has a documented fix that points back to the same discipline: map every page, redirect permanently, keep the old domain, and replace any signal the move removes. Use this table as the scannable reference before, during, and after launch.
The table consolidates the footprints scattered through the steps and cost sections into one place. The left column is the mistake, the centre is why it costs equity, and the right is the done-right fix. Read top to bottom, the fixes describe a migration that carries its authority intact.
| The mistake | Why it costs equity | The fix (done-right move) |
|---|---|---|
| Wildcard redirect to the homepage | Page-level equity on deep pages is discarded, not transferred | A complete page-by-page 301 map of every old URL |
| 302, JavaScript, or meta-refresh redirects | A temporary or client-side redirect transfers signals slowly or not at all | Server-side permanent 301 redirects, always |
| Redirect chains | Each hop slows crawling and dilutes the equity passed | A single direct redirect from old URL to final new URL |
| Dropping the old domain too soon | Every signal still in transit and every inbound link is lost | Keep the old domain live at least one year, ideally indefinitely |
| Internal links left on old URLs | Every internal click bounces through a redirect, wasting crawl budget | Rewrite all internal links to the new host directly |
| No new sitemap or Change of Address filed | Google discovers and trusts the new URLs slowly | Submit a fresh sitemap and file the Change of Address tool |
| Country-code geo-signal abandoned | A generic TLD reads as untargeted, so the home market slips | Rebuild targeting with hreflang and locale URLs at launch |
| Bundling redesign and platform change in one launch | A traffic drop cannot be isolated to a cause | Migrate the TLD as a single, clean variable |
| Migrating onto an unvetted or spammed name | A toxic inherited profile poisons the move from day one | Start from a clean, screened aged domain on the new extension |
One pattern runs down the fix column. The recurring move is to treat the migration as a complete signal transfer onto a clean target, not a homepage swap. The first row and the last row are the bookends: discard the deep-page map and you lose equity at the front of the move; land on a junk domain and you lose it at the back. The clean target name is the foundation the next section returns to.
TLD migration decisions: frequently asked questions
The questions brands and SEOs raise when they weigh a TLD migration, answered against Google’s site-move guidance and the cited recovery figures this guide assembles.
Q1Does changing your TLD hurt SEO?
Not the extension itself. Google treats generic TLDs such as .com, .net, and .org the same for ranking, so the string carries no penalty. The risk lives entirely in the migration. A clean page-by-page move with permanent 301 redirects and the old domain kept live transfers the equity and the temporary dip recovers. A careless move loses it.
The .com advantage brands chase is a trust and click-through effect with users, not a ranking multiplier inside the algorithm.
Q2How long does it take to recover from a TLD migration?
Joost de Valk budgets 6 to 12 months for a domain migration to come through in search, with a 30 to 40 percent traffic dip for the first 3 to 6 months. Elcom reports first visible recovery 2 to 4 weeks after launch and full recovery in 3 to 6 months for a clean move. Google notes a small to medium site can take weeks for the bulk of its pages to move, and larger sites longer.
Q3What is a TLD swap, and is it the same as a migration?
A TLD swap is the informal name for moving a live site from one extension to another, for example from a .net to a .com. It is the same event as a TLD migration. The word swap understates the work, because the move is not a simple rename. Every indexed URL has to forward to its new counterpart for the inherited authority to transfer.
Q4Do I lose my country ranking if I move from a ccTLD to a .com?
You lose the automatic country signal, and unless it is replaced, the home market can slip. Google states a country-code extension signals a specific country by default, while a generic one targets nowhere. Moving from a .de to a .com removes that flag, so the targeting has to be rebuilt with hreflang annotations and locale URLs, ideally live at launch instead of added weeks later.
Q5How long do I keep the old domain after migrating?
Google advises keeping the redirects for as long as possible, generally at least one year, so all signals transfer. Joost de Valk goes further and keeps the old domain indefinitely, calling the renewal cost a rounding error against the risk of losing inbound links. The practical answer is to renew the old domain and hold its redirects live for years, not months.
The variable that decides the outcome: the domain you migrate to
The execution carries the migration, but the domain you land on decides whether it can succeed at all. A clean aged domain on the target extension inherits real, earned authority and carries the move. A spam-flagged or unvetted name inherits a liability the redirects cannot fix. Sourcing the new name from a screened catalogue separates a safe migration from a poisoned one. SEO Domains operates that curated marketplace.
Why the target name is the deciding variable
A migration transfers signals from the old domain to the new one. If the new domain already carries a toxic inherited profile, that liability sits underneath everything the redirects bring across, and no redirect discipline removes it. The brand inherits both its own equity and the new name’s baggage. This is why the choice of which name to land on is the first decision, not an afterthought.
The clean name versus the poisoned one
When the migration target is a fresh registration of an unused name, the only question is brand fit. When the target is an aged domain on the wanted extension, chosen for the equity it already holds, the question becomes whether that equity is real and clean. A vetted aged domain enters the move as an asset. An unvetted one risks entering as a penalty that the migration then amplifies.
How to source a clean name on the new extension
A domain that holds up survives a profile check before money changes hands. The signals that matter are the same ones the authority-metrics work documents, applied to the specific extension the migration targets:
- A clean backlink profile with editorially earned links, read for quality instead of raw count.
- A real prior-use history on the extension, with no spam or unrelated abuse in the record.
- Authority metrics cross-validated across sources, not read from one inflated score.
- A registration history checked through ICANN records and the RDAP lookup that replaced public WHOIS.
An aged domain that passes these on the wanted extension is a migration target that strengthens the move. One that fails them is a liability the redirects will faithfully carry your equity onto.
| Check on the target name | Unvetted name (liability) | Screened name (asset) |
|---|---|---|
| Backlink profile | Toxic or spam-inflated | Clean, editorially earned |
| Prior use on the extension | Spam or unrelated abuse | Real history, topical continuity |
| Authority metrics | Single inflated score | Cross-validated across sources |
| Registration record | Unchecked | Read through ICANN and RDAP before listing |
| Effect on the migration | A penalty the redirects amplify | Earned authority the move carries |
Browse screened aged and expired domains on the extension you want
The legitimate need behind a TLD migration decision is a clean name on the right extension that the brand can own openly and migrate onto with confidence. That is the product, not a migration service and not hosting. SEO Domains operates the curated marketplace where aged and expired domains are screened across their backlink profiles, history, and authority metrics, on the extension a migrating brand wants, before they are listed and priced.
