A 404 tells Google a page does not exist. A 5xx error tells Google something worse: your server could not deliver the page at all. Users see an error screen, conversions stop, and if the problem continues, search engines start to back away.
Short blips rarely do lasting harm. But persistent or widespread server errors slow down crawling, delay indexing of new content and can eventually push pages out of Google's index. That makes 5xx monitoring a core part of technical SEO, not just a job for the hosting team.
This guide explains what each common 5xx code means, how Google reacts to them, how to find and diagnose them, and how to use 503 correctly for planned maintenance.
Key Takeaways
- 5xx status codes mean the server failed to fulfil a valid request; the most common are 500, 502, 503 and 504.
- Google says 5xx and 429 errors make its crawlers temporarily slow down crawling.
- Indexed URLs are kept for a while, but URLs that persistently return server errors are eventually dropped.
- Find errors in Search Console (Page indexing and Crawl Stats), server logs and uptime monitoring.
- Use 503 for planned downtime and keep it short; Google advises against serving such errors for more than 1–2 days.
What the Common 5xx Codes Mean
| Code | Name | What it usually means | Typical causes |
|---|---|---|---|
| 500 | Internal Server Error | Generic failure in the application | Code bugs, plugin conflicts, bad configuration, PHP fatal errors |
| 502 | Bad Gateway | A proxy or CDN got an invalid response from the origin | Origin crashed, misconfigured upstream, firewall |
| 503 | Service Unavailable | Server temporarily unable to handle the request | Maintenance, overload, resource limits |
| 504 | Gateway Timeout | A proxy or CDN waited too long for the origin | Slow database queries, long-running scripts |
| 508 / 520+ | Vendor-specific codes | Loop detection or CDN-specific errors | Hosting- or CDN-specific issues |
How Google Handles Server Errors
Google documents its behaviour clearly in its guidance on HTTP status codes:
“5xx and 429 server errors prompt Google's crawlers to temporarily slow down with crawling.”
— Google Search Central, How HTTP status codes affect Google's crawlers
The same page explains that already indexed URLs are preserved in the index for a while but eventually dropped if they keep failing, and that the crawl rate reduction is proportionate to the number of URLs returning errors. Once the server responds normally again, Google gradually increases crawling. It also treats a 429 Too Many Requests as a sign the server is overloaded.
In practical terms, a short outage is recoverable. A week of intermittent 500s on your product templates is not something to ignore. The knock-on effects can include slower discovery of new pages, which often shows up as Discovered – currently not indexed.
How to Find 5xx Errors
- Page indexing report: look for "Server error (5xx)" under why pages are not indexed. See our Page indexing report guide.
- Crawl Stats report: check the response breakdown and host status for server connectivity problems; our Crawl Stats guide explains the charts.
- Server and CDN logs: the most complete source, showing which URLs failed, when and for which user agents. See log file analysis.
- Site crawlers: tools such as Screaming Frog or Semrush Site Audit flag 5xx responses during a crawl.
- Uptime monitoring: external checks alert you within minutes; see our post on uptime monitoring for SEO.
How to Diagnose and Fix Server Errors (Step by Step)
- Confirm the error. Request the URL yourself with
curl -Ior a browser, from more than one location if possible. Some errors only affect certain regions or user agents. - Determine scope. Is it one URL, one template, or the whole site? Template-wide errors usually point to code; site-wide errors to hosting or infrastructure.
- Check the timing. Correlate the first errors with deploys, plugin updates, traffic spikes, cron jobs or CDN changes.
- Read the server error logs. Application logs (PHP, Node, Python) usually name the failing file or query.
- Check resources. Look at CPU, memory, database connections and PHP worker limits. Overloaded servers often return 503 or 504.
- Check the CDN and firewall. 502 and 504 errors often come from the layer between users and your server. Make sure security rules are not blocking or rate-limiting Googlebot.
- Fix and roll back if needed. Revert recent changes first if they are the likely cause, then fix properly.
- Validate in Search Console. Use "Validate fix" in the Page indexing report and watch Crawl Stats return to normal.
Using 503 for Planned Maintenance
When you need to take a site offline briefly, return a 503 Service Unavailable with an optional Retry-After header rather than a 200 "under maintenance" page, which Google could index in place of your content. Google's guidance on reducing crawl rate says you can temporarily return 500, 503 or 429 to slow crawling, but warns:
“We don't recommend that you do this for a long period of time (meaning, longer than 1-2 days).”
— Google Search Central, Reduce Google crawl rate
| Scenario | Right response | Avoid |
|---|---|---|
| Planned maintenance for a few hours | 503 with Retry-After | 200 maintenance page |
| Server overloaded by bots | 429 or 503 briefly, then fix capacity | Blocking Googlebot in robots.txt |
| Page permanently removed | 404 or 410 | 500 errors |
| Page moved | 301 redirect | Error codes |
How to Prevent Server Errors
Most 5xx incidents are predictable in hindsight. A few habits reduce how often they happen and how long they last:
- Right-size hosting for your peak traffic, not your average. Seasonal sales, email campaigns and viral posts all create spikes; our guide to web hosting and SEO covers what to look for.
- Cache aggressively at the edge so most requests never reach the origin; see our CDN SEO guide.
- Deploy with a rollback plan, and avoid big releases right before weekends or peak periods.
- Test plugin and platform updates on staging first, especially on WordPress and WooCommerce sites.
- Watch slow database queries, which often turn into 504 timeouts under load.
Common Mistakes
- Serving a 200 status on error pages, which can lead to soft 404s and error text being indexed.
- Leaving 503 maintenance mode on for days after a migration.
- Caching error responses at the CDN, turning a brief origin failure into a long outage; see our browser caching guide for header basics.
- Blocking Googlebot with bot-protection rules, which can surface as 5xx or 403 responses only to crawlers.
- Assuming errors are fixed because the homepage loads. Check the specific URLs and templates Google reported.
- No alerting. Without monitoring, you find out from a traffic drop weeks later.
Related Guides
- Excessive DOM Size: Why It Hurts Performance and How to Fix It
- How to Set Up 301 Redirects in .htaccess
- 400 Bad Request Error: Causes and How to Fix It
Frequently Asked Questions
Do 5xx errors hurt SEO?
Short, occasional errors usually do not cause lasting harm. Persistent errors make Google crawl less and can eventually lead to URLs being dropped from the index.
How long can my site be down before rankings suffer?
Google does not give an exact limit. Its crawl-rate guidance advises against serving 500, 503 or 429 for longer than 1–2 days, so aim to restore normal responses well within that window.
What is the difference between a 500 and a 503 error?
A 500 is a generic server failure, usually a bug or misconfiguration. A 503 means the server is temporarily unavailable, typically because of maintenance or overload.
Why does Search Console show 5xx errors when my site works?
Errors may have been intermittent, affected only certain URLs, occurred during traffic spikes, or been triggered only for Googlebot by a firewall or CDN rule. Check logs for the reported dates.
Should I use 503 or 429 to slow Googlebot down?
Both signal temporary overload. Use them only briefly while you fix capacity, and never as a long-term crawl control.
Conclusion
Server errors are one of the few technical problems that can stall crawling site-wide. Monitor them continuously, diagnose by scope and timing, use 503 correctly for maintenance and keep any downtime short.
If 5xx errors keep recurring, our technical SEO team can work with your developers and host to find the root cause, and our traffic recovery specialists can help if rankings have already slipped. Get a free quote.
