Why your old website should stay live until the new one is ready

The risk of a gap where nothing is live at all

Your current site is outdated and you know it better than anyone. The moment work starts on the new one, there's a real urge to just take the old one down immediately, so at least nobody's looking at the embarrassing version while the good one gets built behind the scenes.

It feels slightly silly to say that urge out loud to another person, but it's an extremely common one to have. Almost everyone rebuilding a site has felt it at some point.

Acting on it tends to create a worse problem than the one it was meant to solve. The fix for an embarrassing site is a better site, not an empty one sitting where the old site used to be, answering to nobody.

The embarrassment is temporary either way, and mostly private besides. A gap in what a customer finds, right when they go looking for you, tends to stick around in their memory a lot longer than an outdated color scheme ever would.

If the old site comes down before the new one is genuinely ready to take its place, there's a stretch of time where your business has no website at all. Customers searching for you find nothing, or an error page instead of a business. Anyone who bookmarked you, anyone mid-conversation about hiring you, hits a dead end at exactly the worst possible moment for that to happen.

An outdated site is still a working site, doing its job. A blank gap is not a working anything. Between the two, the outdated one is doing you far more good sitting there than nothing would.

Think about what a gap actually costs you in practice. A search engine sees an error where a page used to be. A customer sees a business that might not exist anymore. Neither impression is one you want, even for a short stretch, and neither is easy to undo once it's formed.

How the two versions can exist at the same time without conflict

The new site gets built on a separate, private staging address the whole time, while the old one keeps running at your real domain, completely untouched by any of the work happening behind it. They don't interfere with each other in any meaningful way. Nobody browsing your actual website sees a single sign that a new one is quietly being built behind the scenes.

What a staging site is and why it matters explains that separate, private space in far more detail, including exactly who should be looking at it while it's still being built.

The two addresses don't even resemble each other in any way. There's no way for a customer to stumble onto the unfinished version by accident while looking for you online.

When it's actually safe to take the old one down

The old site can safely come down once the new one has been fully tested, once every page, form, and link has actually been clicked and checked rather than just glanced at from a distance, and once someone's ready to make the specific DNS switch that sends visitors to the new address. Not a day before any of that.

If you're not entirely sure whether "ready" has actually been reached yet, ask directly: has everything genuinely been tested, or does it just look finished on the surface? Those are two very different states to be in, and the gap between them is exactly where most launch-day problems tend to start.

There's no rush to take the old one down early just because the new one exists. Both can sit there, quietly, for as long as the work needs.

What to do about email and domain settings while both exist

Email tied to your domain runs on entirely separate settings from the website itself, and it's an easy, understandable mistake to assume that touching one touches the other. It generally doesn't. Still, it's worth confirming explicitly with whoever manages your domain that email won't be affected until you're actually ready for it to be.

This is a detail worth asking about directly rather than simply assuming it's fine, because a mistake here means missed customer messages, not just a wonky-looking web page for a few hours. Ask specifically, get a specific answer back in writing if you can, and move on to the next item on the list.

Avoiding confusing customers who bookmark or search for you mid-project

A customer who bookmarked your site last month, or found you through a search result from before the project even started, expects to land somewhere familiar when they click that link again. Keeping the current site live and unchanged until launch means that expectation gets met the entire way through the project, right up until the actual switch happens.

That continuity is worth more than a lot of people give it credit for going in. It's the difference between a customer thinking nothing changed at all and a customer quietly wondering if your business closed down altogether.

A business that seems to have vanished loses more than a single visit. It loses the benefit of the doubt the next time that customer needs whatever it is you sell, and reaches for a competitor's name instead of yours.

The day the switch finally happens is its own separate event, covered in what happens on website launch day. And if something needs to be undone after that switch, having a rollback plan for your website launch day is exactly what that looks like in practice. For the full picture this one decision sits inside, see how to redesign a website without losing what works.

More from the blog

All posts