Should you redesign your website or fix what you already have?
A redesign is the most expensive answer to most website problems, and sometimes it's the right one. Here's how to tell which problems a fix will solve, which ones need a rebuild, and what to protect whichever way you go.
Fix what you have when the problems are specific and the foundation is sound: slow pages, a weak homepage, forms that don't deliver. Redesign or rebuild when the software is out of support and can't be upgraded, the way the site was built makes every change a fight, or the business has outgrown its structure. Whichever you choose, protect the old page addresses.
People tend to ask this question when something about their website is bothering them: it looks old, it's slow, it doesn't bring in work, or it's a chore to change. A redesign promises to fix all of that at once. Sometimes it does. Sometimes it's an expensive way to replace a site that needed a few days of repair.
The way to decide is to name the actual problem first, then ask whether that problem lives in the design, the content, the technology or the structure underneath. Each one points to a different answer.
Match the problem to the fix
| What's bothering you | Usually fixable without a redesign? | What decides it |
|---|---|---|
| It's slow | Often yes | Whether the cause is hosting, images and plugins, or a heavy theme or page builder underneath everything |
| It doesn't bring in calls or inquiries | Often yes | Whether forms, phone links, clarity and trust are the problem, or the site no longer describes the business |
| It looks dated | Sometimes | A refresh of type, images and spacing can be enough if the structure is sound |
| It's hard to use on a phone | Sometimes | Whether the theme was built for phones at all |
| You can't update it without the developer | Rarely | Usually a sign of how it was built, not of the content |
| Every update breaks something | Sometimes | Abandoned plugins and old code can be replaced, up to a point |
| The platform is out of support and can't be upgraded | No | Unsupported software stops getting security fixes |
| The business has changed | No | New services, a new audience or a new location need new structure and content |
When a fix is enough
A site is usually worth keeping when the structure still matches the business, it runs on supported software, and the complaints are specific. Slow pages, a weak homepage, forms that don't arrive, a few outdated sections, missing photos: these are repairs and improvements, not reasons to start over.
It's worth checking the cheaper causes first. If the complaint is that the site doesn't bring in work, our guide to why customers aren't getting in touch covers the checks to run first, most of which take minutes.
It's also worth being clear about what a redesign can't fix. A new site won't fix a weak offer, an unclear message, too few visitors, or slow follow-up on the inquiries you already get. If those are the real problems, a redesign spends the money in the wrong place.
When it's time to rebuild
A rebuild starts to make sense when fixing would mean fighting the foundation. The usual signs:
- It runs on software that's out of support and can't be upgraded in place. Drupal 7, which reached its end of life in January 2025, is the usual example: moving off it means building a new site. Drupal 10 (end of life December 9, 2026) and PHP 8.2 (security fixes end December 31, 2026) are upgrades rather than rebuilds, unless the site's code can't run on the newer version.
- It was built with a theme or page builder that makes every change slow, every page heavy, and every update a risk.
- The structure doesn't match how customers decide. If people choose by location, by product or by trip type and the site is organized by something else, rearranging the furniture won't help.
- The business has outgrown it. New services, new locations or a different audience usually need new pages and new writing, not just a new look.
Two of our recent rebuilds are examples of the structure problem. The Donut King's old site was built on a theme made for online stores, with a product search and a cart, even though nothing could be bought on it. Blue Boar Inn had five pages and a single booking form for eight different rooms. Neither problem was something a fresh coat of paint would have solved.
The middle path
It doesn't have to be all or nothing. A refresh keeps the platform and the page structure but updates the design, the photography and the writing. Phased work fixes the foundation first, such as hosting, plugins and speed, then redesigns the pages that matter most, then the rest. For many small business sites, one of these is the right answer, and it usually costs less than a rebuild.
Whichever you choose, protect what works
A redesign can quietly throw away years of search visibility if the old page addresses stop working. Google's guidance for site moves is to map every old URL to its new one with permanent redirects, keep those redirects for as long as possible, generally at least a year, and expect some temporary movement in rankings. It also warns against pointing lots of old pages at one unrelated page, such as the new homepage.
Before anything launches, make a list of every page address the old site used, especially the ones that get traffic or have links from other sites, and decide where each one goes. When we rebuilt Smoky Cove Lodge's site, every address the old site used, including older pages that had been returning errors, either opens a page or redirects once to the page that replaced it.
A redesign can also cost you inquiries if it removes content or contact paths that were quietly working, such as a page that answered a common question or a phone number in the header. Note what the old site does well before anyone starts.
Protect the rest too: the analytics setup, so you can compare before and after; any forms, booking or payment connections; and your email, which lives in the same DNS records as the website and can break during a launch. Our migration checklist covers those details, and about a week after launch, check Search Console for a jump in pages that aren't indexed.
Questions to ask before you commit
- What specific problem will the redesign solve, and how will we know it worked?
- What happens to every existing page address?
- Is the content being rewritten, or poured into a new design?
- Who owns the finished site, the domain and the accounts?
- Who looks after it after launch, and what does that cost?
Sometimes the answer is to wait
If the site works, brings in business and runs on supported software, and the main complaint is that you're tired of looking at it, a redesign can wait. Put the money into the content, the photos and the follow-up instead. A website is a tool for getting work. When it's doing that job, it doesn't need replacing just because it's a few years old.