When it's time to replace an old website

Age alone is not the issue. Plenty of simple five-year-old sites still work because they are clear, fast enough, usable on phones, and accurate. The question is whether the site still matches the business and how people use the web now. Not whether a designer is bored of the colors.

Strong reasons to replace (or rebuild)

Mobile is broken or embarrassing. If staff avoid sending the link, or you cannot complete a call action on your own phone, that is rebuild-level. Not a tweak.

You cannot update it. No access. Dead vendor. Page builder nobody understands. “We have to call a guy who moved to Florida.” A storefront you cannot reprice will rot.

Contact paths fail. Forms that do not deliver. Old phone numbers. Maps to a previous address. Mailto links that bounce. Revenue leaks.

It actively misrepresents you. Services you dropped. Prices that start fights. Brand from a previous owner. Photos of a building you left.

Technology risk is high. Old CMS versions with abandoned plugins. Repeating malware cleanups. Host that cannot keep TLS current. Emergency mode costs more than a clean rebuild.

The business outgrew the site. One location became three. Appointments became online ordering. A side product became the main revenue line. Stretching the old structure confuses customers.

Weaker reasons (often fixable without full replacement)

• “I am bored of the colors” while content is still accurate
• A few outdated photos (swap them)
• Missing one service paragraph (add a page)
• Wanting a blog someday (can wait)
• A competitor redesigned (react with a plan, not panic)

Sometimes a content and speed sprint saves the foundation. Sometimes polishing a bad foundation wastes money.

Decision questions

1. Can a stranger on a phone understand us and contact us in under a minute?
2. Can we change hours this week without heroics?
3. Does the site match how we actually operate?
4. Are we proud enough to put the URL on the truck and the invoice?
5. How many workarounds are staff inventing (“just message me on Facebook”)?

If you are saying no more than once, dig deeper with a structured review. See What we look at when we review a site.

Rebuild vs refresh

Refresh: same bones, new layout/content/photo pass, speed cleanup. Works when structure is sound and tools are maintainable.

Rebuild: new structure, cleaner build, hosting you control, content rewritten against current business truths. Works when the old platform or page structure is the problem.

Be wary of “redesigns” that only change the skin while broken forms and uneditable guts stay.

Timing

Do not launch a new site the morning of your busiest weekend without a plan. For seasonal businesses, finish testing before the rush. Have redirects ready if URLs change so Google and bookmarks do not fall into holes.

How we help

We will tell you when a refresh is enough and when a replacement saves money long-term. The goal is not novelty. It is a site you can maintain that matches the business customers meet in real life.