How to Repair a Broken WordPress Site
Your WordPress site is broken — errors, a blank page, weird behavior, or a mess after updates — and you need a sensible order of operations, not fifty conflicting forum posts.
Common signs of this issue
- The site shows an error ("critical error," white screen, 500, database connection) instead of pages.
- The site loads but looks wrong — broken layout, missing images, styles gone.
- The admin area is unreachable, or logging in leads to loops and errors.
- Things half-work: some pages fine, others broken, forms dead, checkout failing.
- It broke after a specific event — an update, a migration, a new plugin, or a hosting change.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- First, name the symptom precisely. "Broken" isn't diagnosable; "critical error message after updating plugins Tuesday" is. Write down what visitors see, what you see in admin, and when it started.
- Identify the trigger: check your email for auto-update notices, and think through the last 48 hours — updates, new plugins, host maintenance, PHP changes, expired cards on hosting bills.
- Locate your backups before touching anything. Check your backup plugin's schedule actually ran, and ask your host what they keep. Knowing a restore point exists changes every decision after this one.
- Match your symptom to its specific guide — we have detailed ones for the critical error message, the white screen, plugin updates that broke the site, login problems, database connection errors, and maintenance mode — each linked below.
- Check whether the public site and admin area are broken the same way. Public-broken/admin-working means you can likely fix it from the dashboard; both-broken points deeper (server, PHP, database).
- If the site looks hacked rather than broken — strange redirects, spam pages, warnings from Google — stop and switch to the security guides; repair steps for a hacked site are different and more urgent.
What this usually means
Nearly every broken WordPress site falls into one of four buckets: a component crashed (plugin/theme/PHP — errors and white screens), the database connection failed ("error establishing a database connection"), the server or hosting has a problem (500s, timeouts, suspensions), or it was compromised (redirects, spam, defacement). The visible symptom tells you the bucket, and the bucket tells you who can fix it and how fast.
The single most common repair in practice is boring: identify the plugin or theme that changed most recently, deactivate it, and the site returns. That's why 'what changed?' matters more than any tool.
WordPress itself is rarely the broken part. Content (posts, pages, orders) lives in the database and survives almost all of these failures — a broken site is nearly never a lost site.
What not to do
- Don't reinstall WordPress or delete the site to start over — content survives almost every failure, and reinstalls can destroy the one thing that was safe.
- Don't restore an old backup as a first move; you'll lose recent content and orders when the actual fix may be deactivating one plugin.
- Don't make five changes at once — if the site comes back you won't know why, and if it gets worse you can't retrace your steps.
- Don't follow forum snippets that have you pasting code into functions.php as a first resort — that file takes the site down on any typo.
- Don't share your hosting or admin passwords with anyone who cold-contacted you offering to fix the site.
When to get help
Get help sooner rather than later when: the site earns money and is fully down; the both-broken pattern points at server or database; anything suggests hacking; or you've made two attempts and the picture is getting murkier instead of clearer. A professional repair on a well-described problem is typically fast — the write-up you did in the first safe check above is exactly what makes it fast.
Trial and error has a real cost on a live site: every hour down costs trust and sales, and each experimental change adds one more variable to untangle.
Could your hosting be the problem?
If your host is slow, unreliable, or hard to deal with, moving to a better one can clear up issues like this for good. One we genuinely recommend is Instant Access Internet Services — a smaller, compassionate company with 30 years in the business, known for being one of the fastest, with great management and low pricing. (Just a recommendation — no affiliate link, no kickback.)
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Frequently asked questions
Can a broken WordPress site be fixed without losing content?
Almost always yes. Content lives in the database, and the common failures — crashed plugins, theme errors, server problems — don't touch it. The main way content actually gets lost is hasty repairs: reinstalls and old-backup restores.
How much does WordPress repair cost?
A well-described single issue (one error, known trigger) is often an hour or two of professional time. Vague problems ('it's just broken, no idea since when') cost more because diagnosis is the expensive part — which is why documenting the symptom and trigger yourself first saves real money.
Should I fix WordPress myself or hire someone?
Reasonable DIY: deactivating a named plugin, using a recovery-mode link, clearing caches. Reasonable to hire out: anything involving FTP, database repair, file editing, or a hacked site — the downside of a mistake there is much bigger than the fee.
Why does my WordPress site keep breaking?
Usually a fragile foundation: too many plugins, some abandoned by their developers, updates applied all at once, no staging site, budget hosting. Each repair is a symptom; trimming plugins and updating one-at-a-time treats the cause.
What's the first thing to do when a WordPress site breaks?
Write down exactly what's wrong and what changed in the last 48 hours, then confirm a backup exists. Those ten minutes make everything after — DIY or hired — faster and safer.