Short answer: Repair when the structure is sound and the problems are isolated; redesign when ownership, architecture, content, or maintainability blocks progress.
Begin with evidence, not appearance
An older visual style does not automatically require a rebuild. A modern-looking site can still have weak content, inaccessible controls, slow pages, broken forms, or unclear ownership. Start with the business outcome and inspect the existing foundation.
Repair-versus-redesign scorecard
| Area | Repair is usually sensible when… | Redesign or rebuild is more likely when… |
|---|---|---|
| Performance | A few large assets or scripts cause the problem | The platform and theme make every page slow |
| Accessibility | Issues are isolated and templates are sound | Navigation, forms, contrast, and semantics fail across templates |
| Content | Facts are current and only structure needs adjustment | Services, audience, languages, and messages have changed substantially |
| Search | Titles, links, and individual pages can be corrected | Important topics have no suitable page structure or migration history is unclear |
| Technology | Supported software and accounts are under your control | Unsupported plugins, unknown code, or provider lock-in prevent safe maintenance |
| Operations | Forms and updates work with small corrections | The site cannot support required booking, inquiry, payment, or editorial workflows |
Repair when the foundation is sound
A repair project can improve navigation, rewrite priority pages, correct technical SEO, optimise images, fix forms, and establish updates without replacing everything. This reduces migration risk and can produce value faster.
Before choosing repair, confirm that the business controls the domain, hosting, source or CMS access, analytics, and backups. Confirm that the platform still receives security updates and that someone can maintain it after the project.
Redesign when the structure blocks progress
A redesign is justified when the site serves the wrong audience, cannot represent the current services, uses an unsupported platform, repeatedly breaks, or requires more effort to change than a controlled rebuild. It can also be necessary when multilingual content, accessibility, performance, or integration requirements cannot be implemented reliably in the existing templates.
Do not forget migration
A new site is not finished when the new pages look correct. The migration plan must include:
- an inventory of existing indexable URLs;
- a mapping from every valuable old URL to its new destination;
- preservation of useful page titles, content, and inbound links;
- redirects, canonical URLs, sitemap, robots, and analytics checks;
- form, booking, consent, and legal-page testing;
- a rollback and backup plan;
- post-launch monitoring in Google Search Console and Bing Webmaster Tools.
Make the decision in two stages
First run a bounded audit that identifies business, content, accessibility, performance, search, and technology problems. Then estimate the smallest repair and the smallest responsible rebuild against the same acceptance criteria. Choose the option with the lower total risk and ownership cost—not automatically the lower initial price.