This is for people who already have a website and are unhappy with it. (If you don’t have one yet and are wondering whether you need one, that’s a different question.)
When a site feels tired, the instinct is a redesign: new colours, new photos, a fresher look. Sometimes that’s exactly what it needs. Sometimes the problem is underneath, and a new coat of paint means paying twice. The trick is to sort the complaints before you spend anything.
Sort the complaints into two piles
Write down everything that bothers you about the site, then split the list.
Surface problems are about how it looks and reads: dated styling, weak photos, clumsy copy, an old logo, a homepage that undersells you. A refresh fixes these well, often on the existing platform and structure.
Foundation problems are about how it works: it’s slow, it breaks on phones, it’s painful to update, it’s on a platform that no longer fits, or the page structure doesn’t match how customers decide. New styling doesn’t touch these.
Questions that point toward a rebuild
- Is it slow even after the obvious fixes? If compressing images and removing plugins didn’t get the Core Web Vitals into the green, the problem is often the theme, page builder or hosting. Why website speed matters shows how to check.
- Does it fail on phones? Run this phone checklist. A site that was never built responsively usually needs rebuilding, not patching.
- Is updating it painful? If changing a line of text needs a developer, or you’re afraid to touch it, the foundation is working against you.
- Is the platform holding you back? Software that’s no longer supported, a theme the author abandoned, plugins that can’t be updated without breaking something, or a platform that can’t do what you now need, such as selling online.
- Has the business changed? New services, a new audience, a second language, a shop. If the site’s structure was planned around a business you no longer are, restyling won’t fix it.
If you answered yes to one or two, a focused refresh plus specific fixes is probably enough. If most are yes, you’re looking at a rebuild, whatever you decide to call it.
There’s also a middle path: keep the platform and content, but rebuild the templates and key pages. It’s worth asking about when the platform is fine and the theme isn’t.
If you rebuild, protect what already works
A rebuild can throw away search traffic you spent years earning. The usual cause is simple: old page addresses stop working. Google’s guide to moving a site with URL changes sets out what to do. In short:
- Make a list of every existing URL from your sitemap, analytics and Search Console, and map each one to its new address.
- Set up permanent (301) redirects from each old URL straight to its closest new equivalent, not all to the homepage.
- Keep the redirects for as long as possible; Google says generally at least a year.
- Keep content that ranks. Check in Search Console which pages bring visitors and carry their content over, improved, rather than dropping it.
- Submit the new sitemap in Search Console and watch the indexing reports for a few weeks after launch.
Also carry over your analytics setup and key events, so you can compare before and after. Without that, you’ll never know whether the new site performs better.
Get a second opinion before you commit
You don’t have to make this call blind. A review of the current site should tell you what’s worth keeping, what’s fixable and what’s holding you back. Sometimes the honest answer is “rewrite the homepage and fix the form,” which is a much smaller job than a full rebuild. If you’d like that review, send us the link and we’ll tell you: refresh, rebuild, or leave it alone. Our web service page explains how we handle both.