A website problem does not automatically call for a new website. One broken function may need a focused repair. A business that has changed direction may need a different structure altogether.
The useful question is how much of the existing website can still do its job. Decide that before paying to replace it or continuing to patch something that no longer fits.
Describe the problem before choosing the project
“The website feels old” is a reaction, not yet a brief. Name what customers cannot understand or do, and where it happens. If you still need to find the problems, use our checks for an existing business website first.
Bring the resulting examples to the repair-or-redesign discussion. A designer or support provider can assess whether the cause is local to one page, shared across the site, or tied to a wider mismatch with the business.
A focused repair fits a bounded problem
A repair makes sense when the business offer is still represented accurately, the overall page structure remains useful, and the affected part can be changed without rebuilding the surrounding experience.
For example, imagine a repair company whose service pages still explain the right work, but one inquiry button points to an old contact address. Correcting that destination and checking the route is a defined task. Rebuilding every page would need another reason.
Website support is a place to discuss content updates, troubleshooting, and practical improvements. Ask what the proposed fix addresses, how it will be checked, and whether it leaves any related problem unresolved.
A redesign fits a wider change in what the site must do
Consider a fictional business that has moved from selling individual products to providing installation services. Its old site is organized around a product catalog. Customers now need to understand project suitability, the service area, and how an installation inquiry works.
Changing the homepage headline would leave much of that mismatch in place. A redesign may be justified because the page relationships, content, and main customer journey need to change together.
A technical assessment can also identify whether the existing build can reasonably support the required changes. Do not infer that from its age or appearance alone. Ask the person recommending a rebuild to explain what cannot be retained and why.
Compare the work left over after each option
Request a clear description of the repair and redesign options, where both are viable. Compare:
- Which current problems each option resolves.
- Which useful pages and functions can remain.
- Which limitations would still exist afterward.
- What content, decisions, and work your team must contribute.
- What continued upkeep each option requires.
This also makes a phased approach easier to judge. An urgent correction may be worth making while a larger redesign is planned. Ask whether that work will remain useful or be replaced later, so you understand the trade-off.
Choose the scope, then prepare for it
If a redesign is the right direction, our website content checklist covers the material to gather before design begins. Keep that preparation separate from the decision about whether a rebuild is needed.
Send Imbark your website address and the specific problems you want to solve. The next conversation should establish what needs to change, what can stay, and whether custom web design or a smaller piece of work fits.
