Option 1: Do it yourself
Follow the steps in this guide. Free, and typically 30 minutes to a few hours of careful work.
Option 2: Just contact us
Skip every step below. $49/mo and it is sorted, or WhatsApp us right now.
Last updated: August 2026
Step 0: Read the actual error
Before touching anything, open your hosting panel's error log (or enable WP_DEBUG_LOG). The last entries name the failing file, and the failing file's path names the guilty plugin or theme. Every step below exists for when you cannot get a log; with a log, you often skip straight to the culprit.
Step 1: Reset .htaccess
The most common cause and the fastest fix. Via your host's file manager, rename .htaccess to .htaccess-old and reload the site. Working now? Log into wp-admin, go to Settings, Permalinks, and click Save to generate a clean file. Done. Corrupted .htaccess files usually trace back to plugin writes or interrupted updates.
Step 2: Rule out plugins
Rename the /wp-content/plugins folder to plugins-off and reload. If the site returns, a plugin caused it: rename the folder back, then rename individual plugin folders one at a time until the error reappears. That last one is your culprit; roll it back a version or replace it. Recent updates are the prime suspects, so start with whatever changed most recently.
Step 3: Raise the PHP memory limit
If the log mentions "Allowed memory size exhausted," add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php. If the host caps memory below what a normal site needs, that is a conversation with the host, or a reason to leave them.
Step 4: Rule out the theme
Rename your active theme's folder; WordPress falls back to a default theme. If that clears the error, the theme broke, usually via an update that conflicted with customizations made without a child theme. Restore from backup and move customizations into a child theme this time.
Step 5: Refresh core files
Rare but real after failed updates: re-upload fresh copies of /wp-admin and /wp-includes from an official WordPress download. Never touch /wp-content, which holds your themes, plugins and uploads.
The special case: 500 only on some pages
A single page erroring while the rest works points to a plugin used only there, a page builder template failure, or a memory limit that only heavy pages exceed. The error log entry for that specific page names it.
When to stop and restore
If the site earns money and the diagnosis is dragging, restore last night's backup first and diagnose on staging afterward. Revenue first, forensics second. This ordering, plus the pre-update snapshots that make it possible, is exactly the discipline our safe update process builds into every maintenance plan.
FAQ
Is a 500 error my host's fault or my website's? Usually the website's (plugins, themes, .htaccess), but server misconfiguration after host-side changes does happen. The error log settles the argument; ask support to share it if you cannot access it.
Visitors saw the error. Does it hurt SEO? Brief 500s are harmless. Extended ones reduce crawling and can drop rankings, which recover after stability returns. Fix speed matters more than fix elegance.
The error appeared with zero changes on my side. How? Automatic plugin updates, host-side PHP upgrades and cron tasks all run without you clicking anything. "No changes" almost always means "no visible changes."
How long does a professional fix take? With access and a log, 20 to 60 minutes typically. It is among the most standard flat-rate fixes we quote.
You do not have to do any of this yourself
Skip the steps above. Our engineers handle security, updates, speed, backups and fixes for you, with a 12-minute average response and a 99.99% uptime target.