Will your website go down while it's being redesigned
What 'downtime' actually means technically versus what people fear
Every business owner who's ever agreed to a redesign has wondered, at some point, whether their site is about to vanish while it happens. Fewer people actually ask the question directly out loud. It can feel like assuming the worst about someone before the work has even properly started.
Ask it anyway. It's a fair, specific, entirely answerable question. A straight answer is exactly what you should get back from anyone doing this work, not a shrug or a vague reassurance.
Technically, downtime means the site is unreachable. A visitor types your address into a browser and gets an error instead of a page loading. What people actually fear is broader and vaguer than that single definition: the site looking broken somehow, features not working right, search rankings quietly slipping without warning.
Those are real, valid concerns. They simply aren't downtime in the strict, technical sense, and they get caused by different things entirely. Separating the technical meaning from the general dread helps you ask sharper questions and get less vague answers back from whoever you're talking to.
Worth saying plainly: it's a completely reasonable thing to worry about, and asking it doesn't make you difficult. Your website is how customers find you and reach you. A vague answer to a specific question deserves a follow-up, not a shrug of your own in return.
Why a rebuild happening on staging doesn't touch the live site
A competently run redesign happens on a private staging copy the entire time it's being built, completely separate from the site your customers currently use every day. What a staging site is and why it matters covers how that separation actually works in detail.
The practical result is straightforward: your live site keeps running, untouched, through essentially the entire project, start to finish. If the answer to "where exactly is this being built" isn't staging, ask more questions before you agree to anything at all.
This single fact does most of the work in answering the downtime question honestly. The build itself simply isn't happening anywhere near your live site.
The handful of minutes that are actually risky: the DNS switch itself
There is one genuinely sensitive moment in the whole process: the DNS switch that points your domain at the new site instead of the old one. This moment is short. It's deliberate. It doesn't happen gradually or by accident, and it's the single point in the entire project where a mistake could actually cause visible downtime.
A careful team treats that specific moment with real, deliberate attention. Doing it during a planned window agreed on in advance. Checking the result immediately afterward. Being ready to undo it fast if something looks even slightly wrong.
Outside that narrow window, there's genuinely nothing else in the project that touches your live site directly. Everything else happens on staging, safely away from it, days or weeks before that one deliberate moment.
What causes real visible downtime, and it's rarely the redesign itself
When sites do go down during a project, the cause is generally something adjacent to the redesign rather than the redesign itself. A domain renewal that got missed during a busy stretch of the year. A hosting account that quietly lapsed. A DNS change made carelessly outside a planned window by someone in a hurry.
These are process failures. They are not an inherent risk of redesigning a site in itself. Knowing this changes what you should actually ask about going in. Not "will my site go down," but "who's specifically tracking the domain renewal and hosting bills during this project."
That one question, asked early, does more to protect you than any promise about the redesign itself ever could.
Asking for a written cutover plan instead of a verbal promise
A verbal "don't worry, it'll be fine" is not a plan of any kind. A written cutover plan names the specific day and time of the DNS switch, who's making the change, who's checking the result afterward, and what happens next if something looks wrong.
Ask for this in writing before the project even starts, not as an afterthought once it's already underway. If nobody can produce something like this on request, that tells you more than any answer to the downtime question itself ever could.
A plan doesn't need to be long or formal, and it doesn't need a lawyer involved anywhere in it. A few lines naming the day, the person making the change, and the check that happens right afterward is enough to hold someone to.
What to check in the first hour after launch
Right after the DNS switch happens, check the site from a couple of different devices and networks yourself. Load the homepage. Submit a real test through the contact form. Click a handful of internal links across a few pages.
This takes minutes, not hours, and doesn't require anyone technical to do it. It catches the kind of problem that's much easier to fix quietly in the first hour than after a real customer runs into it first and mentions it publicly, somewhere you'd rather they hadn't.
What happens on website launch day walks through that whole sequence in order, and having a rollback plan for your website launch day covers what happens if that first-hour check turns something up worth worrying about.
If you're weighing whether to keep the current site running until the new one is genuinely ready, why your old website should stay live until the new one is ready makes that case directly, and how to redesign a website without losing what works covers everything beyond just this one narrow question.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go