A 500 is the server's generic way of saying something broke on its end, not the visitor's, and it couldn't complete the request as a result. Unlike a 404, which means the page doesn't exist, or a 403, which means access is refused, a 500 means the server tried and failed: a script error, a database that didn't respond, a plugin conflict, or server resources maxed out under load are all common causes.
Because the code is so generic, the real diagnosis happens in server logs rather than in the error message itself, which rarely explains what actually went wrong. Search engines that repeatedly hit 500 errors on a site will crawl it less over time, treating the instability as a reason to hold back, which makes frequent 500s a slow-burning ranking risk even when each individual incident gets fixed quickly. Monitoring for them and fixing the underlying cause, not just refreshing the page until it loads, is what keeps them from adding up.
