Skip to content

Updates9 min

When is it worth updating an old WordPress site?

Update when yearly patching costs more than a clear project, or when mobile UX, editing, speed, and security all hurt at once. We protect SEO with a URL map and 301s. Price by scope + VAT.

In short

  • Signals: slow mobile, painful editing, security risk
  • If yearly patching costs more than a project. Update
  • Preserve SEO with 301s and a URL map
  • Start with a short audit and a clear quote + VAT
  • An update is more than a new theme

Signals it’s time

Broken mobile UX, painful editing, slow conversions, outdated theme, scary updates. That’s business friction, not cosmetics. Old WordPress often “works” until a critical form or payment breaks.

If you spend more in a year patching than a clear update project would cost, the numbers already argue for a redesign or a healthier foundation.

Patching vs structural update

Patching fits when the problem is local: one plugin, one slow page, one form. A structural update fits when navigation, content model, mobile UX, and brand all hurt at once.

Updating doesn’t mean throwing everything away. We often keep content, URL logic, and what converts, and change what blocks you.

How to protect SEO during migration

We plan a URL map, 301 redirects, check canonicals and indexing, and watch Google Search Console after launch. The goal is a better experience without “missing” pages.

Without a map, even a beautiful redesign can tank organic traffic for weeks. SEO preservation is part of the project, not an afterthought.

Content and editing experience

A good update makes your team’s work easier: clear blocks, fewer “don’t touch” zones, faster new pages. That cuts dependency on an agency for every sentence.

If nobody can edit after launch, the project isn’t finished. Training and documentation are part of success.

Where to start

A short audit: what works, what must be kept, where a new structure pays back fastest. Then a quote without surprises + VAT and stages (MVP → growth).

If you’re unsure, Get in touch: often thirty minutes is enough to say clearly “keep patching” or “time to update”.

End

FAQ.

How do we know it’s time to update, not keep patching?

If yearly patching costs more than a clear project, or mobile UX, editing, speed, and security all hurt at once. A local issue (one plugin, one form) can still be a patch.

Will we lose Google rankings during an update?

We plan a URL map and 301 redirects. Short-term swings are possible, but the goal is to keep and later improve visibility. Without a map, risk is much higher.

How much does a WordPress update cost?

By scope + VAT: from homepage + contacts to a full redesign with migration. We quote after a short call and a look at the current site.

How long does an update take?

Often a few weeks to a few months, depending on pages, products, and custom features. We put the timeline in the quote. We often work in stages so the business doesn’t stall.

Do we need to change the domain?

No. Most updates stay on the same domain. We change the domain only for a separate reason. What matters more: the URL map and 301s.

Next article

A cookie banner that blocks nothing: what we found and what we fixed