Server Error (5xx) in Search Console: What It Means and How to Fix It
When Google gets a 5xx response, it slows crawling and, if errors persist, can drop URLs from the index. This guide explains how Google treats 5xx and 429 responses, how recovery works, how to find the cause on a WordPress site, and what Google’s page does not specify.
- How Google reacts
- Indexing effect
- Find the cause
- Recovery
5xx or 429 -> crawl slows persistent -> URL dropped 2xx again -> rate recovers
Google’s crawlers slow down temporarily when they get a 5xx or 429 response, and content returned with a 5xx is ignored. Already-indexed URLs are kept at first but eventually dropped if they keep returning server errors. Once the server returns 2xx again, Google gradually raises the crawl rate. Find the cause in server logs, fix it, then recheck in Search Console.
How Google reacts
| Area | Behaviour per Google |
|---|---|
| Crawling | Crawlers slow down temporarily; for 500, slowdown is proportional to how many URLs return errors |
| 429 | Treated as a sign the server is overloaded, counted as a server error |
| Content | Content from any URL returning 5xx is ignored |
| 502 and 503 | Grouped with 500; no separate behaviour listed |
Effect on indexing
Already-indexed URLs are kept in the index at first, but eventually dropped. For Google Search, URLs that keep returning server errors are removed from the index. See HTTP status codes for SEO.
Recovery
Once the server returns a 2xx status, Google gradually raises the crawl rate again. Recovery is gradual, not instant, so a fixed outage can still show lingering errors for a while (my own reading of “gradually”).
Find the cause
Google notes that Search Console generates error messages for 4xx to 5xx responses and failed redirects.
Common causes (my own list)
- PHP errors or fatal plugin conflicts.
- Memory or process limits on shared hosting.
- Database connection failures.
- Traffic spikes or bot overload.
- Firewall, rate limiting or security rules returning errors to crawlers.
- Server maintenance without a proper response.
Fix it step by step
Reproduce the error
Load the URL; check status.
Read server logs
Find the failing request.
Disable suspects
Plugins, theme, rules.
Check resources
Memory, CPU, database.
Live test in Search Console
Confirm available.
Watch recovery
Crawl stats over days.
Related behaviours
A 2xx page that looks like an error can be reported as a soft 404 (guide). For crawl capacity effects see crawl budget. Slow responses matter too: TTFB.
Notes for WordPress sites
- Debug log: enable WP_DEBUG_LOG temporarily to capture PHP errors (my own tip).
- Caching: a page cache can reduce load and server errors.
- Cloudflare or WAF: check whether rules block or challenge Googlebot (Cloudflare SEO settings).
- Hosting: persistent errors may need a plan upgrade (speed guide).
Troubleshooting
| Symptom | Likely cause (my own diagnosis) | Action |
|---|---|---|
| Error only for Googlebot | Firewall or rate limit | Allow verified Googlebot |
| Random 5xx under load | Resource limits | Cache and upgrade |
| Error after plugin update | Plugin conflict | Roll back or disable |
| Fixed but status remains | Report lag | Validate and wait |
Checklist
Diagnose
- Reproduce
- Read logs
- Check Crawl stats
- Note timing
Fix
- Plugin conflicts
- Resource limits
- Database health
- Firewall rules
Verify
- Live test passes
- Status 200
- Validate in report
- No new errors
Prevent
- Caching
- Uptime monitoring
- Updates tested
- Capacity planned
What Google’s page does not say
It does not give debugging steps, how much the crawl rate drops or how quickly, how many errors count as persistent, how long Google waits before removing an indexed URL, or the details of network and DNS error handling and robots.txt fetch errors (both are linked elsewhere). It also does not describe 503 as meant for temporary outages.
Key terms
- 5xx
- Server error status codes.
- 429
- Too many requests.
- Crawl rate
- How fast Google requests pages.
- Soft 404
- Error-like page with 2xx status.
Common mistakes
Ignoring persistent errors
URLs can be dropped.
Blocking Googlebot by accident
Firewall rules.
Only checking in a browser
Errors may be bot-only.
Expecting instant recovery
Crawl rate rises gradually.
Rate limiting crawlers hard
429 counts as server error.
No monitoring
Outages unnoticed.
Related guides
Server error questions
What does Google do on a 5xx?
Crawlers slow down temporarily and ignore the content.
Will my pages drop from Google?
Indexed URLs are kept at first but eventually dropped if errors persist.
Is 429 a server error?
Google counts it as one, a sign of overload.
How fast does crawling recover?
Gradually after 2xx returns; no timing is given.
Is 503 treated differently?
The page I used does not give it separate behaviour.
How do I find the cause?
Server logs, Crawl stats and a live test.
Can plugins cause 5xx?
Yes, conflicts are a common cause (my own experience).
How long before URLs are dropped?
Google does not say.
Crawling, content and indexing behaviour come from Google’s page. Causes, steps, WordPress notes, troubleshooting and checklists are my own.