Every web agency on the internet will tell you your website needs a redesign, because selling redesigns is what web agencies do. This guide takes a different job: helping you work out whether yours actually does. Sometimes the answer is a full rebuild. Sometimes it is a $500 fix. And sometimes, genuinely, the right move is to leave the site alone and spend the money elsewhere.
The straight answer: redesign when the website is holding the business back
A website needs a redesign when its structure, technology, content or user experience is stopping it from doing its job properly. That job might be generating enquiries, taking bookings, selling products, building trust, supporting your sales conversations, attracting search traffic, explaining services clearly, qualifying leads or recruiting staff. Notice what is not on that list: being a few years old, using last year's fonts or looking less shiny than a competitor's new site.
First decide whether you need a redesign, refresh or fix
Most articles on this topic offer a binary: redesign or don't. Real websites need a four way decision and getting this framework into your head is worth more than the twelve signs that follow.
Option | Best when | Typical scope |
|---|---|---|
Leave it alone | The website is doing its job | Monitor, maintain, nothing more |
Patch | The problem is isolated | Fix the specific issue and stop |
Refresh | Foundation is strong but presentation is dated | Copy, imagery, styling, selected layouts |
Redesign | Problems run through the whole site | Structure, UX, content, design, development |
What counts as a website patch?
Compressing oversized images. Repairing a broken form. Fixing the mobile navigation. Rewriting one call to action. Installing proper tracking. Correcting spacing on phones. Improving a single landing page. Cleaning up technical SEO. The defining feature: the problem is localised, so the solution stays localised.
What counts as a website refresh?
A refresh keeps the sitemap, platform, functionality and content structure and improves what sits on top: colours, typography, imagery, section layouts, copy, proof, calls to action and visual consistency. It suits a website that basically works but no longer reflects the quality of the business behind it.
What counts as a full redesign?
A redesign revisits the foundations: strategy, user journeys, sitemap, page hierarchy, messaging, design system, components, mobile behaviour, content, development, tracking, SEO and QA. It may also involve a platform migration, a CMS change, new hosting or rebuilt integrations. It is the biggest intervention, which is exactly why it needs the strongest evidence.
The rest of this article is that evidence: the signs to look for and which of the four responses each one usually deserves.
Ask this, in order | Where the answer sends you |
|---|---|
Is the website achieving its main goal? | Yes: look only at isolated niggles. No: keep going |
Are the issues limited to a few pages or features? | Yes: patch those and stop |
Are the platform, structure and UX still sound? | Yes: a refresh will likely do it |
Do problems keep appearing across messaging, mobile, speed and structure? | That pattern is what earns a redesign |
12 signs your website may need a redesign
Each sign below comes with a severity and the response it usually deserves. Very few of them, on their own, justify a rebuild. Patterns of them do.
1. The website no longer matches the business
Businesses drift: new services, new positioning, new pricing, different customers, wider geography, a matured brand, a changed sales process. The website stays frozen at the year it launched. You now serve larger clients but the copy still talks to startups. You added two major service lines and they share one cramped page. The brand went premium and the site still looks DIY. The sales process changed and the only call to action is still Contact Us.
The response depends on depth. If the messaging and styling are wrong but the structure still fits, a refresh handles it. If the entire information architecture describes a business that no longer exists, that is redesign territory.
2. Visitors cannot quickly understand what you do
Run the 10 second test. A stranger lands on your homepage: can they tell what the business does, who it helps, where it operates, why they should care and what to do next, without scrolling forever? Warning signs are a vague headline, jargon, a long company introduction before any services appear, no obvious service list, an unclear call to action or three competing messages fighting for the same screen.
This often needs a homepage rewrite, navigation changes or restructured service pages rather than a full redesign. Clarity is mostly a words problem and words are cheap to fix compared to rebuilds.
3. The site gets traffic but few enquiries or sales
The classic performance signal and the most misdiagnosed. Possible causes: a weak offer, unclear calls to action, thin trust signals, weak service pages, the friction in your enquiry forms, poor alignment between ads and landing pages, the wrong traffic arriving in the first place or mobile friction. We wrote a whole diagnostic on why the visits come but the enquiries do not and the punchline is that the fix is often one landing page, one form or one message, not a new website. If paid traffic is a big share of visits, also check the way your paid search is being managed, because no design survives being sent the wrong clicks.
4. Mobile feels like a shrunk desktop site
Tiny text, awkward menus, buttons too close together, horizontal scrolling, giant images, forms that punish thumbs, popups blocking content, sticky bars covering the one button that matters. The decision test: if these are CSS and component issues, patch them one by one. If the entire site was conceived for desktop and every mobile fix creates a new workaround, the foundation is the problem and that is what redesigns are for. With most Australian service businesses seeing well over half their traffic on phones, this sign carries more weight than almost any other.
5. The website is noticeably slow
Slow has many parents: oversized imagery, an ageing theme, plugin bloat, cheap hosting, page builder overhead, script soup, heavy animation or simply poor development. Slow does not automatically mean redesign. Diagnose first with diagnosing why your website is slow, then work through the fixes that actually speed a site up: image optimisation, better hosting, caching, code cleanup, plugin reduction. Google's own page experience documentation is clear that Core Web Vitals feed its ranking systems, so the stakes are real and what LCP, INP and CLS actually measure translates the jargon. A redesign becomes the rational answer when the platform or theme itself is the bottleneck and fixing one issue keeps creating another.
6. Making small changes has become painful
The most underrated sign on this list. Only the original developer can edit pages. Every content change breaks a layout. Custom fields are undocumented. Plugins conflict. Adding a simple section needs development time and an invoice. The CMS fights everyone who touches it.
7. The site has become a collection of patches
Duplicated CSS. Page specific fixes stacked on fixes. Two page builders fighting in the same install. Unused plugins nobody dares delete. Old templates nobody remembers. Dozens of redirects papering over structural moves. Layouts that drift from page to page. Every website accumulates some of this; the sign is when the next patch costs more than solving the underlying architecture. That crossover point is where a rebuild stops being vanity and starts being maths.
8. Important services are buried
The business grew to twelve services, three industries and four locations, but the sitemap was designed when there were five pages. Symptoms: a giant dropdown menu, everything shoved under What We Do, money pages unreachable from the navigation and visitors guessing where information lives. This is a structural problem, information architecture and no amount of colour refreshing fixes structure.
9. Your brand has changed but the website has not
New logo, new positioning, premium pricing, professional photography, a different audience, a changed tone. If the platform, UX, structure and performance are already sound, a refresh carries the new brand onto the old bones perfectly well. A full redesign earns its place when the brand change also changes the customer journey, the offering, the architecture or the messaging hierarchy, in other words, when the bones changed too.
10. The website no longer supports SEO properly
Warning signs: important topics squeezed onto one page, a URL structure that makes no sense, duplicate pages competing with each other, weak internal linking, a thin service architecture, indexing issues, content that cannot be expanded or a platform that blocks the SEO work worth doing. Do not accept redesign for SEO as a recommendation until someone names the structural problem being solved. Ground yourself in the fundamentals of ranking an Australian business site first and make sure Search Console is set up so you can see the evidence before anyone starts quoting.
11. Accessibility problems are built into the design system
Low contrast everywhere, components that ignore keyboards, navigation a screen reader cannot use, unreadable forms, tiny tap targets, modals that trap people. One isolated issue can be patched. When the component system itself is inaccessible, every page inherits the problem and rebuilding those foundations during a redesign is more efficient than patching the same defect fifty times. Our full guide to accessibility for Australian business websites covers the obligations and the practical fixes and testing a few pages for contrast and keyboard access takes minutes if you want a quick read on which situation you are in. The W3C's WCAG guidelines are the benchmark worth asking any designer about.
12. You are embarrassed to send people to the website
This one is real, but interrogate it. Why exactly are you embarrassed? If the visuals feel dated, the photography is poor, the team page shows people who left in 2022 and the messaging is stale, a refresh probably clears it. If clients cannot find services, the site breaks on phones, forms fail, performance is poor and the content no longer describes the business, the embarrassment is pointing at structural failure and a redesign case is forming.
How old is too old for a website?
The redesign every three years rule is an agency invoicing schedule, not a law of nature. There is no universal expiry date. A two year old website can be badly broken; a seven year old website can still be quietly earning its keep. Age becomes relevant when older architecture starts creating real problems: security holes in unsupported software, mobile behaviour designed for a different era, performance limitations baked into the theme, editing difficulty, accessibility gaps or integrations the platform can no longer support.
Look at evidence before making the decision
Before anyone scopes anything, pull the numbers: organic clicks, conversion rate, lead volume and quality, phone calls, bookings, sales, form completion, engagement, mobile behaviour, site speed, indexing in Search Console, Core Web Vitals. Search Console is free and shows exactly how Google sees the site and getting usable numbers out of Google Analytics 4 turns vague feelings into evidence. Then interrogate what you find: what changed, when did it change, which pages are affected, is the problem across the whole site or three URLs and did traffic quality shift when a campaign or algorithm did?
The question a redesign decision must survive: is the website underperforming or is something upstream underperforming and the website wearing the blame? Traffic is down, therefore redesign is not reasoning. It is a reflex and it is an expensive one.
Run this 20 minute website redesign test
Set a timer, open your own website on your phone and score each area: 0 for poor, 1 for needs improvement, 2 for strong, per check. Be the harshest customer you have.
Minutes | Area | What to check | Max |
|---|---|---|---|
1 to 3 | Clarity | What you do obvious in 10 seconds; ideal customer obvious; call to action obvious | 6 |
4 to 6 | Mobile | Navigation, readable text, tap targets, forms, sticky elements | 10 |
7 to 9 | Performance | Homepage speed, image loading, layout jumping, delayed buttons, script errors | 10 |
10 to 12 | Trust | Reviews, credentials, recent work, real team, clear contact details | 10 |
13 to 15 | Conversion | Clear CTA, form length, phone access, service page CTAs, confirmation after enquiry | 10 |
16 to 18 | Content and structure | Services findable, pages match the current business, navigation sensible, content accurate, no dead ends | 10 |
19 to 20 | Technical health | HTTPS, working forms, broken links, analytics, Search Console, CMS still supported | 12 |
Total the score out of 68, then read it against the ranges below. These are decision support ranges, not science and they work best as a conversation starter with whoever maintains the site.
Score | Verdict | Where to focus |
|---|---|---|
55 to 68 | Keep it and improve selectively | Isolated fixes, conversion work, content, performance tuning |
40 to 54 | Refresh territory | Messaging, visuals, usability and content gaps; a targeted refresh likely beats rebuilding |
25 to 39 | Redesign worth investigating | Run analytics, technical, user journey and content audits before scoping anything |
0 to 24 | Structural rebuild likely | Problems probably span platform, UX, content, performance and conversion; continued patching costs more |
Twenty minutes covers the redesign question specifically. When you have an hour, the broader DIY website health check goes deeper on everything this quick pass skims.
When a website refresh is enough
Choose a refresh when the sitemap works, the CMS is workable, pages are structurally sound, mobile behaves, integrations run, speed is reasonable and the SEO architecture holds, but the styling is dated, the imagery is poor, the copy needs tightening, the proof is thin and the homepage needs rearranging. Typical scope: typography, colours, imagery, a new hero, sharper calls to action, selected component updates and a proper copy edit. A Fitzroy café with a structurally fine site, solid bookings and photography from three owners ago is the textbook case and it is why so much of the way we build hospitality websites is really about presentation and proof sitting on simple, reliable bones.
A good refresh costs a fraction of a rebuild and ships in weeks. Its limit is honest too: it cannot fix structure and pretending it can is how businesses pay twice.
When you should patch instead of redesign
Patch when one form is broken, one template is slow, one page underperforms, tracking is missing, one integration fails or the mobile navigation misbehaves. A Geelong electrician whose site does its job but whose quote form silently fails on iPhones does not need a $15,000 rebuild. They need a developer for an afternoon.
When a full website redesign makes sense
Redesign when multiple issues overlap: the brand no longer matches, the UX frustrates, the structure describes an old business, the content is weak, technical debt is compounding, mobile struggles, conversion lags across the site and the platform is limiting growth. The strongest single indicator is the pattern where fixing one part repeatedly exposes problems in another, that is the sound of a foundation failing. Platform ceilings show up here too: when the store outgrows what the current setup can do, whether a different platform would remove the ceiling is the first honest question and it is where how we approach ecommerce rebuilds always starts, because migrating a trading store is surgery, not decoration.
A justified redesign is one of the highest leverage investments a business can make. An unjustified one is the most expensive way to change your fonts.
When doing nothing is the right decision
Leave the site alone when leads are strong, customers use it easily, the branding still fits, mobile works, SEO is healthy, editing is manageable, security is maintained and no strategic change is coming. In that position, the marginal dollar almost always works harder elsewhere: a proper organic search program, what Google Ads would cost your business instead, better photography, a CRM, call tracking, sharper sales follow up or simply more reviews. Those investments compound. A cosmetic rebuild of a working site mostly resets things that were fine.
Compare the cost of fixing it with the cost of rebuilding it
Each option trades cost against reach. Doing nothing costs nothing and changes nothing. A patch is cheap with narrow impact. A refresh costs more and mainly moves presentation and messaging. A redesign costs the most and is the only option that solves structural problems. The full sums include more than the invoice: internal staff time, content creation, SEO migration risk, opportunities lost while the project runs, ongoing maintenance and how long each solution actually lasts. What a rebuild would actually cost puts a number on the big option so the comparison is real rather than vibes.
Option | Relative cost | Disruption | Best when | Main risk |
|---|---|---|---|---|
Do nothing | None | None | The site works | A minor improvement goes unmade |
Patch | Low | Low | The issue is isolated | More patches may follow |
Refresh | Medium | Medium | Foundation is sound | Structural issues remain underneath |
Redesign | High | High | Multiple systemic issues | Migration and launch risk |
Patch → Refresh → Redesign
Scope, cost, disruption and potential impact all rise in the same direction. Choose the smallest intervention that genuinely solves the problem.
A redesign also carries risk
Redesigns are sold as pure upside. They are not. Done carelessly, a redesign can drop rankings, break URLs, lose tracking, break forms, delete content that was quietly earning traffic, confuse loyal visitors with new navigation, remove the exact elements that were converting and ship a slower site than the one it replaced. We have inherited more than one rebuild that halved a business's organic traffic in a fortnight.
The protections are unglamorous and non negotiable: record baseline metrics before anything changes, inventory the content, identify the pages earning traffic and protect them, map every redirect, test tracking on the new build and take a backup of the site before touching anything. Then run the project against how to plan a website redesign properly, keep protecting your rankings through a migration beside it if URLs are changing and hold launch until the tests worth running before relaunch day all pass.
Website redesign decision matrix
Common situations, mapped to the framework. Find your situation, note the column and resist the temptation to buy more intervention than the problem needs.
Situation | Patch | Refresh | Redesign |
|---|---|---|---|
One broken form | Yes | ||
Outdated imagery | Yes | ||
Slightly stale branding | Yes | ||
Poor homepage copy | Yes | Yes | |
Entire sitemap no longer fits the business | Yes | ||
Mobile broken across the whole site | Yes | ||
Slow because of a few heavy images | Yes | ||
Slow because of the theme architecture | Yes | ||
Platform limits growth | Yes | ||
Conversion weak on one landing page | Yes | ||
Conversion weak across the site | Yes | Yes | |
Rebrand with the same structure | Yes | ||
Rebrand plus new services plus new audience | Yes |
Healthy → Needs maintenance → Needs refresh → Structurally constrained → Rebuild
The website health spectrum. A healthy site gets monitoring, a maintained site gets patches, a dated site gets a refresh and only a structurally constrained site earns a rebuild.
Common website redesign mistakes
Redesigning because a competitor launched a new site
Their rebuild solved their problems or created new ones you cannot see. Neither is a reason to spend your money.
Redesigning because the owner is bored with it
You see the site every day. Customers see it once. Boredom is the least reliable signal in this entire article.
Redesigning without baseline data
No before means no proof of after and no way to catch what the rebuild quietly broke.
Changing every URL unnecessarily
Every changed URL is a redirect to maintain and equity put at risk. Keep URLs that work.
Treating the redesign as a visual project only
Structure, messaging, speed and conversion paths are the levers. Visuals are the finish.
Replacing good content with shorter modern copy
The long service page ranking for forty terms is an asset. Do not trade it for a headline and three icons.
Ignoring mobile until development
Mobile decided the outcome before the desktop mockup was approved. Design for it first.
Removing pages that generate search traffic
Check Search Console before deleting anything. Quietly performing pages are the easiest things to destroy in a rebuild.
Forgetting tracking
Launch without analytics and conversion tracking and the first month of the new site is a blackout.
Launching without redirects
The single fastest way to convert years of SEO into 404 pages.
Launching without backups
If launch night goes wrong, the backup is the difference between a rollback and a rebuild of the rebuild.
Moving platforms without a business reason
Migrations carry real risk and cost. The developer preferring a different stack is not a business reason.
Patching forever when the foundation is broken
The opposite failure. When every fix exposes the next problem, the patches have become the expensive option.
10 questions to answer before spending the money
1. What problem are we trying to solve?
2. Is it across the whole site or specific to a few pages?
3. What evidence shows the problem exists?
4. Can it be fixed without rebuilding?
5. Does the current platform still suit the business?
6. Will the business change significantly in the next year or two?
7. Which pages currently perform well and must be protected?
8. Which integrations need protecting through any change?
9. What does success look like after launch, in numbers?
10. What happens if we do nothing?
The last question matters enormously. If the honest answer is nothing much for a year, you have found your budget's better use. If the honest answer is we keep losing enquiries every week, the redesign case just wrote itself.
Our honest take: redesigns should be earned by the problem
We like building websites. It is most of what we do all day, for businesses in Melbourne, Sydney, Brisbane and across Australia. And that is exactly why we can say this plainly: not every old website should be replaced. A redesign makes sense when the current site has become an obstacle to growth, sales, marketing, content, usability or operations. When the foundation is still good, a smaller intervention is usually the smarter commercial decision and recommending the smaller intervention is how an agency proves it is advising rather than selling.
Redesign because the website is holding something back, not because the calendar says it is old.
FAQs
How do I know if my website needs a redesign?
Look for structural problems appearing across multiple areas: messaging, mobile, speed, navigation, conversion. Isolated problems get patches. Patterns of problems, backed by data, justify redesigns.
How often should a business website be redesigned?
There is no fixed cycle. The every three years rule benefits agencies, not businesses. Redesign when evidence shows the site is holding the business back, which can be after two years or after eight.
What is the difference between a website refresh and a redesign?
A refresh improves presentation on existing foundations: styling, imagery, copy, proof. A redesign revisits the foundations themselves: strategy, structure, UX, content, development, often the platform.
Can I refresh my website without rebuilding it?
Yes, if the sitemap, platform, mobile behaviour and speed are sound. New typography, imagery, tightened copy and stronger calls to action can transform a structurally healthy site in weeks.
Is an old website bad for SEO?
Age itself is not a ranking problem. Old architecture can be, through slow performance, poor mobile experience, thin structure or technical issues. Diagnose which one you actually have before rebuilding.
Should I redesign if my website is slow?
Diagnose first. Oversized images, poor hosting and plugin bloat are fixable without a rebuild. Redesign when the theme or platform itself is the bottleneck and each fix creates the next problem.
Should I redesign if my website is not generating leads?
Not until you know why. The cause might be one form, one landing page, weak trust signals or the wrong traffic. A rebuild that ships the same weak offer converts just as badly.
How much does a website redesign cost?
For Australian small businesses, targeted refreshes commonly run in the low thousands, while full redesigns typically range from around $5,000 to $40,000 and beyond depending on scope, content and complexity. The framework in this article exists to make sure you buy the right sized intervention.
Can a redesign hurt SEO?
Yes, badly, when URLs change without redirects, performing content is deleted or the new build is slower. Baselines, a content inventory, redirect mapping and staged QA are the protections.
Should I change website platforms during a redesign?
Only with a business reason: a genuine capability gap, unsustainable costs or a platform limiting growth. Migration adds risk and cost and preference alone does not justify it.
What should I measure before redesigning a website?
Organic traffic, conversion rate, lead volume and quality, top performing pages, form completion, speed, Core Web Vitals and indexing. Without the before, nobody can prove the after.
Is it better to patch or rebuild an old WordPress website?
Patch when problems are isolated and the theme is maintainable. Rebuild when the theme is abandoned, plugins conflict, editing is painful and each fix exposes another problem. The crossover is when patching costs more than solving the architecture.
Can I redesign the homepage without changing the whole site?
Yes and it is often the highest value single page project a business can run. Just keep the navigation, URLs and tracking intact so the rest of the site is undisturbed.
When is doing nothing the right option?
When leads are strong, customers navigate easily, mobile works, SEO is healthy and no strategic change is coming. In that position the money works harder in marketing, content or sales.
How long should a business website last?
A well built site on a maintained platform commonly serves five to eight years with refreshes along the way. Sites built desktop first, on abandoned themes or against their platform's grain, age much faster.
Next steps: pick your path
Path 1: run the audit. Twenty minutes, phone in hand, harshest customer hat on. If the problems are isolated, fix them and pocket the difference. Score it honestly before reading anyone's proposal, including ours.
Path 2: the score says refresh or redesign. Gather the evidence first: baselines, top pages, redirect list, backup. Then work through our web design guide for Australian businesses so you scope the intervention, not the wishlist. And when it comes time to pick who builds it, how to choose a web designer without getting burned is the companion piece to this article.
Path 3: get a straight verdict. Send the site to our Melbourne web design team and ask us whether we would patch, refresh or rebuild it and why. Sometimes the answer is a rebuild with a business case attached. Sometimes it is a $600 fix and an awkward silence where the sales pitch was supposed to go. Either way you will know, with reasons.
Sources and further reading
Google Search Central: understanding page experience , Google's documentation confirming Core Web Vitals feed its ranking systems, alongside HTTPS and mobile experience.
Google Search Console , the free tool for seeing indexing, queries, clicks and Core Web Vitals data on your own site.
W3C: Web Content Accessibility Guidelines overview , the international accessibility standard worth asking any designer about.
General information only. Rules vary by situation, particularly around advertising claims, privacy, reviews and consumer law. If you're unsure about compliance, get professional advice.