How to redesign your website without losing what already works
What counts as a redesign versus a smaller fix
Someone told you your website needs a redesign. Maybe a designer said it. Maybe you said it to yourself after one too many people mentioned the site looks dated. In practice, that word covers two very different projects, and knowing which one you're actually signing up for matters before anything else.
A smaller fix touches the surface. New photos, updated copy, a cleaner header, a color palette layered onto the same pages and the same platform underneath. A redesign generally means the structure itself changes too: new page templates, a new platform, sometimes a new URL scheme entirely. That distinction is why everything else in this post applies mainly to the second kind of project.
If you're not sure which one your site actually needs, that decision deserves its own look. Signs your website needs a rebuild, not a few fixes walks through the difference in detail. This post assumes you've already landed on redesign.
Why rankings and content history are the thing to protect
A redesign puts something specific at risk, and it isn't how the site looks. It's everything search engines and existing links already know about the site as it stands today. Every page that currently ranks for something got there through months, sometimes years, of accumulated signal: links pointing to it, people finding it, content that kept answering a real question well enough to keep showing up.
A visual refresh alone doesn't erase any of that. A new platform, or a restructured set of URLs, can — but only if nobody plans for it. The design is the part everyone talks about in the first meeting. The content history is the part quietly paying your bills right now, and it deserves at least equal attention.
What happens to the individual pages and posts — merged, kept as-is, or cut entirely — gets a full answer of its own at what happens to your old content during a website redesign. Losing rankings outright is a related but separate risk, with its own mechanics.
The migration mechanics at a glance: staging, DNS, cutover
Most redesigns follow roughly the same shape underneath, even when the visual results look nothing alike. The new site gets built somewhere the public can't see it, on what's called a staging environment. Testing happens there, out of view. Nothing about your live site changes during this phase, no matter how long it takes.
When the new site is ready, DNS — the system that points your domain name at a server — gets switched over. That switch is the cutover, and it's the moment your visitors start landing on the new site instead of the old one. It can be quick once it's initiated, though the exact timing depends on your domain's settings and how records propagate.
The outline sounds simple. What actually can or can't break during that window is a longer conversation, worth having before you agree to a start date.
The downtime question, answered directly
Will your current site go down while the new one gets built? Ask it plainly, because it's the question underneath most of the anxiety here. It doesn't have to happen that way. Building on staging means your live site keeps running, untouched, right up until the cutover happens.
When downtime does occur, it tends to cluster around the cutover itself and around DNS propagation, not around the weeks of build work leading up to it. That's a meaningfully different risk than the fear most people carry into this conversation, which is that the site disappears the day the project starts.
The full mechanics of what can and can't cause an outage, and the exact questions to ask about it, live at will your website go down during a redesign. It's worth reading before signing anything.
Redirect maps and preserving what already ranks
One of the more overlooked pieces of a redesign is what happens to the old URLs. If a page currently sits at yoursite.com/services and the new site moves it to yoursite.com/what-we-do, anyone who bookmarked that old link, and any search engine that indexed it, needs to be pointed somewhere.
The tool for that is a redirect map: a planned list of every old URL and where it should now lead. Without one, old links quietly turn into dead ends, and search engines lose the trail they already built for that page over time.
How that map actually gets built, starting from an inventory of the old site, is covered fully at what a redirect map is and why your redesign needs one. Preserving search rankings specifically has its own dedicated mechanics too, at how to redesign a website without losing your google rankings.
Scoping the rebuild before you talk to anyone
Before getting quotes from anyone, write down what's actually changing. Which pages stay. Which features are new. What's getting cut entirely. A loose idea like "redesign the site" turns into a fuzzy price the moment three different people each guess at what you meant by it.
A written scope also gives you something concrete to hold a contractor to later, when the project inevitably drifts a little from that first conversation.
The process for building that document, and using it to compare quotes fairly, is laid out at how to scope a website rebuild before getting quotes.
Choosing who runs the migration
Not everyone who builds attractive websites has actually run a migration. The two skills overlap but aren't identical — moving a site safely requires understanding redirects, DNS, and platform quirks, not just design software and visual taste.
Ask directly about migration experience, separate from design portfolio. Ask, too, what happens to your admin access and your files during the transition, since that's a distinct question from who's doing the design work.
The fuller vetting process is at how to choose who builds your website, and the access and ownership questions specifically belong at who owns your website. Both are worth reading before the first real conversation with anyone about this project.
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