What actually happens on the day your new website goes live

Nobody explains what actually happens, so here's the sequence

A lot of people never ask. They nod along when someone says "we'll flip the switch Thursday" and hope the phrase means something specific. It does. Launch day, also called cutover day, is a short, concrete sequence of steps. It is not one dramatic moment.

Once you see the sequence written out plainly, most of the fear drains out of it. Here it is, start to finish, without the jargon attached.

First, the new site gets one final check on staging, the private copy nobody outside the project has seen yet. Then someone updates the DNS records that tell the internet where your domain points. After that comes a waiting period while different networks catch up to the change. Finally, someone checks the live site and confirms visitors are landing on the new one, not the old one.

That's the whole shape. Everything below is detail sitting inside those four steps. None of it requires you to understand networking. It just helps to know what's supposed to happen, so you can tell the difference between normal and not, calmly, in the moment.

The DNS switch, in plain terms

Your domain name is a label pointing at an address. The DNS switch changes what address that label points to: from the server hosting your old site, to the one hosting your new one. It's a small, specific edit: a couple of records in a settings panel, changed in one sitting.

The edit itself takes seconds. What takes longer is every computer, phone, and network on the internet noticing the change and updating its own memory of where your domain points.

That waiting part is the piece people mistake for something going wrong. It isn't. It's just the internet's own memory catching up at its own pace, in the background, without anyone needing to intervene.

Why some visitors keep seeing your old website right after launch walks through why your laptop and your phone can briefly disagree about which version they're loading during this stretch.

Two sites, briefly, and why that's fine

During that catch-up window, some visitors reach the new site and some still reach the old one. It depends on which cached version their particular device or network happens to be holding onto at that moment. That's not a bug. Both sites stay technically live and reachable during this stretch.

That overlap is genuinely useful, not just tolerable. It means there's no gap where nothing loads for anybody at all. Someone is always looking at a working site, even if it isn't consistently the same one for a few hours after the switch.

Why your old website should stay live until the new one is ready covers the decision to keep both running instead of shutting the old one down early, and why that call gets made well before launch day itself even arrives.

Someone needs to be watching afterward

Someone needs eyes on the new site right after the switch happens. Not staring at it nonstop, refreshing every few seconds. Just checking key pages, the contact form, and the checkout flow if you have one, on a regular interval through the first stretch after launch.

What they're watching for: broken links, images that didn't carry over cleanly, forms that silently fail to send anywhere, pages that load slowly or not at all on a phone. Catching these in the first hours is far less stressful than a customer catching them for you a week later, publicly.

Ask directly who that person is before launch day arrives. Write their name down somewhere specific. "Who's watching the site this afternoon" is not a question you should feel embarrassed to ask out loud in a planning call.

It doesn't need to be a technical person. It just needs to be someone paying attention, with a phone number the rest of the team actually has.

The difference between a calm launch and a rough one

A calm launch day is almost boring, in the best possible way. The DNS change goes in, staging becomes live, a few hours pass, someone confirms everything looks right. That's it. No drama, because the real work happened earlier, on staging, long before this day ever arrived.

A rough one traces back, almost every time, to something skipped beforehand. Nobody tested the contact form. Nobody checked what happens to old page addresses. Nobody had a plan for what to do if something looked wrong after the switch went live.

Having a rollback plan for your website launch day is what separates "we caught it and fixed it" from an actual scramble in front of customers watching it happen.

Choosing the right day and time

Pick a time when someone is genuinely available to watch the site afterward, and when a rough hour or two wouldn't hit your business at its hardest. A retail site probably shouldn't launch during its busiest sales window of the year. A quiet Tuesday morning beats a Friday evening if your team goes home at five.

This isn't superstition. It's making sure a person who can actually fix something is awake, present, and paying attention if something needs fixing. That single scheduling choice does more to keep launch day calm than almost anything else on this list combined.

The full picture this day fits into, from the first planning conversation through the weeks after, is worth reading if you haven't already: how to redesign a website without losing what works. And if you're not sure your new site has been tested enough to reach this day at all, what a staging site is and why it matters explains what should already be settled before anyone touches DNS.

More from the blog

All posts