Real 84EM email is only @84em.com

WordPress Repair vs Rebuild: How to Decide

Repair when the foundation is sound; rebuild when code debt and security make fixing cost more than starting clean. How to decide.

> ls ./guides/wordpress-project-rescue/

> Inheriting a Site

> Hacked Site

> Repair vs. Rebuild

> Stalled Project

> Post-Rescue

Should you repair or rebuild?

Repair when the damage is contained and the underlying foundation (the theme, the architecture, the core structure) is sound. Rebuild when the foundation itself is the problem: a page builder that’s outgrown its usefulness, years of accumulated code debt, or a security posture so compromised that fixing it piece by piece costs more than starting clean.

When repair is the right call

If a site’s core architecture is solid and the problems are contained, specific bugs, isolated security findings, particular broken features, repair is faster and cheaper, and it preserves everything that’s already working. Most WordPress problems fall into this category: something specific is wrong, not everything.

When rebuild pays for itself

Rebuild starts making sense once the foundation itself is what’s holding the site back. A page builder that’s made the site slow and hard to maintain, a codebase so tangled that safely changing one thing risks breaking another, or security vulnerabilities deep enough that patching them one at a time never actually catches up, these are foundation problems, not surface problems, and no amount of careful repair fixes a foundation that’s fundamentally wrong for what the site needs to do.

Migrating content and preserving SEO

A rebuild’s biggest hidden risk isn’t the new build, it’s losing what the old site had already earned: rankings, indexed pages, and inbound links. Preserving that means careful URL mapping and redirects from old paths to new ones, not just standing up a new site and hoping search engines figure it out. Skipping this step is how a rebuild that improves the site technically still costs the business real traffic.

Real example

84EM rebuilt a financial services company’s marketing site from a slow, hard-to-maintain page builder into a hand-built custom WordPress block theme, earning a perfect mobile performance score while giving the client’s team the ability to edit content directly without risking the layout. For an online bank locked out of routine updates by its existing site, 84EM also rebuilt the platform to give the editorial team full control over layouts and audience-targeted content without needing a developer for routine changes.

See inheriting a broken or legacy WordPress site if you’re still assessing which way an inherited site should go.

Talk to 84EM about a WordPress repair or rebuild once you know which one your site actually needs.

Let's Talk

Direct access to the senior engineer who scopes, builds, and ships your project. No one in between.

Folks We've Helped