Redesign or rebuild? How to decide before you spend.

Sooner or later every business looks at its website and thinks: this isn’t working any more. The next question is usually the expensive one. Do we give it a new look, or do we start again from scratch?

Both are valid answers. They just fix different problems. A redesign changes how the site looks and how information is organised. A rebuild changes what the site is made of — the platform, the code and how content is managed. Picking the wrong one is how projects end up costing twice.

The difference, in plain terms

Think of your website as a shop. A redesign is a refit: new layout, new signage, better shelving, the same building. A rebuild is moving to a new building because the old one can’t hold what you sell any more.

Signs a redesign is enough

If the foundations are sound and the problem is mostly how the site feels to visitors, a redesign is usually the better use of budget.

• Your team can update content easily, and the site rarely breaks.
• Pages load reasonably fast, including on mobile data.
• The site looks dated next to competitors, or no longer matches your brand.
• Visitors can’t find key information — prices, services, how to contact you.
• Your platform is still supported and receiving security updates.

Signs you need a rebuild

When the problems sit underneath the design, a new coat of paint won’t last. These are the signals that usually point to a rebuild:

• Small edits need a developer, or break something else on the page.
• The site is slow even after images are compressed and caching is set up.
• You need features the current setup can’t support — bookings, accounts, payments, multiple languages.
• The platform, theme or plugins are no longer maintained.
• Nobody fully understands how the site was built, or who has the logins.

Five questions to answer first

1. What should a visitor do on the site? Call, book, buy, apply? Write it down — it decides the structure.
2. Which pages bring in traffic and enquiries today? Your analytics and Search Console will show this, and those pages need protecting.
3. What does the site need to do in the next two years that it can’t do now?
4. Who will update it, and how often?
5. Who owns the domain, hosting and code? If it isn’t you, fix that first, whichever route you take.

Protect what already works

The biggest hidden cost of a new website is lost search traffic. It happens when pages that ranked well are removed or moved without telling search engines where they went.

• Export a list of every URL on the current site before anything changes.
• Keep high-performing pages, or redirect them permanently (301) to their new equivalents.
• Carry over page titles, meta descriptions and headings that already rank.
• Check Search Console in the weeks after launch for errors and missing pages.

The middle path: rebuild in stages

It doesn’t have to be all or nothing. Many businesses keep the parts that work and replace the rest — a new homepage and service pages first, the blog or shop later. This spreads the cost and lets you check results before committing to the next stage.

The short version

Redesign when the foundations are good and the experience is the problem. Rebuild when the foundations are the problem. Either way, decide what the site must achieve, protect the pages that already bring in business, and make sure everything ends up in your name.