Questions to ask before you commit to a website redesign
What's the plan for downtime and the cutover
Someone has handed you a redesign proposal, and it probably reads fine on paper. Before you sign it, there's a short list of questions worth asking out loud first, and this is the opening one: what actually happens to your current site while the new one gets built, and during the switch itself?
A reasonable answer describes building on a private staging area first, with your live site left completely untouched until a planned cutover moment. A vague answer, or one that dodges the specifics entirely, is worth pressing on directly. Ask them to walk through it step by step. A team that's done this before can.
Ask what happens on a day you're closed, too, in case something needs fixing before your customers are back online. The answer tells you how much thought has actually gone into this part.
The full mechanics behind this exact question are laid out at will your website go down during a redesign.
What happens to my existing content and rankings
Ask directly what happens to the pages currently on your site: the blog posts, the service pages, anything already published and live. Are they getting rewritten, kept as-is, merged together, or cut entirely, and who's actually making that call?
This is worth asking even if you don't think your current content is anything special. Some of it may be doing quiet work you're not fully aware of, in search results or otherwise, and it's worth protecting deliberately rather than by accident. Ask for a specific list of which pages carry over.
If the answer is a shrug, or something like "we'll figure that out as we go," treat that as an answer too. A plan for your content should exist before the build starts, not get improvised partway through it.
Who has access to what during the transition
During a redesign, access to your domain, hosting, and files can end up scattered across accounts belonging to whoever's doing the work, rather than to you. Ask plainly who holds the login to what, and confirm you'll get your own direct access, not just borrowed access sitting inside someone else's account.
This question matters more than it sounds like it should. Get specific here. Ask for the domain registrar login, the hosting login, and the site's admin login by name, not as a vague bundle called "access." It has its own full answer at who owns your website, worth reading before you sign.
Write the answer down somewhere you'll actually find it again. A verbal assurance that "you'll have access" is easy to remember wrong months later, once the project has moved on to other things and everyone's attention is elsewhere. Ask for it in an email, not just a conversation, so there's a plain written record either side can point back to.
What's explicitly in scope and what isn't
A good proposal names what's included clearly enough that you could hand it to a completely different person and get a comparable quote back. If the scope reads vague, something like "a modern redesign" with no real specifics, ask for it in writing before agreeing to anything else.
This is also the moment to ask what happens if something you assumed was included turns out not to be. A written scope protects both sides from that exact argument happening later, once work is already underway. Get the answer in the proposal itself, not in a verbal aside during a call.
If you're not sure yet exactly what to ask for, working through how to scope a website rebuild before getting quotes first gives you the language to make this question specific instead of vague.
What the rollback plan is if something goes wrong
Ask what happens if launch day doesn't go smoothly. Is there an actual plan to revert to the old site if something breaks, and who decides to use it in the moment? A team that's already thought about this will have a quick, specific answer ready. A team that hasn't will need a minute to think, and that pause tells you something too.
What a real rollback plan actually includes is covered fully at having a rollback plan for your website's launch day. Read it before this conversation, not after.
Even a brief answer is fine here. What you're checking for is whether the question has been considered at all, since a team that's never thought about it is more likely to improvise under pressure.
What happens after launch, not just at launch
The proposal probably describes the build and the launch itself in careful detail. It's worth also asking what happens the week after, and the month after that. Who fixes something if it quietly breaks. Who handles updates going forward. Whether ongoing care is included already or a separate conversation entirely, billed on its own.
A redesign that ends the moment the site goes live, with no plan for what comes next, tends to age the same way the old site eventually did: quietly, until it's the thing getting replaced all over again. Ask this question even if launch feels far away right now. The answer shapes how the whole project gets built, not just what happens afterward.
It also tells you something about the proposal itself. A plan that only thinks as far as launch day is a different commitment than one that's already thinking about year two.
That ongoing question deserves its own answer, at who takes care of your website after launch. This whole list of questions is pulled from a fuller picture, worth reading in full at how to redesign a website without losing what works before you sign anything at all.
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