Short answer: change your domain when the current name actively costs you more than the migration will. Execute with permanent 301 redirects from every old URL to its exact new equivalent, keep both domains registered indefinitely, and expect a temporary ranking dip of several weeks before recovery.
Four signals it is time to change
- You have outgrown the name. The name describes a product line, a region, or a business model you no longer are. Every conversation now begins with an explanation.
- The name leaks traffic. You are on a compromise extension or a hyphenated variant, and the .com owner is capturing people looking for you.
- There is a legal problem. A trademark conflict has surfaced. This one is not optional and the timeline is not yours to choose.
- Nobody can spell it. Support tickets, referral leakage, and repeated corrections in meetings all point the same direction.
Note what is not on that list: simply disliking the name. Founder fatigue with a name is extremely common and rarely a sufficient reason on its own. Your customers have far less exposure to it than you do.
The migration checklist
| Stage | Action |
|---|---|
| Before | Crawl and export every existing URL |
| Before | Map each old URL to its exact new equivalent |
| Before | Secure the new domain and set up hosting |
| Launch | Deploy permanent 301 redirects, one to one |
| Launch | Update internal links to point at new URLs directly |
| Launch | Submit the change in search console tools |
| Launch | Update sitemap and resubmit |
| After | Update backlinks you control, and request updates on high-value ones |
| After | Update social profiles, email signatures, ad accounts, packaging |
| Ongoing | Monitor crawl errors and redirect chains weekly |
The one-to-one rule
The single most damaging migration mistake is redirecting everything to the new homepage. It is quick, it feels tidy, and it destroys the accumulated value of every individual page.
Each old URL must redirect to the page that serves the same purpose on the new domain. A blog post redirects to that blog post. A product page redirects to that product. Where no equivalent exists, the closest relevant page is far better than the homepage. Bulk redirects to root are treated as a signal that the old content is gone, and the equity goes with it.
Realistic recovery timeline
- Weeks one to two: visible ranking fluctuation as crawlers process the change
- Weeks two to six: gradual recovery as the new URLs are indexed and equity transfers
- Months two to three: most sites approach previous levels
- Beyond: full recovery, sometimes exceeding the old baseline if the new name performs better
Plan for the dip rather than being surprised by it. Do not schedule a migration immediately before your peak trading season, and do not panic and reverse course in week two — reversing mid-migration compounds the damage substantially.
Should you run both domains in parallel?
Not as live sites. Two domains serving the same content creates duplication problems and splits your equity exactly when you are trying to consolidate it.
What you should do is keep the old domain registered indefinitely, with redirects in place permanently. Old links, printed materials, and bookmarks persist for years. Letting the old domain lapse means every one of those becomes a dead end — or worse, gets picked up by someone else.
The cost of waiting
Migration cost scales with everything you have built: more pages, more backlinks, more printed material, more customers who know the old name. A rebrand at fifty customers is straightforward. The same rebrand at fifty thousand is a project.
If the four signals above apply, the cheapest moment to act is now. Every month of delay adds to the eventual bill.
At a glance
- Change when the name costs more than the migration, not when you tire of it
- Redirect one to one — never bulk-redirect to the homepage
- Expect a several-week dip; plan around peak season
- Keep the old domain registered permanently
- Migration cost grows every month you delay
Frequently asked questions
Will I lose all my rankings?
No, if the migration is executed properly. Permanent redirects pass the large majority of equity. Losses come from poor mapping, not from moving itself.
How long should redirects stay in place?
Indefinitely. There is no point at which removing them becomes beneficial.
Should I announce the change?
Yes. Tell customers directly and update every owned channel. Surprise domain changes generate support tickets and erode trust.
Choose a name you will not outgrow
If you are rebranding, the priority is a name broad enough that you never do this again — short, distinctive, and not locked to any single product line.
