Medium — Server Reliability
Server Error (5xx) in Google Search Console
Google received a 500, 502, 503, or other 5xx response when trying to crawl your page. If this happens consistently, the page will be dropped from the index. Intermittent 5xx errors degrade crawl efficiency and trust.
Tests response codes, TTFB, and crawler access. No account required.
Why This Happens
- 500 Internal Server Error. Unhandled exceptions in your application code. PHP fatal errors, uncaught Node.js exceptions, or database connection failures.
- 502 Bad Gateway. The reverse proxy (Nginx, Cloudflare) couldn't reach your origin server. Common during deployments.
- 503 Service Unavailable. Server is overloaded or in maintenance mode. If Google hits 503s repeatedly, it backs off crawling significantly.
- 504 Gateway Timeout. The origin server took too long to respond. Heavy database queries or memory issues during peak traffic.
How to Fix It
- Check server logs. Look at the exact error and stack trace during the times GSC reports the failures.
- Monitor uptime. Use an uptime monitor (UptimeRobot, Pingdom) to detect 5xx errors in real-time.
- Optimize slow queries. Database timeouts are the most common cause of 500/504 errors under load.
- Add caching. Serve cached responses when the origin is overloaded. A CDN with origin failover prevents 502s during deploys.
- Fix deploy gaps. Zero-downtime deployments (rolling restarts, blue/green) prevent 502s during releases.
- Rate limit gracefully. Return 503 with
Retry-After header instead of 429 or connection resets.
How SEODiff Detects This
SEODiff's crawler checks HTTP status codes for every page it fetches. The Surface Scan flags any non-200 response codes, and the Rendering Reality Check in the Deep Audit detects pages that return 200 but failed to render (JavaScript errors that produce empty or broken output — a precursor to server errors under load).