Google Search Console – Servererror (5xx)

If an Error 500 really occurs, it should be found in an error log file. You can find it in your hosting area. If necessary, the support of your hosting can help you.

Alternatively, you could also enable debugging in WordPress. How to do this is described here: https://www.ads-software.com/support/article/debugging-in-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.

In both cases you should be able to see what the cause is in the logfile.

In addition, please note that the Search Console sometimes reports things with a time delay. Go to the relevant URL in the Search Console and check the live view. If everything is OK there, then it is Google’s own cache. This usually takes some time to clear.

And: Google is not interested in files such as /wp-includes/block-supports/block-style-variations.php. Good if your host has already blocked the visibility.

Hi there @threadi, and first of all, than you so much for your help!

So, I’ve checked and CPanel Error log is filled with errors such as:

[Mon Sep 16 20:57:39.370980 2024] [autoindex:error] [pid 41212:tid 47760650946304] [client 66.249.69.162:0] AH01276: Cannot serve directory ……………………../wp-content/uploads/revslider/templates/bubble-morph-hero/: No matching DirectoryIndex (index.php,index.php7,index.php5,index.perl,index.pl,index.plx,index.ppl,index.cgi,index.jsp,index.jp,index.phtml,index.shtml,index.xhtml,index.html,index.htm,index.js) found, and server-generated directory index forbidden by Options directive

[Mon Sep 16 20:46:03.327981 2024] [autoindex:error] [pid 40769:tid 47760634136320] [client 66.249.69.162:0] AH01276: Cannot serve directory ………/wp-content/uploads/revslider/templates/cube-animation/: No matching DirectoryIndex (index.php,index.php7,index.php5,index.perl,index.pl,index.plx,index.ppl,index.cgi,index.jsp,index.jp,index.phtml,index.shtml,index.xhtml,index.html,index.htm,index.js) found, and server-generated directory index forbidden by Options directive

I think don’t feel confident enough (don’t have the knowledge) to debug the site myself… I’m imagining it is not that easy and I really don’t want to mess up…

Regarding my hosting, they suggested I asked for help here ?? on the forum…

In addition, please note that the Search Console sometimes reports things with a time delay. Go to the relevant URL in the Search Console and check the live view. If everything is OK there, then it is Google’s own cache. This usually takes some time to clear.

I did and when I try to copy the files like these:
mysite.com/wp-includes/sodium_compat/src/Core32/Poly1305/State.php
and paste them in a incognito browser I get a
“
This page isn’t working

[mysite.com]?is currently unable to handle this request.

HTTP ERROR 500

“
And: Google is not interested in files such as/wp-includes/block-supports/block-style-variations.php. Good if your host has already blocked the visibility.

I would imagine that… but if that is the case why did this errors spiked after the installation of the two plugins…

For reference [5xx errors and pages afected]
https://postimg.cc/LJLXKRsv

Non oindexed pages spiked also on the same day
https://postimg.cc/rDXV9b94

And it was I that blocked the visibility of the directories after I asked for help to my hosting.
They explained that WordPress Core files were in fact acessible, which I could confirm by visiting: mysite.com/wp-includes/ (all files were visible) and that I should add this line on .htaccess:

Options -Indexes

Which I also did…

But the thing is that the erros still apear on GSC… Should I do anything else?

Again THANK you so much for all the help

The above messages from the error log are not errors but warnings. They were probably caused by access to unauthorized directories by bots looking for points of attack. Unfortunately, this is normal madness on the Internet and cannot be prevented.

Have you checked the live view URLs reported by the Search Console as described above? There should also be information about this.

Hi threadi,

Again, thank you so much for all your help!

Replying to your topics

The above messages from the error log are not errors but warnings. They were probably caused by access to unauthorized directories by bots looking for points of attack. Unfortunately, this is normal madness on the Internet and cannot be prevented.

Just to be clear – this example bellow apears on my CPANEL under Metrics > Errors:
[Mon Sep 16 20:57:39.370980 2024] [autoindex:error] [pid 41212:tid 47760650946304] [client 66.249.69.162:0] AH01276: Cannot serve directory ……………………../wp-content/uploads/revslider/templates/bubble-morph-hero/: No matching DirectoryIndex (index.php,index.php7,index.php5,index.perl,index.pl,index.plx,index.ppl,index.cgi,index.jsp,index.jp,index.phtml,index.shtml,index.xhtml,index.html,index.htm,index.js) found, and server-generated directory index forbidden by Options directive

…and mentions [autoindex:error], so I assumed this was an error :/

And has this error started to apear on the same day of the errors of the Google Search Console, I deducted that there was a connection between both incidents and that they were related… So, there is nothing to do , regarding this issue?

as to

Have you checked the live view URLs reported by the Search Console as described above? There should also be information about this.

I assumed that what you meant by live view was to copy and past the error URLs as they apear on search console on an incognito browser window and test them – I did that and the browser displays a 500 error.

??

Thank you

No, I was referring to the function that the Search Console offers for this. However, if you experience Error 500 yourself, then this must be reflected in the error log. Look there to see what exactly was logged at the time you called up the URL.

The above message starts with “Cannot serve directory”, everything before that is an individual specification from your hoster, which does not necessarily have to be an actual error. In this case it is just a warning. If you examine the Error 500 through your call, it should say something like “PHP Fatal error” or similar.

ohhh I think you mean url inspection tool!
If that is it, for this specific page:
https://www.clinicamedicadoporto.pt/wp-includes/block-supports/block-style-variations.php

I get a 5xx error also… “It is not possible to index the page”
https://postimg.cc/JHDTTwyJ

if I check on chrome developer tools console and when I load the page I get:
“Failed to load resource: the server responded with a status of 500 ()”

If you examine the Error 500 through your call, it should say something like “PHP Fatal error” or similar.

:: If it is not what I previously done I don’t think I know how to do this “examine though my call”.

??

No, the URLs of files in wp-includes do not matter. You don’t need to check them. These should fly out of Google again due to the change your host has made. Relevant are URLs that belong to your website itself that Google reports as incorrect.

By checking the error log, I meant: call up a faulty URL and check the error log immediately afterwards for the latest entry there. Pay attention to the time at which you called up the URL. Then you should see what kind of error occurs there. However, if it is a wp-includes-URL, I would ignore it.

Ok. I’ll try to see to that.

the only change they made (actually I but by their recommendation) was to include this line of code on the .htacess file

Options -Indexes

Most errors are actually regarding wp-includes, I think.
I’ll ignore them
Thank you for all your help.
I’m deeply grateful ??