Error 500 is the server’s “something went wrong” - a message that deliberately says nothing, but the list of causes is short and repetitive. Internal Server Error, a blank page with just a number, sometimes a message from your host - all the same family: the server tried to build the page and failed. Just like with a WordPress critical error, your data is intact. The difference is that this time something closer to the server broke rather than WordPress itself - which is why the diagnosis starts from a different end.
Five causes behind most cases
- A damaged
.htaccessfile - a tiny file of server rules; it breaks surprisingly often, for example after changing permalink settings or through a security plugin - An exhausted PHP memory limit - a site with a gallery, a store and a page builder needs more than hosting gives by default
- A plugin or theme - the same mechanism as with a critical error, only surfacing at the server level
- An incompatible PHP version - after a change on the server or after plugin updates
- A problem on the hosting side - an overloaded shared server, an outage; rarer, but it happens
Step 1 - rule out .htaccess (2 minutes)
Over FTP or the file manager in your hosting panel, find the .htaccess file in the site’s main directory (it can be hidden - turn on showing hidden files). Rename it to .htaccess-old and refresh the site.
Works? That was it. Log into the WordPress dashboard, go to Settings → Permalinks and click “Save changes” - WordPress will generate a fresh, correct file. Fix complete.
Does not work? Restore the name and move on.
Step 2 - plugins and theme
The procedure is identical to a critical error: in wp-content rename the plugins folder to plugins-off and check the site; if it comes back, re-enable plugins one at a time until you find the guilty one. Then, if needed, the same test on the theme.
Step 3 - memory and PHP version
In the hosting panel look for the PHP section:
- PHP version: if older than 8.1 - raise it (ideally on a test copy, if your host offers one). If the error appeared right after a version bump - go back to the previous one; some plugin is not keeping up and has to be updated or replaced
- Memory limit (
memory_limit): for a site with a store, 256 MB is a sensible minimum. Many hosts let you change this with a slider in the panel, without touching files
What helps: the error logs. In the hosting panel there is a “Logs” or “PHP error logs” section - the last entries around the time of the crash usually name the culprit by file, for example
wp-content/plugins/plugin-name/.... That is the same information you would reach by disabling plugins one by one, only immediately.
Step 4 - hosting
If none of the above helped, write to your host’s support with the time the error occurred and ask them to look at the server logs. Sometimes the answer is “shared server overload” - and that is the moment for an honest conversation about whether this hosting can carry your site. An undersized server is not only about outages, it is about everyday sluggishness too - and a slow store loses customers even when it formally “works”.
Error 500 only sometimes? That is a problem too
A separate variant: the site normally works, but throws a 500 every now and then - under heavier traffic, when an order is placed, at night during the backup. That is the worst kind of failure, because it is hard to catch red-handed and customers hit it at random. Usually server limits or a heavy plugin choking under load are to blame. There is no way around logs and monitoring here - it is typical work I catch for clients under ongoing support, before it grows into a full-day outage.
Frequently asked questions
How is error 500 different from a WordPress critical error?
A critical error is a message from WordPress itself - the engine is running and managed to display it. Error 500 comes from the server - something broke earlier or deeper. The suspect list is similar, but with a 500 you start from .htaccess and the server logs, not from a recovery email.
Does error 500 hurt my Google rankings? A brief outage - no. A site down for days or throwing 500s regularly - yes, Google gradually drops those URLs from results.
How long does a professional fix take? Typically hours. Diagnosis with logs is fast, because the list of causes is short. I give the quote in writing after looking at the site.
Sitting on this yourself and unsure where to start? I speed up and repair existing sites and stores - Core Web Vitals, outages, the features that are missing. Tell me what is happening and you will get a concrete quote with a date.