Redesign, repair, or leave it alone?

Start with the problem, not the age of the site.

There is no useful rule that says a business website expires after a fixed number of years. An older site can still be clear, fast, easy to use, and easy to maintain. A newer site can already be creating problems.

The useful question is simple: what is the current site preventing the business or the customer from doing well?

That diagnosis matters because a redesign is not automatically the most responsible recommendation. Sometimes the best move is to fix the contact path, clean up mobile behavior, repair metadata, improve service pages, or remove technical clutter while leaving the rest alone.

A focused repair is usually enough when...

• The core pages and URL structure still make sense.
• The site already represents the business reasonably well.
• The main problems are isolated: broken forms, weak calls to action, mobile spacing, metadata, performance, or technical cleanup.
• The platform is still maintainable and the business is not fighting it every time something changes.
• Existing search visibility can be improved without reorganizing the whole site.

STATICMETHOD's Website Rescue exists for this category: a live website that needs focused technical and conversion cleanup, not a sales pitch for a full rebuild.

A redesign starts making sense when...

• The company has changed but the website still describes an older version of it.
• Visitors have to work to understand the services, products, audience, or next step.
• The mobile experience technically fits the screen but feels awkward to use.
• Important proof, work, reviews, pricing logic, or business information is buried.
• The site looks credible in pieces but the full customer journey feels inconsistent.
• The content hierarchy has become a patchwork of additions instead of a deliberate structure.

A redesign can preserve good content, URLs, search equity, and working systems. It does not require erasing everything that came before it. That is why a redesign should include a plan for protecting existing search visibility, not only a new visual direction.

A rebuild is justified when the foundation is the problem.

Sometimes the site cannot be meaningfully modernized without replacing major parts of it. That can happen when the platform is abandoned, the theme or codebase is too brittle to maintain, basic accessibility or responsive behavior is difficult to correct, important integrations are unreliable, or the information architecture no longer matches the business.

In that situation, repeatedly patching the old site can become more expensive and more fragile than rebuilding it around the business as it operates now.

Before requesting redesign quotes, document what already works.

A useful redesign brief should not be a list of things you dislike. Make a short inventory of what deserves to survive:

• Pages that already attract useful search traffic.
• URLs people or other websites already link to.
• Forms, automations, analytics, ecommerce, or other systems the business relies on.
• Copy, photography, reviews, project examples, FAQs, and policies that are still accurate.
• Customer paths that already work well.

That gives a designer something more useful than "make it modern." It also reduces the chance that a visual refresh accidentally removes something valuable.

How STATICMETHOD makes the call

The decision starts with the existing website. We look at clarity, credibility, mobile usability, search foundations, conversion paths, and technical friction before deciding how much needs to change.

If you are not sure which category your site falls into, check the website you have first. The goal is to choose the smallest scope that actually solves the business problem.