Three reasons we hear, almost word for word.
The motivations behind nearly every refresh project.
“My dashboard is full of warnings.”
Old builder, abandoned theme, plugin alerts, PHP nagging, core update blocked.
“I like the site. I do not want to lose it.”
Design, content, SEO rank, team familiarity. A redesign threatens all of it.
“I want to future-proof before the next push.”
Campaign, launch, hosting move, AI work, audit. Better to clear it now.
Not every site needs the same fix.
Pick the path that fits. If you landed on the wrong one, here is where the others live.
Scope, set in writing.
What ships. What does not.
Why Refresh, when a rebuild was quoted?
Both end with a modern site. Only one keeps what you already paid for.
Cost framing is relative. Actual figures depend on site size, builder, and the audit.
What changes, what stays.
The visible site barely moves. Everything holding it up gets brought current.
Layer by layer, brought up to current.
Most refreshes touch more than one layer.
Five steps. Fixed scope. Fixed fee.
Scoped in writing before any work begins.
Audit
We review your current builder, theme, plugins, and content volume. Scope and fixed fee are agreed in writing before any work begins.
Staging clone
A full copy of your site is cloned to a private staging environment. Your live site keeps running untouched throughout.
1:1 rebuild
Page by page, the site is rebuilt on the new builder using the same fonts, colours, layouts, and content. Pixel match is the bar.
Side-by-side QA
Visual diff against the live site, link check, SEO settings carried, custom fields verified, forms tested. You sign off on staging before anything ships.
Cutover
Clean swap on the same URLs, hosting, and admin login, done in a brief planned window. Your team logs in to a modern editor.
Dashboard warnings, cleared.
Site Health goes from red flags to all-clear.
Example. Actual issue counts depend on site age, stack, and starting baseline.
Your live site stays untouched.
Refresh is a backbone swap, not a leap of faith.
All work runs on a private staging clone. Your live site keeps serving visitors untouched.
If anything fails at the swap, we roll back to the existing site in minutes. Same DNS, same hosting.
Posts, pages, media, meta, structured data, and URLs verified one by one before sign-off.