Stay on WordPress, refresh it, or rebuild
Three answers, and the first one is right more often than anybody selling the third will say.
In short
Stay if the problems are content, speed or a few plugins. Refresh if the structure holds and the design has aged. Rebuild only when the problem is structural: the content model cannot express what you sell, or nothing can be edited without a developer.
Work it out in a minute
Nine questions across revenue, capacity and control. Shows which of the three is costing you most, and where to start.
What we take on
Stay, if it works and it is slow
Slow is nearly always hosting, images and plugins, in that order, and all three are fixable in days without touching the platform. Speed is the most common reason given for a rebuild and the one least likely to need one.
Stay, if the complaint is the content
Pages that do not say the right thing are a writing problem wearing a technology costume. Rebuilding the site around the same words gets you the same result on a newer stack.
Refresh, if the bones are sound
Same structure, same URLs, new design and new copy. Keeps the search history you have already earned, which a rebuild usually spends its first six months winning back.
Rebuild, if you cannot edit it
When a headline change needs a developer, everything downstream slows to their calendar. That compounds, and it is a real reason.
Rebuild, if the content model is wrong
When what you sell will not fit the shapes the site has, you get workarounds in every page and nobody can report on anything. That is structural and no amount of design fixes it.
Rebuild, if the plugin count is the architecture
Thirty plugins holding one business process together is a system with thirty owners and no map. The question there is not WordPress, it is who owns what happens when one updates.
Whatever you pick, keep the URLs
The single most expensive mistake in this whole decision is changing addresses without redirects. It is also the easiest to avoid, and it is where most of the lost traffic after a rebuild comes from.
The honest default is stay
Most sites we look at should not be rebuilt. We say so, and it costs us the larger project, which is exactly why it is worth asking somebody who does not sell only rebuilds.
What a rebuild has to fix to be worth doing
A rebuild is worth its cost when it removes a constraint that is slowing the business down every week, not when it makes the site look current. The test is simple and most proposals fail it: name the thing your team cannot do today, and say how the new site lets them do it. If the answer is about fonts, that is a refresh.
The second test is who can change it afterwards. A site that only its builder can edit has swapped one constraint for another, and in a year you will be having this same conversation about a newer platform. We would rather hand over something your own people can run, and that goal changes what gets built.
The third is what happens to the search you already have. Every URL that changes without a redirect is a page Google has to rediscover and rerank, and the recovery is measured in months rather than weeks. Keeping addresses is unglamorous, it is nearly always possible, and it is where the money quietly goes when it is skipped.
None of this is an argument for or against WordPress. It runs a very large share of the web and it is a reasonable answer for a lot of businesses. It is a poor answer when the site has become a stack of plugins nobody owns, and a good one when somebody in your team can publish a page on a Tuesday without asking anyone.
Questions we get
Is WordPress outdated?
Not in any way that matters to a business. It is mature, which is different, and the weaknesses are usually in how a specific site was built rather than in the platform.
The question worth asking is whether yours is maintained, editable and fast, because a badly built site on a modern stack is worse than a well built one on an old one.
How do we know if it is the plugins?
Count them, then find out which ones a business process depends on. Under ten and well chosen is normal. Thirty, with three doing overlapping jobs, is a maintenance problem rather than a platform problem.
The tell is whether anybody can say what breaks if one is switched off. If nobody can, that is the finding.
What does a refresh actually include?
Same structure and same URLs, with new design, new copy and the speed work. It keeps the search position you already have, which is usually the most valuable thing you own and the easiest to lose.
It is the right answer far more often than it is offered, because it is the smaller project.
If we do rebuild, what should it be built on?
Whatever your team can run after we leave. That is the deciding factor, ahead of anything technical, and it is different for a team with a developer than for one without.
This site is static HTML on a CDN, which suits a site that changes weekly and is read by search engines. That would be the wrong answer for a shop with ten thousand products.
Will we lose our Google rankings?
Only if the URLs change without redirects, and that is avoidable. Plan the address map before anything is built, not after launch when the traffic drops.
Expect some movement for a few weeks even when it is done properly. Expect months if it is not.
Can you just tell us which one we need?
That is the twenty minutes. We look at the site, the plugin list, what your team can edit today and what you are trying to sell, and give you the answer.
You keep it either way, including when the answer is that the site is fine and the problem is somewhere else.
More in the guides and every answer in one place.
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built