Repair your website if the problem is small, clear and sitting on a sound base. Rebuild it if the problems reach into the site's structure, platform, content and daily use. The right choice is the one that removes the cause, not just the symptom.
We hear this question often in website discovery calls. A team may have broken search, forms that no one trusts, old content, slow updates and a design that no longer fits the organisation. They want to know if a few fixes will buy more life, or if that money would be better put towards a new site.
There is no rule based on age alone. A five-year-old site may still have a strong base. A newer site may already be hard to use or built around the wrong goals. Start with evidence, not the launch date.
Start with the job your website must do
Before you list faults, state the job of the site in one sentence. It might need to help families compare a school, help donors trust a charity, help buyers find products, or help referred clients check that a firm is right for them.
Then name the main users and the actions they need to take. This matters because a working site can still be the wrong site. In our calls, we often find that the organisation has changed while the website has not. New audiences have appeared. Two sites now repeat the same content. A simple brochure site has become a store, resource library or lead tool.
If the job has changed in a major way, a rebuild is more likely. If the job is still right and one part is failing, repair may be enough.
Use the six-part decision framework
1. Check the size of the problem
List each issue and group it under design, content, navigation, technology, search, forms, speed, accessibility and editing. Our beginner's website audit guide can help you run this check.
A repair suits one or two contained faults, such as a broken form, a poor page layout or an unclear menu label. A rebuild becomes more likely when the same issue appears across many page types, or when several systems fail together.
2. Test the foundation
Ask a developer to check the code, content system, hosting, plugins, integrations and mobile behaviour. You need to know if the site can accept safe changes without causing new faults.
Do not rebuild just because the site uses a certain platform. Platform choice must fit the team and the site's needs. The warning sign is a fragile setup that takes too much effort to update, patch or extend. We often meet small marketing teams that avoid simple changes because they fear breaking something. That is a business cost, even when the site looks fine to visitors.
3. Check the content model
A content model is the way items such as people, products, services, news and locations are stored and linked. A good model lets the team update an item once and use it in the right places.
In discovery, we have seen teams post the same news on two sites, manage large product lists by hand, or hide useful details inside pop-ups that cannot be shared as pages. These are not only design faults. They point to a structure that may need to be rebuilt.
Repair is still possible if the content types are sound and only need a cleaner template, better filters or a simpler editing flow.
4. Count the cost of keeping the site
Look beyond the quote for the next fix. Add the staff time spent on repeated entry, support calls, manual work, failed forms and workarounds. Add the risk of missed enquiries or users who cannot find what they need.
Now compare that total with the useful life of the repair. If a fix solves a known problem for a few years, it may be good value. If it only holds the site together until another planned change, treat it as a bridge and limit the scope.
5. Check what must change next
List the work expected in the next 12 to 24 months. This may include a brand update, new services, a new customer system, online sales, more languages or a merged site.
A repair makes little sense if you will soon replace the same page templates, navigation or platform. A rebuild can be the safer choice when the planned change touches the whole site. If the roadmap is light, a repair may avoid work you do not need.
6. Check whether your team can run it
The site must work for visitors and the people who keep it current. Ask the staff who publish content to show you their normal tasks. Watch where they copy information, leave fields blank, keep side spreadsheets or ask a developer for help.
A new site should reduce that load. It should also have clear owners and rules after launch. Our guide to website governance explains how to keep content, design and measurement on track.
When a repair is the better choice
- The website still serves the right users and goals.
- The site structure and content types are sound.
- The faults are limited and can be tested after the fix.
- The platform is secure, supported and practical for your team.
- No major brand, service or system change is close.
- The repair has a clear life and does not block later work.
Set a fixed scope, success measure and stop point. For example, repair search so users can find known items, then test it with real terms. Do not let a small job grow into a slow rebuild with no shared plan.
When a rebuild is the better choice
- The website's role or main audience has changed.
- Navigation, search and content structure fail across the site.
- Several sites or tools repeat the same work.
- Simple updates take too long or need specialist help.
- The base is fragile, hard to support or costly to extend.
- Planned changes affect most templates or systems.
A rebuild does not mean throwing away everything. Useful copy, images, data and lessons can move across. The current sitemap may also be a useful starting point, even if it needs work. See our UX and UI website checklist for areas to test during planning.
Use a repair as a bridge when needed
Sometimes the site needs help now, but the organisation is not ready for a rebuild. In that case, fix the issues that affect access, trust, security, enquiries or sales. Leave cosmetic changes and large new features for the planned project.
Write down what the bridge repair must achieve and when you will review it. This keeps urgent work useful and stops it from becoming an open-ended spend on an old plan.
Make the decision with evidence
Run an audit, speak to users, review analytics, test key tasks and map the team's editing process. Then score each of the six areas as healthy, strained or failing. Mostly healthy points to repair. Several failing areas, especially foundation and structure, point to rebuild.
You can explore IGNITE's website capabilities and recent work to see how strategy, design and development fit together. If you want a clear view of your current site before you spend, contact IGNITE. We can help you define the smallest repair that will work, or the rebuild that will remove the problem for good.