Business Websites
Website Redesign vs Rebuild: Which One Does Your Business Need?
Redesign when the site works but looks wrong. Rebuild when the structure or platform is the thing holding you back.
4 min read
A redesign changes how the site looks and reads. A rebuild changes what it is built on and how it is structured.
The question is not which is better. It is which problem you have. Businesses that get this wrong usually spend on a redesign, feel better for a few months, then find the original problem is still there because it was never a visual one.
The quickest way to tell them apart: if you can describe what is wrong without mentioning how it looks, you probably need a rebuild.
When a redesign is the right call
A redesign makes sense when the foundation is sound and the presentation is the problem. The site loads reasonably, works on a phone, can be updated without a developer, and has a structure that matches what the business does.
Typical signs:
- It looks dated next to competitors, and you have heard so from customers
- The branding has changed and the site has not
- The copy describes a version of the business from several years ago
- Pages are cluttered and the important information is buried
- It works but does not reflect the quality of what you sell
A redesign is usually faster and cheaper, and the risk is lower because URLs and structure stay put. If this describes your situation, resist being sold a rebuild.
When a rebuild is worth it
A rebuild is warranted when the problems are structural. New paint does not fix these, and attempting a redesign on top of them tends to cost more in the end.
Signs the foundation is the issue:
- The site is slow, and the cause is how it was built rather than the images on it
- It was built before mobile mattered and adapts badly to a phone
- Every content change needs a developer
- The platform or its plugins are no longer maintained, which is a security problem as well as a functional one
- One page tries to cover every service, so nothing can rank for anything specific
- You need something the current setup cannot support, such as online ordering, bookings, or an integration with another system
- Nobody has the login details, or the original developer is unreachable
The middle path most businesses overlook
There is a third option that gets skipped because it is less satisfying to buy: fix the specific things that are wrong.
If the site is slow because of oversized images, compress them. If services are crammed onto one page, split them. If the form is broken, repair it. If the platform is out of date, update it and put maintenance in place.
This kind of work often produces more measurable improvement than a redesign, at a fraction of the cost. It is worth asking for a list of what is actually wrong before agreeing to replace everything.
- Website maintenanceWhere the ongoing fixes and updates sit once the immediate backlog is cleared.
Protecting search visibility through the change
A rebuild is one of the most common ways a business loses search visibility it had already earned. It rarely happens dramatically. Traffic drops over a few weeks and by the time anyone connects it to the launch, the cause is harder to trace.
This is avoidable, and it is a reasonable thing to ask about before signing anything.
What needs to happen:
- Record every existing URL before work starts, along with which ones currently receive traffic.
- Map each old URL to its closest equivalent on the new site, and set up redirects. Every one, not just the main pages.
- Keep the content that was already earning visibility. Shortening a page for design reasons is how businesses lose rankings they did not know they had.
- Keep headings as real headings rather than converting them into images.
- Remove the rule that stopped search engines indexing the staging site, before launch rather than after.
- Check indexing and errors for several weeks afterwards, so a problem is caught while it is still small.
- SEOHandling structure, redirects, and indexing around a site change.
Questions worth asking a developer
These separate a considered proposal from a template one:
- What specifically is wrong with the current site, and which of those needs a rebuild rather than a fix?
- How will existing URLs be handled, and will every old page redirect somewhere sensible?
- Who can update content afterwards, and does that need a developer?
- What happens to the site's speed, and how will that be measured?
- What is not included that we will need within a year?
- Who is responsible for updates and backups after launch?
The answer to the first question tells you the most. If a developer recommends a full rebuild without having looked at the current site properly, that is a recommendation about their preferred way of working rather than about your business.
A short way to decide
Write down the three things that most annoy you about the current website.
If all three are about appearance, a redesign will fix them. If any are about speed, structure, updating content, or something the site cannot do, that one will still be there after a redesign, and it should drive the decision.
Then check the third option. Ask what it would cost to fix just those three things. Sometimes the answer makes the larger project unnecessary, and sometimes it makes clear that the larger project was always the right call.
We look at the existing site before recommending either path, because the honest answer is often narrower than a full rebuild.
If a rebuild is genuinely warranted, URL mapping and redirects are part of the work rather than something handled afterwards.
Continue reading
Business Websites
What Should a Business Website Actually Include?
Fewer pages than most proposals suggest, with far more attention on the few that customers actually read.
Business Websites
How Much Should a Business Spend on a Website?
There is no useful average, but there is a reliable way to work out what your project should cost and to compare proposals fairly.