When a WordPress theme starts failing, whether it's abandoned, buggy, or just old, you end up at a fork in the road. One path is to keep the theme and fix it, usually by way of a child theme. The other is to rebuild on something modern and move on. Both are legitimate. Both get sold as "obviously the right answer" by people who happen to sell one of them.
Here's how we actually decide, with the questions we ask on every job.
What a child theme fix really is
A child theme is a small theme that sits on top of your existing (parent) theme and overrides only the parts you change. Your customisations live in the child; the parent stays untouched and updatable. It's the mechanism WordPress designed for exactly this.
A "child theme fix" for a broken theme means keeping the parent, then using the child to override the specific templates, functions or styles that are failing: patching a deprecated function call, replacing a template that relies on a dead library, restyling something the block editor changed. The site keeps its look, its content, its structure. You've essentially adopted the theme and started maintaining it yourself.
If the theme is abandoned, "keeping the parent updatable" is moot because there are no updates coming. In that case a child theme is still the cleanest place to put fixes, but you're also free to patch the parent directly. Our main guide on fixing abandoned themes walks through what that looks like.
What a rebuild really is
A rebuild means a new theme, either a well-maintained commercial theme, a block theme, or something custom, with your content migrated across and the design recreated or refreshed. Done well, it's not a redesign unless you want it to be. Done badly, it's a six-week project that ends with a site your customers don't recognise.
The payoff is a clean foundation: current PHP, current WordPress features, no dead dependencies, and a theme that will keep receiving updates without anyone having to hand-patch it.
The five questions that decide it
1. Is the theme fundamentally sound?
Open it up (or have someone do it). A theme that's well organised, uses WordPress conventions, and has one or two things broken by a PHP upgrade is worth patching. A theme with 40 bundled plugins, a custom page builder nobody else uses, and its own copy of jQuery from 2014 is a rebuild candidate no matter how nice it looks.
2. How much of the site depends on theme-specific features?
Some themes are a skin. Others are a platform: custom post types, shortcodes, sliders, a built-in booking system. The more of your content is locked in theme-specific features, the more expensive a rebuild becomes and the more attractive patching looks, at least for now.
3. What's the security picture?
If the theme has known, unpatched vulnerabilities, or it was already compromised while unmaintained, patching has to include a security pass and you should weight the decision toward rebuild. A theme with no history of security problems that simply stopped getting updates is a much safer thing to adopt. We covered why this matters more than it used to in Hacking Is Automated Now.
4. What's the two-year cost, not the this-month cost?
Patching is almost always cheaper today. But every PHP version bump and every major WordPress release is another round of fixes. If the theme is going to need attention every six months, add that up. Sometimes the rebuild is the cheaper option by year two.
5. Do you want a new site anyway?
Be honest. If the design is dated and you've been meaning to refresh it, a rebuild is the natural moment. If the site is fine and you just want it to stop breaking, patch it and put the money elsewhere.
A rough rule of thumb
- Patch (adopt the theme) when: the code is decent, the breakage is a few specific things, the site design still works for you, and there's no security history.
- Child-theme fix when: the parent is still maintained and someone edited it directly. Move the edits, keep the updates.
- Rebuild when: the theme is bloated or built on dead dependencies, it has a security history, or you're going to want a new site within a year anyway.
How we handle this for clients
Every site that comes to us with a failing theme gets the same first step: a proper look at the code and a written verdict. We tell you which of the three options we'd choose and give you a fixed price for it. That assessment is a flat $99, credited toward the fix, so nobody pays for advice twice. If the answer is "patch it", the patch is typically done within a few days. If it's "rebuild", we scope that separately and you decide.
Whatever you choose, do the diagnosis first. The most expensive outcome is rebuilding a site that only needed a twenty-line fix, closely followed by patching a theme that was always going to need replacing.
Next step
Send us the theme. We'll tell you if it's worth saving.
A senior engineer diagnoses your abandoned or broken theme and writes back within one business day: what's wrong, patch or rebuild, and a fixed price. $99, credited toward the fix.