marumba insightsARTICLES & ANSWERS

Web Development

Redesign or Rescue? Judge your aging site.

A five-question test: refresh, repair or replace.

Redesign or Rescue? How to Judge an Aging Website

By Todd Sullivan · November 15, 2026 · 8 min read

The short answer: rebuild only when the foundation is the problem. If the platform is still supported, the content still fits the business and the site can be measured and maintained, repair or refresh it. If the platform is unsupported, the site cannot be edited safely or the business has fundamentally changed, a rebuild is worth the cost. Most aging sites fall in the middle, and most of those are better served by a rescue first.

Three options, not two

Rescue: fix what is broken

Update software, patch security holes, repair forms, fix speed and mobile problems, clean up redirects and tracking, restore backups and documentation. The look and structure stay. Best when the site mostly works but has accumulated neglect.

Refresh: new front end, same engine

Redesign the templates, navigation and content on the existing platform. Best when the platform is healthy and supported, but the design, messaging or user experience are dated.

Rebuild: new platform and structure

Start over with a new technology, information architecture and design. Best when the current platform is end-of-life, the code cannot be maintained, or the business needs capabilities the old site cannot support.

The five-question test

  1. Is the software still supported? Check your CMS, framework, server runtime and plugins. If any core piece no longer receives security updates, you carry real risk, and that points toward a rebuild or at least a platform migration.
  2. Does the site do its job? Look at leads, calls and sales over the past year. If the site produces results and visitors can complete key tasks, a full rebuild is hard to justify.
  3. Is the content still right? Services, pricing, team, locations and messaging should match the business today. If they do not, the problem is partly editorial, and a new template will not fix it.
  4. Can you measure and edit it? If analytics are missing, forms are unreliable or every change requires a specialist and a weekend, maintenance costs will keep climbing.
  5. Is the experience acceptable on a phone and for everyone? Check speed, layout, readability and accessibility. These are usually fixable, but severe problems across the board suggest the underlying structure is dated.

Mostly yes: repair or refresh. Mostly no, especially on questions one and four: plan a rebuild.

What it means when software is "unsupported"

Every platform has a lifecycle: current releases get features and fixes, older ones get security fixes only, and eventually support ends. After that date, newly discovered vulnerabilities simply never get patched. This is not a theoretical risk. Security firm Censys found that more than 70% of publicly reachable WordPress sites with visible PHP version data were running PHP versions past end of life, and that PHP 7.4, which stopped receiving security fixes in November 2022, was still the most common version, on over 20% of sites (Censys). Owners often update the CMS dashboard and never touch the server runtime underneath it.

The same applies to any stack, including ColdFusion, .NET and Java. Look up your runtime, framework and CMS on the vendor's lifecycle page, write down the end-of-support dates and put them on a calendar. Plugins deserve their own check: a plugin that has not been updated in a year or more, or whose author has disappeared, is a liability even if everything else is current.

A 30-minute self-check

  1. Find your versions. Look up the CMS version, server runtime version and the list of plugins or extensions.
  2. Check the dates. Is each one still supported? When was each plugin last updated?
  3. Test the money paths. Submit your own contact form, make a test booking or purchase, and confirm the notification arrives.
  4. Run a speed and mobile test. Google's PageSpeed Insights is free and shows specific fixes.
  5. Check search health. Open Search Console and look for indexing errors, security warnings and manual actions.
  6. Confirm the basics. HTTPS works everywhere, the certificate is current and backups exist and can be restored.

If steps one and two turn up end-of-life software and step three finds a broken form, you have your answer before spending anything.

Red flags that point toward a rebuild

  • The server software or CMS version is past end of life.
  • The site was built on a plugin or theme the author no longer updates.
  • No one has a working copy of the source code or the hosting credentials.
  • Pages are built with tables, Flash remnants or inline scripts that modern browsers handle poorly.
  • You cannot add a page or fix a typo without breaking something.
  • The site cannot be made accessible or mobile-friendly without rewriting most of it.

Red flags that point toward a rescue instead

  • The platform is current but updates have been skipped.
  • The site loads slowly mainly because of oversized images or unneeded scripts.
  • The design looks dated, but navigation and content are sound.
  • Forms or email notifications have stopped working.
  • Analytics were never configured properly.

Three illustrative scenarios

These are composites meant to show how the decision plays out, not real clients.

  • The neglected but sound site. A contractor's WordPress site is two years behind on updates, loads in six seconds because of oversized photos and has a contact form that silently fails. The structure and content are fine. Rescue: update, compress images, fix the form, add monitoring and backups.
  • The healthy site with a dated look. A law firm's site runs on a current, supported platform with strong rankings, but the design reads as ten years old and the mobile layout is cramped. Refresh: new templates and clearer service pages, same URLs and platform.
  • The site nobody can safely change. A distributor's site runs on a custom platform whose original developer is gone, the runtime is past end of life and adding a product page breaks the navigation. Rebuild: a new platform with a redirect plan so existing rankings carry over.

The cost of waiting, and the cost of rebuilding

Waiting has a price: unpatched software invites attacks, slow pages lose visitors and a dated site can cost you credibility before anyone reads a word. Rebuilding has a price too. Every redesign risks search visibility if URLs, titles and content are mishandled, and migrations take time and attention away from running the business. A well-run migration protects your rankings (we walk through how in Migrating a Website Without Losing Your Rankings), but it takes planning.

Decide on outcomes, not taste

A redesign driven by "it looks old" tends to disappoint. A project driven by a specific goal tends to succeed: more qualified leads, faster response time, easier updates, lower maintenance cost, compliance with accessibility standards. Write down two or three measurable goals before talking to any developer, and judge every proposal against them.

What to gather before you talk to a developer

  • Login access to hosting, domain registrar and any CMS or admin area.
  • A list of what the site is supposed to do (leads, sales, bookings, information).
  • Twelve months of traffic and conversion numbers, if you have them.
  • The top 10 pages by traffic and any pages you must not lose.
  • A list of integrations: payment, email, CRM, scheduling, inventory.
  • Three sites you like, and one you do not, with a sentence about why.

What drives cost and timeline

Rather than quote ranges that vary widely, it helps to know what moves the number:

  • Page and template count. Forty similar pages are far cheaper than forty unique layouts.
  • Content work. Writing, photography and migrating existing copy often take longer than the design itself.
  • Integrations. Payments, CRM, scheduling and inventory connections add testing and risk.
  • Custom functionality. Portals, calculators and member areas cost more than brochure pages.
  • Approvals. The biggest timeline variable is usually how quickly feedback and content arrive.
  • Migration care. Redirect mapping and testing take hours but protect traffic worth far more.

Rescues are usually the shortest and most predictable. Rebuilds take the longest because of content and approvals, not code.

Questions to ask any developer

  • What exactly is wrong with the current site, and how did you find out?
  • What would you keep, and what would you replace?
  • How will you protect existing search rankings and tracking?
  • Who owns the code, the content and the accounts when the project ends?
  • What does ongoing maintenance cost, and what does it include?
  • How will we know it worked? Which numbers will we compare, and when?

A simple decision rule

If a developer can inspect the site and give you a short written list of what is broken, what it will cost to fix and what it will cost to replace, you can compare the two honestly. If anyone proposes a rebuild without examining what you have, or a rescue without testing whether the foundation holds, get a second opinion.

Quick answers

How often should a business site be redesigned?

There is no fixed schedule. Many sites go several years between major redesigns if they are maintained and improved continuously. Redesign when goals change or the foundation ages, not because a calendar says so.

Will a redesign hurt my rankings?

It can if URLs, titles and content are mishandled. It need not if the migration is planned, which is why the redirect map matters as much as the design.

Is a rescue just a temporary patch?

Not if the foundation is sound. A rescue that updates software, fixes performance and sets up monitoring and backups can keep a site healthy for years.

Sources

Want help with this?

Tell us what you are working on and we will point you in the right direction.

Call Get a quote