A website redesign is worthwhile when the site no longer supports the way your business sells, serves customers or gets found online. But a dated colour palette alone isn't a reason to rebuild everything. Some sites need focused repairs. Others need a new design on the existing platform. A smaller group need a full rebuild because the structure, technology or content has become the problem.
The right decision starts with evidence: mobile usability, enquiries, page speed, search performance, content accuracy and how easily your team can update the site. This guide helps you choose between a repair, a redesign and a rebuild without throwing away pages or rankings that still have value.
Repair, redesign or rebuild: what is the difference?
These terms are often used as if they mean the same thing. They don't. The scope changes the budget, timeline and amount of risk you take on.
| Option | What changes | Best fit | Main risk |
|---|---|---|---|
| Repair | Specific faults such as broken forms, slow pages, layout problems, outdated plugins or incorrect content | The site structure still works and only a limited set of issues is hurting performance | Repeated patches can become expensive if the underlying platform is already failing |
| Redesign | Visual system, page layouts, navigation, calls to action and selected content, usually on the current platform | The technology is serviceable, but the experience no longer matches the business or its customers | Changing layouts without protecting content and URLs can damage search visibility |
| Rebuild | Platform, templates, structure, integrations and front-end experience | The current site is difficult to manage, insecure, structurally weak or unable to support required features | A rushed migration can lose content, tracking, redirects and working functionality |
A sensible website redesign service should diagnose the site before proposing the biggest possible project. If a form fix and a clearer service page solve the real problem, a full rebuild is wasteful. If the site cannot be updated safely or doesn't work properly on mobile, another cosmetic patch won't fix it.
Signs your business website needs more than a cosmetic update
Customers struggle to complete important tasks
Start with the actions that matter to the business. Can a visitor understand what you offer, find the right service, request a quote, call you or complete checkout without getting stuck? Test these journeys on an ordinary mobile connection, not only on a designer's large desktop screen.
A redesign becomes urgent when navigation hides important pages, forms fail, buttons are hard to tap, or the next step is unclear. These are commercial problems, not design preferences.
The site no longer reflects the business
Businesses change faster than websites. You may have added services, entered new areas, changed your ideal customer or stopped offering something that still dominates the homepage. If visitors regularly ask questions the website should answer, the information architecture and message need attention.
Don't solve this by adding more menu items to an already confusing structure. Map the current offer, decide which pages support real buyer questions, and remove duplication before designing new layouts.
Mobile visitors get a second-rate experience
A site can technically be “responsive” and still be unpleasant to use. Watch for oversized banners, text that becomes tiny, horizontal scrolling, pop-ups that block the page, slow image-heavy sections and forms that require too much typing.
Mobile review should cover the full journey, including menus, quote forms, maps, payment steps and confirmation messages. A clean homepage means little if the enquiry form breaks on a phone.
For a South African redesign, don't treat a fast office fibre test as proof that the mobile experience is good. Test priority pages on a throttled mobile profile and a modest phone, then reduce image weight, scripts and form steps where they delay the next action. South Africa has extensive 3G and 4G/LTE coverage, but the practical redesign question is whether a customer can still load the page and send an enquiry under the connection and device conditions they actually use.
Your team avoids updating the website
If a small text change requires a developer every time, staff will postpone updates. Old prices, staff details, opening hours and service information then remain live because the content system is too fragile or confusing.
A rebuild may be justified when the current platform is unsupported, heavily customised without documentation, or dependent on components that can no longer be updated safely. If the platform is sound, better templates, permissions and training may be enough.
Traffic arrives but enquiries do not
Low conversions do not automatically prove the design is bad. The traffic may be irrelevant, the offer may be unclear, or visitors may not trust the proof on the page. Review search queries, landing pages, form completions, calls and other lead actions together.
Redesign the path to enquiry only after identifying where people drop out. Otherwise, you can launch a better-looking website with exactly the same sales problem.
Maintenance has turned into recurring emergency work
Frequent plugin conflicts, broken layouts, malware clean-ups or unexplained downtime are signs that the site's technical debt needs a proper assessment. Allanux's website maintenance and WordPress redesign service covers the operational side of this decision, including updates, backups, security checks and redesign work for WordPress websites.
The important distinction is whether routine maintenance can restore a stable baseline. If every update breaks another component, planning a controlled rebuild is usually safer than continuing with isolated fixes.
Audit the evidence before approving a redesign
A redesign brief should begin with what the current website does well and where it fails. That prevents the project from becoming a subjective debate about colours and competitors.
- Business goals: Identify the main actions the website must generate, such as quote requests, bookings, calls, purchases or support enquiries.
- Analytics: Review useful landing pages, device mix, conversion events and paths that lead to enquiries. Treat bounce or engagement metrics as clues, not verdicts.
- Search data: Export pages and queries from Google Search Console. Mark pages that already earn impressions, clicks or useful rankings so they are protected.
- Content: Check accuracy, duplicated pages, missing service detail, outdated proof and questions sales staff answer repeatedly.
- Technical health: Test speed, mobile behaviour, forms, tracking, backups, updates, security and third-party integrations.
- POPIA and lead data: List every form and the personal information it collects, why it is needed, where it is sent, who can access it and which suppliers process it. The redesign must carry the relevant collection notice and reasonable security safeguards into the new form and CRM flow; a prettier form does not reset the business's POPIA responsibilities.
- Ownership: Confirm who controls the domain, hosting, analytics, Search Console, website admin and licensed software before work begins. For a
.co.zadomain, verify that the business's registrant details are current and that it can access the registrar account and transfer process. ZADNA describes registration as a continuing right to use the name while it is kept current, not outright ownership.
If the current site still attracts useful searches, don't discard it. Preserve the pages and language that work, then improve the experience around them. A redesign should build on evidence, not reset years of accumulated search value.
How to protect SEO during a website redesign
The safest redesign keeps every valuable URL unchanged. When a URL must change for a valid reason, map the old page to the closest relevant new page with a permanent redirect. Sending every removed URL to the homepage is not a proper migration plan.
- Crawl and export the current site. Record live URLs, titles, headings, canonicals, status codes, internal links and indexable pages.
- Combine that inventory with Search Console data. Flag pages with clicks, impressions, backlinks or conversions.
- Create a one-to-one URL map. Keep existing routes where possible. Document redirects before launch, not after traffic drops.
- Move useful content intentionally. A shorter page isn't automatically better. Preserve explanations, proof and answers that match real searches.
- Keep internal links accurate. Update menus and in-body links to point directly to final URLs rather than relying on redirect chains.
- Test metadata and indexing controls. Check titles, descriptions, canonicals, robots directives and the XML sitemap on the finished build.
- Verify tracking and forms. A launch is not complete until analytics, Search Console, call links, forms and thank-you events work.
- Monitor after launch. Watch crawl errors, indexed pages, queries, conversions and server logs closely enough to catch migration defects early.
If a provider cannot explain how URLs, redirects and tracking will be handled, the project isn't implementation-ready. Allanux's web design and development service is the primary commercial next step for a scoped redesign or rebuild discussion.
What a useful website redesign brief should contain
A short, specific brief saves more time than a folder full of design references. It should state the business problem, users, required actions and constraints.
- The reason for the project and the result the business needs
- Primary audiences and the questions each audience must answer
- Required pages, content owners and approval responsibilities
- Forms, payments, bookings, CRM, email or other integrations
- Existing URLs that must remain stable
- Content, images and brand assets that will be reused or replaced
- Accessibility, mobile, speed, security and backup expectations
- Testing, launch, training and post-launch support responsibilities
For a smaller company site, start with the customer journey rather than a long feature list. Allanux's business website design service shows the natural commercial route when the current site needs a clearer lead-generation structure.
Questions to ask before choosing a redesign provider
Ask how the provider will decide what to keep. A capable answer should cover analytics, Search Console, content, URLs, functionality and buyer journeys—not just visual references.
- Will you audit the current website before proposing the new structure?
- Who writes, migrates and approves the content?
- How will existing URLs and search-performing pages be protected?
- What happens to forms, analytics, integrations and email delivery?
- What is included in testing and what counts as a revision?
- Who owns the domain, website, content and accounts after launch?
- Where will form submissions be stored, who can access them, and what POPIA notice and safeguards will apply?
- What maintenance is needed after the project?
Be cautious when a quote is based only on the number of pages. Two five-page websites can require very different work if one includes content migration, bookings, custom forms or search-risk management. Scope must reflect what the site needs to do.
