Rescue, refresh, or replace
When a site is not working, the industry's default answer is "rebuild it", because a rebuild is the biggest available invoice. Sometimes that is right. Often it is not, and knowing which is which saves you a great deal of money.
There are three honest options:
- Rescue — the structure is sound, specific things are broken. Days of work.
- Refresh — the foundation is fine, the presentation and content are dated. A couple of weeks.
- Replace — the platform itself is the constraint. Four to six weeks.
Work down them in order and stop at the first one that solves your problem.
Rescue: when the site is fine and something is broken
Signs you are in rescue territory: enquiries dropped suddenly rather than gradually; the site is slow but the layout is fine; forms are not arriving; something broke after an update; you have no tracking.
Typical rescue work is unglamorous and high-return — fixing the contact form, compressing images, installing analytics with real conversion tracking, making the phone number tappable, adding the pricing information that was never there, clearing out plugins nobody uses.
This is where most sites we look at actually belong. A few days of focused work on an existing site frequently outperforms a rebuild, because it fixes the specific things that were losing you work rather than replacing everything and hoping.
Refresh: when it works but looks its age
Signs: it does not look right on phones; the design reads as clearly from another decade; the content describes services you no longer offer; competitors look sharper side by side.
A refresh keeps the platform, the URLs, and the search history, and changes the layer people see — new templates, rewritten copy, real photography, better conversion paths. Because the URLs do not change, there is no ranking risk, which removes the single biggest hazard of a redesign.
The trap is scope creep: a refresh that grows a new booking system, a customer portal, and a migration is a replacement with a refresh's budget, and it will run over. Write down what is in and what is out before starting.
Replace: when the platform is the problem
Genuine reasons to rebuild:
- The site cannot be made fast, because of how it is built rather than what is on it.
- It is on a platform you do not control or cannot export from.
- It has an unfixable security problem, or has been compromised.
- It cannot be edited without a developer, so it never gets updated.
- The business has changed enough that the structure no longer describes what you do.
Note what is not on that list: "it is five years old". Age alone is not a reason. A well-built site from 2019 that loads fast and converts is doing its job.
If you do replace, the two things that decide whether it goes well are redirect mapping — every old URL pointed at its new equivalent before launch — and keeping the content that already earns traffic. Sites lose rankings in redesigns almost entirely through skipping those two steps, and both are preventable.
Modernizing the parts that are not the website
Often the website is the least broken thing. Worth auditing at the same time, and usually cheaper to fix:
- How enquiries are handled. If they land in an inbox nobody owns, no website change will help.
- Your Google Business Profile. For local trades it frequently drives more contact than the website. Incomplete profiles are extremely common.
- Invoicing and payment. Sending a customer a bank transfer request in a text message in 2026 is a modernization opportunity.
- Scheduling. A shared calendar that everyone actually uses removes a category of daily friction.
- Reviews. Nothing on your site persuades like recent, detailed reviews, and asking for them is free.
If budget is tight, some of these return more per dollar than anything on the website itself.
How to decide in an afternoon
- Write down what is actually wrong, in specifics — "the form does not arrive", "it takes eight seconds on my phone", not "it feels dated".
- For each item, ask whether it can be fixed on the current platform. Most can.
- If everything on the list can be fixed in place, you need a rescue or a refresh.
- If two or more items are blocked by the platform itself, you need a replacement.
- If the list is mostly about how it looks, ask whether looks are what is costing you work. Sometimes yes. Often the honest answer is no.
Questions people ask about this
Will I lose my rankings if I rebuild?
Only if the redirects are done badly or not at all. Map every existing URL to its new equivalent before launch, keep the content that earns traffic, and expect a brief unsettled period rather than a collapse. Sites that lose rankings in a redesign almost always skipped the mapping.
Can I rescue a site built by someone I no longer work with?
Usually, provided you can get access to the hosting and the domain. Start the access recovery before anything else — it is the step most likely to take weeks. If a former developer holds the domain and will not release it, there is a formal transfer dispute process through the registrar.
How do I know if my site is genuinely slow?
Load it on your phone on cellular data, logged out, and count. Then run it through a free page speed tool for the specifics. Ignore the score out of a hundred and read the list of what is slow — it is nearly always oversized images, and that is a fix rather than a rebuild.
