How to find and fix Server Error(5xx) in Google Search Console

A server error occurs when Googlebot can't reach your URL, the request takes too long, or your site is overloaded. This makes Googlebot give up on accessing your page.

To see if Google is noticing any issues with your site's availability, check the host status in the Crawl Stats report. If there are any problems, you can confirm and fix them.

Click on the settings button in Google Search Console and open the Crawl Stats Report.

After clicking on the Crawl stats Report you will see the Host Status.

If the status is green, like in the screenshot, then your site is in good state. Otherwise, if there's a problem, you need to investigate further by clicking on the Host Status.

General Guidelines to fix Server Error reported in Google Search Console

1. Check recent host availability in the Crawl Stats report to identify persistent issues.
2. Reduce excessive page loading for dynamic page requests by keeping parameter lists short.
3. Ensure your site's hosting server is not down, overloaded, or misconfigured.
4. If problems persist, consider increasing your site's ability to handle traffic with your web hoster.
5. Verify that you are not inadvertently blocking Google due to DNS or firewall misconfigurations.
6. Control search engine site crawling and indexing by using a robots.txt file and managing Googlebot's crawl rate.

Types of 5xx Server Errors and Their Solutions

For a real-world example of how to troubleshoot these errors, check out our recent case study on Server Error 5xx in Google Search Console. This live case study highlights the process of diagnosing and resolving a complex issue involving multiple redirects.

1: 500 Internal Server Error: This is a generic error message indicating that something unexpected happened on the server, and it couldn't handle the request properly.

To troubleshoot and fix this error, you can try the following steps:

• PHP code mistake: When attempting to modify code using plugins like "File Manager" or the "theme editor" option in the Appearance menu, it's crucial to proceed with caution. Without careful inspection before saving changes, your site suddenly encounter this issue.To avoid such problems, it's advisable to have access to your hosting or cPanel before making any modifications to the code. This ensures that you can safely troubleshoot and rectify any issues that may arise during the editing process.
• .htaccess file issue: Some time you will make unnecessary changes in the .htaccess file due to which site sudden report this issue. In this case we should make a new .htaccess file
• Check Error Logs: Review the server's error logs to identify the specific cause of the error. Error logs can provide valuable information about what went wrong and where to focus your troubleshooting efforts.
• Disable Plugins and Themes: If the error occurred after installing or updating a plugin or theme, try disabling them one by one to see if the error resolves. This can help identify if a specific plugin or theme is causing the issue.
• Increase PHP Memory Limit: If the error is related to insufficient memory, you can try increasing the PHP memory limit in your server configuration or via the wp-config.php file.
• Check File Permissions: Ensure that file and directory permissions are set correctly. Improper file permissions can sometimes lead to server errors.
• Review Recent Changes: If you recently made changes to your website, such as modifying code or updating configurations, consider reverting those changes to see if the error goes away.
• Contact Hosting Provider: If you're unable to resolve the issue on your own, consider reaching out to your hosting provider for assistance. They may be able to provide further insights or help resolve server-related issues.

2: 501 Not Implemented: The server doesn't recognize the request method or can't fulfill it. It might become available in the future.

To address this error, you can try the following steps:

• Check Request Method: Ensure that the request method used by the client (e.g., GET, POST, PUT, DELETE) is supported by the server.
• Review Server Configuration: Verify that the server configuration includes support for the requested functionality or feature. You may need to update server settings or install additional modules or plugins to enable support for the requested method.
• Update Software: If the error is related to outdated software or plugins, consider updating them to the latest versions. Newer versions may include support for the requested functionality.
• Consult Documentation: Review the documentation or specifications for the server and any relevant software to ensure compliance with supported request methods and features.
• Contact Server Administrator: If you're unable to resolve the issue on your own, consider reaching out to your server administrator or hosting provider for assistance. They may be able to provide guidance or make necessary adjustments to address the error.

3: 502 Bad Gateway: The server acting as a gateway received an invalid response from another server.

To troubleshoot and resolve the "502 Bad Gateway" error, you can try the following steps:

• Refresh the Page: Sometimes, the error is temporary and can be resolved by simply refreshing the page. Click the refresh button on your browser or press F5 to reload the page.
• Check Network Connectivity: Ensure that your internet connection is stable and that there are no network issues. You can try accessing other websites to confirm if the problem is specific to the site displaying the error.
• Clear Browser Cache: Cached data in your browser may sometimes cause issues. Try clearing your browser cache and cookies, then reload the page to see if the error persists.
• Try Another Browser: If the error persists, try accessing the website using a different web browser to determine if the issue is browser-specific.
• Contact Website Administrator: If you continue to encounter the "502 Bad Gateway" error, it's possible that there is an issue with the website's server configuration or upstream servers. Contact the website administrator or hosting provider for assistance in resolving the issue.
• Check Server Logs: Server logs can provide valuable information about the cause of the error. Review the server logs for any relevant error messages or warnings that may indicate the root cause of the problem.

4: 503 Service Unavailable: The server can't handle the request due to being overloaded or undergoing maintenance. This is usually temporary.

Here are some common causes of the "503 Service Unavailable" error and steps to resolve it:

• Server Overload: If the server is receiving too many requests or experiencing high traffic volume, it may become overloaded and unable to handle additional requests. In such cases, the server may return a "503 Service Unavailable" error to indicate that it is temporarily unable to process requests. To resolve this issue, wait for the server load to decrease or consider upgrading your server resources to handle higher traffic volumes.
• Maintenance: The server may return a "503 Service Unavailable" error during scheduled maintenance or upgrades. If the website is undergoing maintenance, the server may be temporarily offline, resulting in the error. In such cases, wait for the maintenance period to complete, and the website should become available once again after maintenance is finished.
• Server Configuration Issues: Incorrect server configurations or misconfigurations can also lead to a "503 Service Unavailable" error. Check the server configuration settings and ensure that all configurations are correct. Fix any misconfigurations to resolve the error.
• Check for DDoS Attacks: Distributed Denial of Service (DDoS) attacks can overwhelm the server with a large volume of fake requests, leading to a "503 Service Unavailable" error. Monitor server logs for any signs of suspicious activity or DDoS attacks. Implement DDoS protection measures to mitigate the impact of such attacks.
• Restart Server or Services: Sometimes, restarting the server or specific server services can resolve temporary issues causing the "503 Service Unavailable" error. Restart the server or relevant services and check if the error persists.
• Contact Hosting Provider: If you are unable to resolve the "503 Service Unavailable" error on your own, contact your hosting provider or server administrator for assistance. They can help diagnose the issue and implement appropriate solutions to restore server functionality.

5: 504 Gateway Timeout: The server acting as a gateway didn't receive a timely response from another server.

Here are some common causes of the "504 Gateway Timeout" error and steps to resolve it:

• Upstream Server Issues: The most common cause of a "504 Gateway Timeout" error is when the upstream server, which is responsible for processing the request, takes too long to respond or is unavailable. This could be due to server overload, network issues, or server misconfigurations. Check the status of the upstream server to ensure it is operational and responsive.
• Server Overload: If the upstream server is overloaded or experiencing high traffic volume, it may struggle to process incoming requests in a timely manner, resulting in timeout errors. Monitor server resources and traffic volume to identify any instances of server overload. Consider optimizing server resources or implementing load balancing to distribute traffic more efficiently.
• Network Issues: Network connectivity issues between the gateway server and the upstream server can also cause a "504 Gateway Timeout" error. Check for network connectivity issues, such as packet loss, latency, or network congestion, and resolve them to ensure smooth communication between servers.
• Proxy or Gateway Configuration: Improper configuration of proxy servers or gateways can lead to timeout errors. Review the configuration settings of the gateway server and ensure that they are correctly set up to communicate with the upstream server. Fix any misconfigurations or errors in the proxy settings.
• Increase Timeout Settings: Adjust the timeout settings on the gateway server to allow more time for the upstream server to respond before triggering a timeout error. Increase the timeout values appropriately based on the expected response time of the upstream server.
• Implement Retry Mechanisms: Implement retry mechanisms or caching strategies to handle timeout errors gracefully. If a request times out, retry the request after a certain interval or serve cached content if available to prevent users from experiencing prolonged downtime.
• Contact Service Providers: If you are unable to resolve the "504 Gateway Timeout" error on your own, contact your hosting provider, network administrator, or service provider for assistance. They can help diagnose the issue and implement solutions to resolve the timeout errors.

6: 505 HTTP Version Not Supported: The server doesn't support the HTTP version used in the request.

Here are some common causes of the "505 HTTP Version Not Supported" error and steps to resolve it:

• Outdated Server Configuration: The server may be running an outdated or unsupported version of the HTTP protocol. Upgrade the server software to a version that supports the HTTP protocol version used by the client.
• Client-Side Configuration Issue: Sometimes, the client may be using an outdated or unsupported version of the HTTP protocol. Ensure that the client's software or browser is updated to a version that is compatible with the server's HTTP protocol.
• Misconfigured Proxy Servers: If the request is passing through one or more proxy servers, ensure that the proxy servers are properly configured to support the HTTP protocol version used by the client. Check the proxy server settings and update them if necessary.
• Firewall or Security Software: In some cases, firewall or security software installed on the server may block certain HTTP protocol versions. Review the server's firewall and security settings to ensure that they are not interfering with the HTTP protocol communication.
• Check Server Logs: Examine the server logs to identify any specific errors or warnings related to the "505 HTTP Version Not Supported" error. The logs may provide clues about the underlying cause of the issue, allowing you to take appropriate action to resolve it.
• Contact Server Administrator: If you are unable to resolve the error on your own, contact your server administrator or hosting provider for assistance. They can help diagnose the issue and implement the necessary changes to support the HTTP protocol version used by the client.

7: 506 Variant Also Negotiates: Content negotiation for the request results in a circular reference.

This error is part of the HTTP status code definitions and is specified in RFC 2295.

Here's what this error means and how to address it:

• Understanding Content Negotiation: Content negotiation is the process where a server selects the best representation of a resource based on the client's preferences, such as language or content type. The "Variant Also Negotiates" error occurs when there is an issue with this negotiation process.
• Circular Reference: The error indicates that there is a circular reference in the negotiation process, meaning that the server and client are unable to agree on a suitable representation of the resource due to conflicting preferences or configurations.

Troubleshooting Steps:

• Review Content Negotiation Settings: Check the content negotiation settings on both the server and client sides to ensure they are configured correctly. Look for any conflicting directives or preferences that may be causing the circular reference.
• Adjust Configuration: If possible, adjust the content negotiation configuration to resolve the circular reference. This may involve modifying the negotiation algorithms, updating preferences, or specifying explicit rules for handling certain scenarios.
• Check Server Logs: Examine the server logs for any additional information or errors related to the content negotiation process. This can help identify the specific factors contributing to the error and guide troubleshooting efforts.
• Update Software: Ensure that both the server and client software are up-to-date and compatible with the content negotiation protocols specified in RFC 2295. Updating to the latest versions may resolve any known issues or bugs related to content negotiation.

• Consult Documentation: Refer to the documentation for the server software, client applications, and relevant standards (such as RFC 2295) for guidance on resolving content negotiation issues. The documentation may provide specific instructions or recommendations for troubleshooting and configuration.
• Seek Technical Support: If you're unable to resolve the "506 Variant Also Negotiates" error on your own, consider seeking assistance from technical support resources, forums, or communities dedicated to web development and server administration. Experienced professionals may offer insights or solutions to address the issue effectively.

8: 507 Insufficient Storage: The server can't store the representation needed to complete the request.

This error is part of the HTTP status code definitions and is specified in RFC 4918

Here's what this error means and how to address it:

• Understanding the Error: The "507 Insufficient Storage" error indicates that the server does not have enough storage space to fulfill the request. This typically occurs when the server's disk or storage system has reached its capacity limit.
• Check Server Storage: Begin by checking the server's storage capacity and usage. Verify if the disk or storage system is nearing its maximum capacity or if specific directories or partitions are full.
• Free Up Storage: If the server is low on storage space, identify and remove any unnecessary or temporary files, logs, or backups that are consuming disk space. Consider archiving or deleting outdated data to free up storage capacity.
• Optimize Resource Usage: Review resource usage patterns and optimize the server's configuration to better manage storage resources. This may involve implementing storage quotas, optimizing file storage formats, or configuring automated cleanup processes.
• Monitor Storage Usage: Set up monitoring tools or scripts to regularly monitor storage usage and receive alerts when storage capacity reaches predefined thresholds. This proactive approach allows administrators to take corrective actions before storage shortages impact server performance.
• Consider Expansion: If storage capacity limitations are a recurring issue, consider expanding the server's storage capacity by adding additional disk space or upgrading storage infrastructure. Evaluate options for scalability and growth to accommodate future storage needs.
• Review Application Behavior: Examine the behavior of applications or services running on the server to identify any factors contributing to excessive storage usage or inefficient resource utilization. Optimize application configurations or workflows to reduce storage requirements.
• Update Software: Ensure that server software, including the operating system, filesystem, and applications, is up-to-date with the latest patches and updates. Software updates may include optimizations or bug fixes related to storage management and resource utilization.

9: 508 Loop Detected: The server detected an infinite loop while processing the request.

This error is part of the HTTP status code definitions and is specified in RFC 5842.

Here's what this error means and how to address it:

• Understanding the Error: The "508 Loop Detected" error indicates that the server has detected a circular reference or loop in the request processing. This typically occurs when there is a redirection loop or a recursive function that continues indefinitely.
• Identify the Cause: Begin by identifying the source of the loop. Review the server logs, request processing logic, and any relevant configurations to pinpoint where the loop is occurring.
• Check Redirections: If the error is related to redirections, inspect the redirection rules or configurations in place. Ensure that there are no circular redirects where a request is continually redirected back to the original URL or to another URL in a loop.
• Review Recursive Functions: If the error is caused by a recursive function, examine the code responsible for the recursion. Look for conditions or logic that may result in the function calling itself indefinitely and modify the code to break out of the loop appropriately.
• Limit Recursion Depth: Implement safeguards or limitations to prevent infinite recursion. Set a maximum recursion depth or limit the number of times a function can call itself to prevent excessive looping.
• Test and Debug: Once modifications are made to address the loop, thoroughly test the application or server to ensure that the error no longer occurs. Use debugging tools and techniques to verify that the loop has been resolved and that request processing behaves as expected.
• Monitor for Recurrence: Monitor server logs and performance metrics after implementing changes to detect any recurrence of the "508 Loop Detected" error. Continuously monitor request processing to identify and address any potential issues that may arise.
• Optimize Performance: Evaluate the overall performance of the server and application to identify opportunities for optimization. Consider factors such as algorithm efficiency, resource utilization, and caching strategies to improve overall system stability and performance.

10: 510 Not Extended: Further extensions to the request are required for the server to fulfill it.

This error is defined in RFC 2774.

Here's what this error signifies and how to handle it:

• Understanding the Error: The "510 Not Extended" error indicates that the server cannot fulfill the request without additional extensions. It typically occurs when the client's request lacks certain mandatory extensions or parameters required by the server to process the request fully.
• Check Request Extensions: Review the client's request to identify any missing or incomplete extensions or parameters. The server expects certain extensions to be included in the request to fulfill it properly.
• Verify Server Requirements: Determine the specific extensions or parameters that the server requires to process the request. Consult the server documentation or specifications to understand the mandatory requirements for the requested operation.
• Update Client Request: Modify the client's request to include the necessary extensions or parameters as per the server's requirements. Ensure that the request is properly formatted and includes all mandatory elements specified by the server.
• Test Request: After updating the client request, test it against the server to verify that the "510 Not Extended" error no longer occurs. Use testing tools or utilities to send the modified request and observe the server's response.
• Handle Errors Gracefully: If the server encounters the "510 Not Extended" error despite providing the required extensions, handle the error gracefully. Provide informative error messages to the client, indicating the specific extensions or parameters that need to be included for successful request fulfillment.
• Update Server Configuration: If the server requires additional extensions that are not currently supported, consider updating the server configuration or software to accommodate the necessary extensions. Ensure that the server environment is configured to handle the required extensions effectively.
• Communicate with Clients: If the error persists due to client-side issues or limitations, communicate with the clients to educate them about the required extensions and how to include them in their requests properly. Provide guidance or documentation to assist clients in submitting requests that meet the server's requirements.

11: 511 Network Authentication Required: The client needs to authenticate to gain network access, often seen in Wi-Fi hotspots.

Here's what this error signifies and how to handle it:

• Authentication Requirement: The "511 Network Authentication Required" error implies that the client attempting to access the network resource needs to authenticate itself before proceeding further.
• Intercepting Proxy: This error is often encountered in scenarios where an intercepting proxy is deployed to control access to the network. The proxy intercepts the client's request and requires authentication before permitting access to the requested resource.
• Captive Portals: In some cases, the error may be triggered by captive portals used in public Wi-Fi networks or similar environments. These portals require users to agree to terms of service or authenticate before granting full internet access.
• Authentication Process: To resolve this error, the client needs to undergo the authentication process specified by the network intermediary. This may involve providing credentials such as a username and password or accepting terms of service.
• Handling the Error: If encountering the "511 Network Authentication Required" error, the client should follow the instructions provided by the network intermediary to complete the authentication process. This may involve accessing a login page or acknowledging terms of service.
• User Guidance: Users should be informed about the authentication requirement and guided on how to complete the authentication process successfully. Clear instructions and prompts can help users navigate the authentication steps effectively.
• Technical Support: If users encounter difficulties during the authentication process, they may require technical support or assistance from network administrators. Providing access to support resources can help users resolve authentication-related issues promptly.
• Retry Request: Once the authentication process is successfully completed, the client can retry the original request to access the desired network resource. Subsequent requests should proceed without encountering the "511 Network Authentication Required" error.

Conclusion

In conclusion, understanding and addressing server errors reported in Google Search Console is crucial for maintaining a healthy and accessible website. By analyzing the specific error codes, such as 500 Internal Server Error or 503 Service Unavailable, and implementing the appropriate solutions, website owners can ensure smooth operation and improved performance. From reducing excessive page loading to checking hosting server status and controlling search engine crawling, following these general guidelines can help resolve server errors and enhance the overall user experience. By staying vigilant and proactive in addressing these issues, website owners can mitigate potential disruptions and maintain a positive online presence.