What does “Server error (5xx)” mean and how do you fix it?
The server returned a 5xx error to Googlebot. The server answered Googlebot with 500, 502, 503 or a similar error. If errors persist Google slows crawling and may start dropping URLs from the index.
Contents
What does this status mean?
The server answered Googlebot with 500, 502, 503 or a similar error. If errors persist Google slows crawling and may start dropping URLs from the index.
Possible causes
- The server is overloaded or hit a resource limit.
- A bug in application code crashes on specific URLs.
- A firewall, rate limit or bot protection blocks Googlebot.
- A temporary outage during maintenance or deployment.
How to fix it
- Find the 5xx entries from Googlebot request times in your server error logs and fix the cause.
- Verify that firewall and CDN rules do not block Googlebot.
- Use 503 with a Retry-After header for planned maintenance rather than a blank page with 200.
- Increase server capacity and caching, and watch the server error rate in Search Console crawl stats.
- When fixed, start validation and resend important URLs.
Steps for your platform
Open the matching fix page for menu names and setting locations on your platform:
- WordPress
- WooCommerce
- Shopify
- Wix
- Blogger
- Webflow
- Squarespace
- Joomla
- Drupal
- Magento
- OpenCart
- PrestaShop
- Ticimax
- IdeaSoft
- Next.js
- React SPA
- Laravel
- Ghost
After fixing
In Search Console start "Validate fix" for the status, resubmit the page with URL inspection and confirm the blocker is gone with the free Free indexability checker tool. For many URLs see Bulk URL indexing: how to send thousands of pages to Google. Validation can take days to weeks.
Related terms
Frequently asked questions
Does a brief 5xx matter?
Google tolerates a brief outage. Errors lasting days can cause index loss.
How do I know if my server blocks Googlebot?
Run a live test in URL inspection; if it errors while the site opens in a browser, blocking is likely.