Website Redesign vs Rebuild: Which One Does Your Site Actually Need?

Most organisations that contact me don't need their first website. They have one already, and it's letting them down: it looks dated, it's slow, enquiries have dried up, or nobody in the team can edit it without something breaking.

At that point there are two ways forward. A redesign keeps the foundations and replaces what sits on top. A rebuild replaces the foundations too. They can differ in cost by a factor of three or more, and I've spent 15 years watching businesses pay for the wrong one: expensive rebuilds that a redesign would have covered, and doomed redesigns stacked on foundations that should have been condemned.

This guide explains how to tell which one your website actually needs, what each costs in Brisbane in 2026, and the part almost everyone gets wrong: protecting your Google rankings through the change.

What Counts as a Redesign, and What Counts as a Rebuild

The words get used loosely, so here's how I use them.

A redesign keeps your platform and codebase and changes what visitors experience: visual design, page layouts, content structure, messaging, and conversion paths. Your CMS, hosting, and underlying code stay put. Think renovation.

A rebuild replaces the platform itself. New codebase, often a new CMS, usually new hosting, with your content migrated across and the design done fresh as part of it. Think knockdown and rebuild, on the same block, keeping the address.

There's a middle case worth naming: a replatform, where the design is broadly fine but the technology underneath has to go. It's priced and planned like a rebuild, because the work is in the foundations either way.

Signs a Redesign Is Enough

A redesign is the right call when the foundations are genuinely sound. That usually looks like:

• The platform is mainstream and current. WordPress, Statamic, Shopify, or a custom build on a supported framework, with software versions that are still receiving security updates.
• Someone competent can work on it. The code is clean enough that a developer can make changes confidently, or it's a standard CMS setup without years of hacks layered on it.
• The site works, it just doesn't perform. Pages load, forms submit, nothing is held together with tape. The problem is that it looks ten years old, the content no longer matches your business, or visitors arrive and don't enquire.
• Your needs haven't fundamentally changed. You needed a marketing site then, you need a marketing site now. You're not trying to bolt an online store or a customer portal onto a brochure site.

In these cases the money goes where the problem is: audience thinking, content, design, and conversion. That's the cheaper path, and when the foundations deserve it, it's the right one.

Signs You Need a Rebuild

Some websites shouldn't be renovated, and the signs are usually technical:

• End-of-life software. If your site runs on PHP or CMS versions that stopped receiving security updates years ago, a fresh coat of design is paint on rust. I regularly meet websites where the CMS looks fine from the dashboard while the server underneath runs software that reached end of life years earlier.
• Theme and plugin archaeology. Many older WordPress sites are a purchased theme, a page builder, and 40 plugins deep, each patching a gap in the last. Every update is a gamble and every change has side effects. Rebuilding costs less than untangling.
• Nobody will touch it. If your last three developers have all suggested starting again, believe them. A codebase that experienced people refuse to work on is telling you its market value.
• The fixing never stops. If the developer who built your system spends every month repairing it rather than adding to it, that's a verdict on the build. Paying for those repairs is paying twice for the same code.
• It's slow in ways that can't be fixed. Caching and image optimisation rescue some sites. They can't rescue a site whose theme ships a megabyte of code to render a heading. Performance that's architectural doesn't respond to tuning.
• The platform no longer fits the business. You've outgrown a template, you need integrations your platform can't do, or you're locked into a proprietary builder you don't own. A custom platform conversation is different from a design conversation.
• Repeated security incidents. A site that keeps getting compromised has a structural problem, not a bad-luck problem.

If two or more of those describe your website, stop budgeting for a redesign. It will consume most of the money and leave the actual problem in place.

The Assessment I Run Before Recommending Either

When someone asks me whether their site needs a redesign or a rebuild, I look at five things before giving an answer:

1. The stack. Platform, CMS version, PHP version, hosting environment, and how far behind current everything sits. This is the single biggest factor.
2. Performance. Core Web Vitals, page weight, server response times, and whether the causes are fixable configuration or baked-in architecture.
3. Search equity. What the site ranks for, which pages earn traffic, and what has to be protected through any change. Sometimes an unloved site has rankings worth serious money, and that changes how carefully you move.
4. Content. Whether the structure and messaging can be reshaped in place, or whether the content model itself (the way pages, sections, and data are organised) is the constraint.
5. The editing experience. If your team avoids updating the site because the CMS fights them, that's a real cost, and it weighs toward rebuilding on something better.

You can run a rough version of this yourself: ask your host what PHP version you're on, run your homepage through Google's PageSpeed Insights, and ask whoever maintains the site how confident they feel making changes. The answers usually point clearly in one direction.

What Redesigns and Rebuilds Cost in Brisbane

For an established small-to-medium organisation in Brisbane in 2026, sensible budget ranges look like this:

• A design refresh (visual updates within the existing structure): roughly $5,000 to $15,000.
• A full redesign (new design, restructured content and conversion paths, same platform): roughly $10,000 to $30,000 depending on size and how much content strategy is involved.
• A rebuild: priced like a new website, because it is one, with migration on top. Custom projects typically start from $15,000 and scale with functionality; I've broken the bands down properly in my Brisbane website cost guide.

The comparison that matters isn't redesign-versus-rebuild on price alone. It's lifetime cost. A $12,000 redesign on failing foundations buys two years before the rebuild happens anyway, and you pay for design twice. If the foundations are condemned, the rebuild is the cheaper option on any horizon longer than a year or two.

Who You Hire Decides Which Problems You Get

Not every enquiry I get is about a brochure site. A solid share are businesses running custom Laravel or PHP software that doesn't do what they need, or does it badly, and the developer who built it is still there, still fixing things, month after month.

That pattern tells you most of what you need to know. A developer permanently repairing their own work isn't unlucky, they're out of their depth. On a healthy project the fixes taper off in the weeks after launch and the conversation moves on to what the software should do next: new features, better reporting, the workflow that got cut from round one. When it never moves on, when every invoice is another round of patching things that were meant to work in the first place, the build is the problem, and more patching won't turn it into a good one.

Nearly every time, that traces back to the hire. The work needed someone who builds business software, and it went to someone who builds websites.

Those are different jobs. Custom software lives or dies on the things brochure sites never touch: talking to an ERP or accounting system and coping when it returns nonsense, moving data between platforms without silently losing it, permissions and audit trails, holding up under real traffic, automated tests so a change in one corner doesn't quietly break another, and a deployment process that isn't someone dragging files onto a server at 11pm. A developer whose entire career is small template sites has never had to solve any of it. Not because they're bad at what they do, but because what they do never asked.

So the questions to ask before handing over a rebuild aren't about design taste:

• What have you built of comparable complexity, and can I speak to that client?
• Which systems have you integrated with, and what happened the first time one of them failed mid transaction?
• How do you test, and what's actually covered?
• How do changes reach the live site?
• A year after launch, what does working with you look like?

Vague answers there are the same warning sign as a vague migration plan. You're not being difficult by asking. You're avoiding the exact situation that has people calling me to take over someone else's software.

How to Keep Your Google Rankings Through the Change

This is the step that turns successful projects into disasters when it's skipped. Your existing site has search equity: pages that rank, URLs that other sites link to, and years of accumulated trust. Handled carelessly, a relaunch torches it, and traffic drops that take months to recover.

The protection work isn't complicated, it just has to actually be done:

• Crawl the existing site first so there's a complete inventory of URLs, titles, and the pages that earn traffic.
• Keep URLs the same wherever possible. The best redirect is the one you never need.
• 301 redirect every URL that changes to its closest equivalent, individually mapped, not blanket-redirected to the homepage.
• Preserve what's ranking. If a page earns search traffic, its content and intent survive the migration, even if its design doesn't.
• Re-verify after launch. Watch Search Console for crawl errors and ranking movement in the weeks after, when problems are still cheap to fix.

Ask anyone quoting your project to walk you through their redirect and migration process. If the answer is vague, that's a real risk to your revenue, not a technical detail.

Sometimes the Right Answer Is Neither

An honest assessment sometimes comes back: keep the site. If the platform is supported, performance is acceptable, and the design is merely unfashionable rather than broken, the highest-return spend is often content, targeted landing pages, or conversion improvements, not a new website.

I've talked organisations out of rebuilds for exactly this reason. A website that quietly does its job doesn't need to be new, it needs to be maintained properly and improved where the data says it's weak.

Frequently Asked Questions

How much does a website redesign cost in Brisbane?
A visual refresh on an existing platform typically runs $5,000 to $15,000, and a full redesign with restructured content and conversion paths runs roughly $10,000 to $30,000. If the platform itself has to change, you're pricing a rebuild, which starts around $15,000 for custom work.

How do I know if my website needs a rebuild instead of a redesign?
Check the foundations: software versions that no longer receive security updates, developers who refuse to work on the code, performance problems that tuning can't fix, repeated security incidents, or a platform your business has outgrown. Two or more of those points to a rebuild.

Will I lose my Google rankings if I rebuild my website?
Not if the migration is done properly: crawl the old site, keep URLs where possible, individually 301 redirect everything that moves, preserve the content that ranks, and monitor Search Console after launch. Rankings drop when this work is skipped, not because rebuilds are inherently risky.

How long does a redesign or rebuild take?
A focused redesign typically runs 4 to 10 weeks. A rebuild follows normal custom website timelines of 8 to 16 weeks depending on scope, plus the migration work.

Can a WordPress developer build custom business software?
Some can. Many can't, and that mismatch is the most common reason I'm called in to take over a custom system. A Laravel or PHP platform stands on integrations, data integrity, automated testing, and deployment discipline, none of which a career of small template sites requires. Ask for comparable work before assuming the skills carry across.

Can I redesign my website in stages?
On a sound platform, yes, and it's often the smart way to spread cost: restructure the highest-traffic templates first and work down. On a failing platform, staging just spreads the pain, because every stage fights the same foundations.

I regularly take over existing websites in exactly this situation, and the first thing I'll tell you is which of these paths your site is actually on, including when the answer is "keep it." You can read about how I approach web design and development in Brisbane, or get in touch and I'll give you a straight assessment.