Server Errors (5xx), explained properly.
5xx errors indicate server-side failures: 500 (generic fault), 502 (bad gateway), 503 (unavailable), and 504 (timeout). Persistent 5xx errors reduce Google's crawl rate and can remove pages from the index. For example, a plugin conflict throwing 500s for 24 hours can wipe rankings on the affected URLs.
What are server errors (5xx)?
Server errors are HTTP status codes that indicate a problem on the server side, preventing a page from loading properly. Unlike 4xx client errors, these occur when the server fails to respond correctly. The IANA HTTP status codes registry maintains the official list.
Why do server errors matter for SEO?
- **Crawlability:** Googlebot may stop crawling, affecting your crawl budget. - **Indexability:** pages returning 5xx errors will not be indexed. - **User experience:** visitors bounce when content will not load. - **Conversion rates:** you cannot convert visitors if the site is not accessible.
Common types of 5xx server errors
- **500, Internal Server Error:** a generic error indicating a server malfunction without specifics. Causes include plugin conflicts, memory overload, or misconfigurations. - **502, Bad Gateway:** occurs when one server acting as a gateway or proxy receives an invalid response from another server. Common in load balancer or reverse proxy setups. - **503, Service Unavailable:** the server is temporarily unable to handle the request, often due to maintenance, overload, or downtime. It should use a Retry-After header when intentional. - **504, Gateway Timeout:** happens when a server acting as a gateway or proxy times out waiting for a response. Often seen on slow or overwhelmed servers. - **507, Insufficient Storage:** the server has run out of disk space (less common).
What causes 5xx errors?
- Plugin or theme conflicts (especially in WordPress). - Memory or CPU overload. - Server misconfigurations (.htaccess, nginx, php.ini). - DNS or CDN issues. - Hosting limitations or outages. - CMS errors, database corruption, or failed cron jobs.
How to monitor for server errors
1. **Google Search Console:** check the Pages report under Indexing, in the "Why pages aren't indexed" section, for "Server Error (5xx)" listings. 2. **Screaming Frog:** run a full crawl and filter for 5xx status codes; export this as part of routine SEO audits. 3. **Uptime monitoring tools:** UptimeRobot (free, simple alerts), Pingdom (detailed performance tracking), and StatusCake (client reporting features).
How to fix server errors
**500 errors:** - Check the error logs. - Disable plugins or themes, then re-enable them individually. - Increase the PHP memory limit or max execution time. **502 and 504 errors:** - Check proxy settings and load balancer configuration. - Contact your CDN provider. - Upgrade hosting if it is consistently overloaded. **503 errors:** - Wait for maintenance to complete. - Add a Retry-After header to notify bots. - Fix resource-hungry scripts or database issues.
Preventing 5xx errors long-term
- Choose reliable hosting and avoid the cheapest options. - Use uptime monitors and respond quickly to issues. - Test plugins in staging before deploying live. - Keep your CMS and PHP versions updated. - Use caching and CDNs to reduce server load.
Are 5xx errors always bad?
Generally yes, with one exception. If you are intentionally using a 503 to take a site offline for maintenance, and you tell Google to retry later, that is fine.
Server Errors (5xx): common questions.
How are 5xx errors different from 4xx errors?
4xx errors (404, 403) are client errors: the request was malformed or the resource does not exist. 5xx errors are server errors: the server failed while trying to handle a valid request.
Will 5xx errors hurt my rankings?
Yes when persistent. Occasional 5xx errors during traffic spikes are tolerated, but repeated errors over hours or days cause Google to slow crawling and may deindex affected URLs.
How do I fix 5xx errors?
Identify the cause (capacity, database, plugin conflicts, memory limits, or specific URLs), check Search Console's Coverage report and your server logs, then fix accordingly.
What is a 503 retry-after header?
Return HTTP 503 with a Retry-After header indicating when the site will be back. Google respects this and pauses crawling without penalising the site.
“I've had the pleasure of working with Chris on several SEO projects for my websites in the health field. He was definitely been able to demystify things so that I felt able to make decisions with him and feel confident they were the right ones. For a non-techie, that is worth gold! I look forward to working with Chris again and warmly recommend him to anyone who - like me - is unsure about all things SEO.”
“I was recommended by my branding partner to use Chris and his team last year. I can’t recommend them highly enough. They are very responsive , easy to communicate with and great at translating techy stuff when needed. They are now an essential part of my business model”
“We've been working closely with Chris, Hannah and the team for over 12 months now. As a small company with ambitious growth plans, it was incredibly important that we made the right choice on who to trust with our SEO. 18 months later, we're totally thrilled with our experience so far and our growing online presence within our market. We'd happily recommend BTT and their services to other SMEs. Drop them an enquiry!”
You work directly with the senior people who do the work, a small Bristol team you will actually get to know, not a call centre or an account manager relaying messages.
Meet the team →
