Server Error (5xx) in Search Console: Causes and Fixes
Why Googlebot sees 5xx errors, how to find the cause, and how to confirm the fix.
"Server error (5xx)" in Search Console's Page indexing report means that when Googlebot requested a page, your server answered with an error in the 500 range instead of the page. If it happens often, Google slows down crawling and may drop affected pages from its index.
What the codes mean
- 500 Internal Server Error โ something broke while generating the page: a code error, a plugin conflict, a database problem.
- 502 Bad Gateway / 504 Gateway Timeout โ a proxy or CDN could not get a timely response from your server.
- 503 Service Unavailable โ the server is overloaded or in maintenance. Short 503s during maintenance are fine; long ones are not.
Step 1: Check whether it is still happening
Open some example URLs in your browser and use URL Inspection's live test. If they load normally now, the errors may have been temporary โ an outage or traffic spike. Check the Crawl stats report (Settings โ Crawl stats) for when errors occurred.
Step 2: Look for common causes
- Hosting limits. Shared hosting can hit CPU, memory or process limits during busy periods or heavy crawling.
- Firewalls and bot protection. Security tools sometimes challenge or block crawlers, returning errors or challenge pages instead of content. Check that verified Googlebot traffic is allowed and not served a challenge.
- Slow database queries or heavy pages that time out.
- Broken updates to the theme, plugins or server software.
- Maintenance mode left on longer than expected.
Your hosting error logs usually show the exact cause โ ask your host for them if you cannot access them.
Step 3: Fix and test
Fix the cause โ upgrade the plan, adjust the firewall, repair the plugin, add caching โ then test again. Run your key pages through the free site audit report to confirm they return a normal response and load properly. The bulk indexability checker shows the status code for many URLs at once.
Step 4: Validate in Search Console
Click "Validate fix" on the issue. Google rechecks the affected URLs over the following days or weeks.
Plan maintenance properly
If you must take the site down, return a 503 status with a Retry-After header for the shortest time possible. Never show a maintenance page with a 200 status โ Google may index it in place of your content.
A worked example
An education site saw hundreds of 5xx errors every evening. Crawl stats showed they clustered between 7 and 10 pm โ the site's busiest hours. Server logs showed the hosting plan's process limit being reached. Moving to a larger plan and enabling page caching removed the errors, and Google's crawl rate recovered over the next few weeks. Related: how to check if a page is indexed and Core Web Vitals for beginners.
Questions to ask your host
- Did my account hit CPU, memory or process limits on the dates shown in Search Console?
- Is any firewall or bot protection blocking or challenging Googlebot?
- What do the error logs show for these URLs at those times?
- Was there maintenance or an outage on the server?
- Would a larger plan or caching solve the load issue?
Share the exact dates and example URLs from Search Console โ specific information gets faster, more useful answers from support teams.
Related guides
More free tools: browse all our free SEO tools, no sign-up needed.
Frequently asked questions
Do a few 5xx errors hurt SEO?
Occasional short errors are normal. Persistent errors reduce crawling and can lead to pages being dropped.
Can a firewall cause 5xx errors for Google only?
Yes. Bot protection can block or challenge crawlers while normal visitors see the site fine.
What status should I use during maintenance?
503 with a Retry-After header, for as short a time as possible.
How long does validation take?
Usually days to a few weeks, depending on how many URLs are affected.