How to fix the 'Server error (5xx)' error in Google Search Console

Have you been hit by a 5xx server error in Google Search Console?

500 errors are an HTTP status code that indicates you messed up something and need to start a late-night debugging session.

500 errors are offensive. I can only compare it to eating fermented shark in Iceland – something you’ll want to spit out almost immediately.

500 server errors create a poor user experience and can reduce your crawl budget. If they persist, Google may start ignoring your site altogether. Your website should be commitment-worthy.

If you’re an SEO professional, you’ve likely stayed up until 3 a.m. with coffee and your DevOps team trying to fix a 500 error. You’ll want to keep reading.

I’ll spare you the suspense and admit – it’s usually not a quick fix.

How do I fix ‘Server error (5xx)’ in Google Search Console?

1. Review all the pages under Server error 5xx report

First, I manually reviewed all the pages flagged in the Google Search Console Server error (5xx) report.

To access the report, go to Google Search Console > Pages > and look under the section Server error (5xx).

If the list is extensive, you’ll want to export it to a CSV, Google Sheets, or Excel file to determine a URL structure pattern.

It may only impact a specific subdomain or subfolder.

2. Inspect the URLs in Google Search Console

Once you’re in the Google Search Console error report, click the magnifying glass icon to inspect the URL in Google Search Console.

After you inspect the URL, you can confirm if it’s listed in your XML sitemap.

Start with the pages listed in your XML sitemap that are serving 500 errors. These are your priority pages.

3. Go to the crawl stats report in Google Search Console

Next, go to Settings > Crawl stats report in Google Search Console.

This report shows the crawl request breakdown. Ideally, you’d see less than 1% of server errors (5xx) listed.

4. Analyze server logs

If you’ve got a good relationship with your dev team, you likely have access to server logs.

If you don’t, I understand your struggle. It’s the developers’ natural defense mechanism not to give access to their domain.

The moment you get access to server logs, it feels like a kid at Christmas. Server log files show all the requests made by search engine crawlers.

Server logs give you access to all different kinds of gifts like:

• How often a user visited your site.
• Time of day.
• Pages of your website with the most crawl requests.
• Users who receive the 500 server error.

5. Update plugins (if using WordPress)

If you’re using WordPress, check your outdated plugins. These can be culprits of 500 server errors.

You can either update the plugin or disable it.

Just be sure to backup everything before messing around with plugins.

6. Investigate .htaccess file

If you’re using a CMS like WordPress, Wix, or Squarespace, the .htaccess file is created automatically.

If you’re using a more sophisticated angle of web development, check your .htaccess file for any recent configuration changes.

If you see any changes, save a copy of the new one and revert to the old version.

7. Go back to the most recent server update

If you recently updated your server, there may be some configuration changes that caused something wonky to happen.

While you and Dev dive into the issue, revert the most recent server update until you identify the root cause.

8. Reach out to your hosting provider

I mistakenly hosted my first-built website on GoDaddy in a shared hosting environment. It caused weekly outages on my site.

Eventually, I migrated off of GoDaddy and into a private hosting environment. It saved me hours of work.

9. Upgrade your server

It may be time to ditch your current server and upgrade to a more efficient server with more memory and processing power.

What is a 500 server error?

500 server error is a server-side error caused by your website’s server. This means Google cannot access or index your page.

Server-side errors are a “it’s not me, it’s you” type of scenario.

500 server error response code cheat sheet

Here are a few common 500 server errors and how to address each.

• 501 – Not implemented: Your server is outdated or has a virus.
• 502 – Bad gateway: Your server is overloaded or there was an outage – or connectivity issues. Try accessing the page in Incognito mode. If it still doesn’t work, flush your DNS cache.
• 503 – Service unavailable: The error is likely temporary and will resolve itself. But to be sure, check to see if your server is down. If not, increase your server resources and disable your CDN and plugins.
• 504 – Getaway timed out: This signals a temporary glitch in your connectivity or your server is overloaded. Always contact your hosting provider. Then, check your server logs. You can also temporarily disable your CDN and check plugins.
• 509 – Bandwidth limit exceeded: This means your server is having a bandwidth issue. Contact your hosting provider to upgrade your server. Then, compress your website content and minify your code.
• 524 – Timeout occurred: The connection between your browser and the server is slow. Check your server memory usage and determine if you need to upgrade your server. Then, compress your website content and minify your code.

What if Google Search Console reports a 500 error, but my site is working?

First, double-check that you’ve cleared your cookies and cache files from your browser.

If you’re still seeing the error, this could be a 503 error,

As mentioned above, a 503 error is when your server is overstuffed like a dumpling with crawl requests. Your server can’t handle the number of requests.

In this situation, consider upgrading your server.

Consult your dev team before starting to maintain that solid relationship. This is a temporary and quick solution.

In the long run, you’ll want to identify uncompressed files and begin compressing them.

Don’t fall into the ‘Server error 5xx’ trap in Google Search Console with overloaded servers or poor configuration

If you’ve come across a “Server error 5xx” in Google Search Console, you know how frustrating it can be.

These errors are outdated and unwelcome – like finding a stack of VHS tapes at a flea market.

But 500 server errors can be dangerously unassuming.

Don’t make the mistake of avoiding it. You can’t ignore these errors. It’s one of those impossible errors like washing cigarette smell off your hands.

Grab some booze for a late night with your dev team if you want your website to be meant for search engine consumption.

Let your SEO instincts kick in. Eventually, you’ll develop a vested interest in fixing your 500 server errors.

Contributing authors are invited to create content for Search Engine Land and are chosen for their expertise and contribution to the search community. Our contributors work under the oversight of the editorial staff and contributions are checked for quality and relevance to our readers. The opinions they express are their own.

The above is the detailed content of How to fix the 'Server error (5xx)' error in Google Search Console. For more information, please follow other related articles on the PHP Chinese website!