Website & Development
Change Your Domain Name Without Downtime or SEO Loss
Copy for AI
You can move a domain or hosting without downtime if you plan the DNS switch.
Downtime rarely comes from the transfer itself. It almost always comes from DNS caching: visitors and mail servers remember your old address for a while.
The verdict: lower your TTL early, build and test the new environment, and only then switch the records. Monitor from the very first minute.
This is part of the broader website migration without losing rankings. That piece is about your Google positions; this one is about staying online and reachable during the cutover.
For the full approach to a B2B site, read the pillar on building a B2B website.
What are you actually moving: domain, hosting or DNS?
Three different things, and half of the confusion starts here.
Transferring a domain, moving hosting and repointing your DNS are separate operations. Often you do just one, sometimes all three at once.
Three operations, three risk profiles
Here’s what each one means:
- Domain transfer: the name itself (yourcompany.be) moves to another registrar
- Hosting move: files and database go to a new server, same domain
- DNS switch: you repoint the records that say which address belongs to your domain
Running WordPress? Then a hosting move also means moving files and the database. That playbook is in migrating WordPress to new hosting or a new domain.
The DNS switch is the sensitive step
That’s where downtime or email outage actually happens.
The good news: a pure registrar transfer doesn’t need record changes if the new provider takes over the same DNS zone. The site simply stays reachable.
The risk rises as soon as you also switch servers or move your nameservers.
Why does downtime happen during a transfer?
Because of DNS caching, not the transfer itself.
DNS records have a TTL (time to live): the number of seconds servers may remember your address before checking again.
Say the TTL is 24 hours. Visitors can then keep landing on your old server for up to a day, even though your site moved long ago.
The “split brain” period
That causes two problems at once.
Some visitors land on the old server, possibly already switched off.
Others reach the new one.
That period can last from hours to about two days. So propagation is the key concept: the time it takes for the whole world to see your new records.
Lower the TTL 24 to 48 hours ahead
The fix is timing. Lower the TTL of the relevant records to around 300 seconds (five minutes).
Do it at least 24 to 48 hours before the cutover. Why so early?
A server that cached your old record just before the change still keeps the old, long TTL. Only once that window has passed does everyone see the short one.
Here’s what that does to your rollback window:
After a successful transfer, raise the TTL again, for example to an hour.
How do you prevent email outage during the transfer?
Protect your mail records, because they don’t move along with your website automatically.
People think “the site is moving”. Yet the same domain often carries your business email too.
Rebuild the DNS zone and forget the mail records, and your email goes down. The website won’t show a thing.
Map the mail records first
List your complete mail configuration before the transfer. At least these four:
- MX records: which server receives incoming mail; wrong or empty means no email
- SPF: which servers may send for your domain; forget it and mail lands in spam
- DKIM: the cryptographic signature on your outgoing mail
- DMARC: the policy that enforces and reports on SPF and DKIM
The golden rule
Only changing your web hosting? Then don’t touch your MX and mail records.
Too many transfers go wrong because someone copies the whole zone over “clean”. The mail records get wiped out.
How do you transfer a .be domain to another registrar?
With a transfer code from DNS Belgium. If everything’s correct, it can be done within a few hours.
According to DNS Belgium, the code is five groups of three digits, separated by hyphens.
It goes to the email address of the domain holder as it appears in the registry.
Three checks before you request the code
These decide whether the transfer goes smoothly:
- Holder email: make sure it’s correct in the registry, because that’s where the code lands.
- Timing: the code is valid for a limited time (in the order of a week), so request it only when you’re ready.
- DNS zone: a registrar transfer needn’t take your site or email offline, as long as the zone moves with the same records.
An old or wrong address at step 1 stalls the whole transfer.
Other extensions such as .com or .nl
They work comparably, with their own authorization or EPP code and their own lead times.
The principle stays the same. Sort out the DNS side and the name transfer is usually the smallest risk.
What is the safe step-by-step plan for the cutover?
Build and test the new environment fully before you switch a single record.
That way the cutover is flipping a switch, not a leap into the unknown. The four moments that matter:
The six steps in order
Work through them like this:
- Take inventory. Record A/AAAA, CNAME, MX, SPF, DKIM, DMARC and any CAA records.
- Lower the TTL. Set it to around five minutes, 24 to 48 hours ahead.
- Prepare the new environment. Site, database and a valid SSL certificate, tested via a temporary hosts entry.
- Schedule the cutover. Pick a quiet moment for your B2B audience, then change the records.
- Monitor and recover. Check propagation, forms, email, 404s and SSL right after the switch.
- Raise the TTL again once everything’s stable, and keep the old environment as a safety net.
Your inventory from step 1 is both your reference and your rollback plan.
Don’t skip steps 5 and 6
They’re the ones teams drop. Yet monitoring and a rollback plan make the difference between a quiet transfer and a panicky evening.
If something’s off, the low TTL lets you roll back within minutes.
A technically perfect transfer won’t generate leads. But email outage or a day of downtime costs you trust and revenue directly.
So plan it as a real project.
How do you change your domain name without losing SEO?
Treat it as a full site move, because that’s how Google sees it.
A registrar or hosting move leaves your URLs untouched, so Google barely notices.
Change the domain name itself, for example from yourcompany.be to newbrandname.be after a rebrand or merger, and every URL gets a new address. All signals have to move along.
What changes for Google
The risk depends on what you change:
| What are you changing? | Do your URLs change? | Risk to your Google positions |
|---|---|---|
| Registrar (domain transfer) | No | Small, as long as the DNS zone is correct |
| Hosting or server | No | Small, provided the site stays fast and reachable |
| Domain name | Yes, all of them | High without a redirect plan, manageable with one |
Google describes the playbook in its guide to site moves with URL changes.
The five steps for a new domain name
These make the difference:
- Change one thing at a time. Google advises against a new domain, CMS and design all at once.
- Build a redirect plan. Every old URL gets a 301 to the same page on the new domain, not the homepage.
- Verify both domains in Search Console and use the Change of Address tool after going live.
- Update everything that points to the old domain: canonicals, hreflang, internal links, sitemap and profiles.
- Keep the redirects for at least a year and keep the old domain registered.
Move to the new domain first, then adjust the layout. If traffic drops, you’ll know where it came from.
How to build the redirect list is explained in our 301 redirect plan.
The Change of Address tool
According to its help page, Google then prioritises crawling and indexing the new site. It forwards signals for 180 days.
Submit the change for every verified variant of your old domain: with and without www, and subdomains.
Ask for your best backlinks to be updated
Also update your Google Business Profile and your own profiles on other sites.
Then ask partners with important backlinks to update their link. Search Console shows who links to you most:
The Links report in our own Search Console for customerimpact.be, October 2026. Top linking sites is your list of partners to contact.
Those are the sites whose links you’d most like to point at the new domain directly.
Keep the old domain registered
Google recommends keeping redirects for as long as possible, so links on other sites keep passing value.
Watch out: let the old domain lapse and someone else can register it.
Check the result after the switch
Every old URL should end up on the right new page with a single 301.
Our free redirect checker tests a list of old URLs in one go, for status code and final destination.
Then watch clicks in the Performance report over the following weeks:
Our own Search Console for customerimpact.be, last 28 days, October 2026. After a domain change, compare clicks on the new property with the old one.
A dip of a few weeks is normal. A dip that keeps going points to broken redirects.
Rather not handle the domain change alone? Our SEO migration service guides the redirect plan, the Search Console steps and the follow-up.
The short summary
A transfer without downtime isn’t luck. It’s sequence.
Lower your TTL in time and test the new environment. Protect MX, SPF, DKIM and DMARC, then switch with a rollback of minutes ready.
Is the transfer tied to a new or revamped website? We plan the migration so your site stays online and your email keeps running.
Frequently asked questions about changing your domain name
Will I lose my Google rankings if I change my domain name?
Not permanently, if you redirect every old URL with a 301 to the same page on the new domain and use the Change of Address tool in Search Console. Do expect a few weeks of fluctuation while Google processes the new URLs.
How long should I keep my old domain?
Keep the redirects active for at least a year and preferably keep the old domain name registered for as long as links still point to it. That way, visitors arriving via old links, bookmarks and emails still end up in the right place.
Do I need the Change of Address tool when switching to https?
No. According to Google, you only use the tool when changing domain or subdomain, not when moving from http to https, switching between www and non-www, or moving within the same domain.
Does a registrar transfer affect my SEO?
No, as long as your DNS records stay identical and the site stays reachable. Your URLs do not change, so Google does not notice the transfer.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.