A lot of businesses ask the wrong first question about an old website. They ask, “Should we rebuild it?” The better question is, “What is actually broken?” Some sites only need cleanup, faster code, or better content structure. Others are held together so badly that patching them costs more than replacing them. The goal is to make a sensible call early, before you spend time and money fixing the wrong thing.

Start with the thing that is failing

Do not begin with design opinions. Begin with the problem you can point to. Is the site slow? Hard to update? Missing pages? Not showing up in search? Not connected to the tools you use every day?

A repair makes sense when one part is broken and the rest still works. A rebuild makes sense when the whole site is fighting you: the layout is rigid, changes are risky, and the structure no longer matches the business.

Signs a fix is probably enough

A fix is usually the right move if the site still fits the business and only a few things are off. For example: the pages are mostly right, but the mobile layout needs work; the content is fine, but the loading time is poor; or the site has weak metadata and internal linking, so search engines have a hard time reading it.

In those cases, you can often keep the existing site and improve what matters most. That may mean cleaning up the page structure, improving speed, fixing accessibility issues, tightening the copy, or connecting the site to a booking form, CRM, or other tool it should already talk to.

Signs a rebuild is the better call

A rebuild starts to make more sense when the site is built around the wrong shape of business. Maybe it was made as a quick template and never grew with the company. Maybe every change needs a developer because the content model was never planned well. Maybe the site looks fine on the surface, but under the hood it is slow, messy, and hard to extend.

A rebuild is also worth serious thought when you need things the current setup cannot support well: a better CMS, custom page types, integrations, customer login areas, or a structure that is meant to grow instead of being patched forever.

Ask one simple cost question

The real test is not “Can we fix it?” It is “How much time will this keep taking every time we touch it?”

If each new change creates another round of work, another workaround, or another risk of breaking something else, the site is already expensive. At that point, a clean rebuild can be the cheaper path because it removes future drag instead of just covering up the current problem.

A practical way to decide

You can sort most cases with four checks. First, list what is broken. Second, note how often it breaks. Third, ask whether the issue sits in the design, the content, the code, or the underlying structure. Fourth, decide whether the current site can grow into what you need next.

If the answer is mostly “yes,” fix it. If the answer is mostly “no,” rebuild it. A good studio should be able to tell you which side of that line you are on, and say no to a rebuild if a repair is the smarter move.

What to do next if you are unsure

Bring the problem, not a preset solution. A clear conversation about what is in the way is usually enough to tell whether you need a repair, a partial rebuild, or a fresh start.

If you are comparing options, look for someone who will audit what already exists, keep what still works, and replace only what does not. That approach avoids waste and makes it easier to choose the smallest build that actually solves the problem.