One of my most common conversations: “My site is six years old. It’s still fine… right?” Then we open it together on a phone, and I watch the owner’s expression change. Like seeing a photo of yourself from a decade ago: everything familiar, nothing feels right.
The question isn’t whether to do something. It’s what: renovate or rebuild? And that decision is worth real money in both directions.
Five deciding questions
Answer these five honestly and follow the trail:
1. How is the speed?
Run a PageSpeed test. Mobile above 70: the foundation is decent, renovation is viable. Below 50: the problem is likely the foundation itself, and patches only postpone the inevitable.
2. Does it function flawlessly on mobile?
Not “looks okay” - functions: comfortable menu, tappable buttons, fillable forms. If the site was designed when mobile was a “bonus”, renovation usually can’t fix it; that is architecture.
3. How easy is it for you to update?
If every small change means begging someone who vanished, or you’re afraid to touch anything because “last time everything broke”, the foundation no longer serves you.
4. Is the content still right?
Changed services, old prices, photos from 2019. If the problem is mostly content, a focused renovation plus a serious content update may be enough. Content is the cheapest thing to fix.
5. How much have you already spent on patches?
Honest math: what did the fixes cost over the past two years? If the answer approaches the price of a new site, you are paying a mortgage on a collapsing house.
The summary rule: one or two local problems = renovate. Three or more, or any problem touching the foundation (speed, mobile, technology) = a rebuild will be cheaper within two years.
The big fear: “But we’ll lose Google!”
This is the fear that keeps businesses stuck with dying websites, so let’s dismantle it: a well-managed migration does not lose rankings. It usually improves them, because Google receives a faster, sounder site with the same strong content.
The three rules of a safe migration:
- URL mapping: every ranking old page keeps its address on the new site, or gets a permanent (301) redirect to its replacement. No strong page is orphaned.
- Preserve the winning content: check Search Console for the pages bringing traffic, and keep and improve those. You are rebuilding the house, not burning the library.
- A controlled launch: pre-launch checks, submitting the new sitemap to Google, and close monitoring in the first weeks.
That is exactly how we ran a real WordPress-to-static migration you can read about on this blog, before-and-after numbers included.
Bottom line
An aging website is not a failure - it is a natural life cycle: what was built in 2020 met a different internet. The renovate-or-rebuild decision is cold economics (the five questions above), and the fear of losing Google should not paralyze: a managed migration preserves rankings and almost always improves them.
Want an honest diagnosis for your site - renovate, rebuild, or “leave it exactly as is”? Send it over, we’ll tell you the truth ↗