Website Maintenance vs Website Redesign
Maintenance improves or repairs the website that already exists. A redesign changes the site's underlying presentation, architecture or technology more substantially. Choosing correctly can prevent both unnecessary rebuilding and endless patching of a site that has outlived its structure.
How to think about it
Maintenance is usually sensible when the site still reflects the brand, works on modern devices, has a manageable codebase and mainly suffers from outdated content, isolated technical problems or neglected upkeep. Those issues can often be corrected without changing every URL and template.
What businesses should decide
A redesign becomes more reasonable when the information architecture no longer matches the business, core templates cannot support current devices or accessibility needs, the platform is blocking necessary functionality or maintenance repeatedly costs more than fixing the underlying system.
Use the website's actual condition
Generic checklists and package names are useful starting points, but the current website should drive the decision. Review what is working, what is outdated, what creates risk and what the business expects the site to do over the next year.
Request help with an existing website →
Signs maintenance is probably enough
The site still communicates the brand well, important templates work on current devices, navigation remains understandable and the platform can support foreseeable changes. In this situation, fixing content, performance or isolated technical problems can extend the site's useful life.
Signs a redesign deserves consideration
The site may need deeper work when important information cannot fit the existing architecture, core templates consistently fail accessibility or mobile needs, required integrations cannot be supported safely or the visual system materially undermines trust.
A redesign still needs a maintenance plan
Rebuilding does not eliminate ongoing care. The new site will accumulate content changes, software updates and new business requirements too. Decide who owns post-launch maintenance while planning the redesign rather than waiting until the original project team leaves.
Consider the cost of disruption
A redesign can improve a weak site, but it also changes familiar workflows and may affect established URLs, analytics, integrations and search visibility. Those costs are justified when the underlying problems are substantial. They are harder to justify when the main complaint is a handful of outdated pages or fixable visual issues.
Use a staged approach when the answer is unclear
Start with urgent repairs and a short audit. That can reveal whether the site becomes manageable once neglected maintenance is cleared. If deeper structural limitations remain, the findings provide a better brief for redesign. This avoids committing to a rebuild before understanding the existing asset.