Tagged: 500, crawling, directory, listing, robots.txt
-
AuthorPosts
-
February 11, 2015 at 1:58 pm #394329
I have the same problem as desribed here: https://kriesi.at/support/topic/500-error-and-403-error-with-avia_framework_globals/
But the answers are marked private. Can You help me with my problem. I see a directory listing denied in the server log. Is it enough to disallow the folder in robots.txt, ,and does that has any impact on the quality of index at google?
February 11, 2015 at 5:37 pm #394506Hi GeorgLudwig!
What are the exact errors your getting? Copy and paste them here please.
Best regards,
Elliott- This reply was modified 9 years, 9 months ago by Elliott.
February 11, 2015 at 5:48 pm #394519In Webmaster-Tools the error appears in the first tab “Server Errors”
In the log I have
66.249.67.91 – – [08/Feb/2015:23:39:26 +0100] “GET /wp-content/themes/enfold/ HTTP/1.1” 500 0 “-” “Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)” “www.diva-heels.de”
and
[Sun Feb 08 18:45:16 2015] [error] [client 66.249.67.91] PHP Fatal error: Call to undefined function get_header() in /is/htdocs/wp1026082_MQOSW0RJLQ/www_diva/wp-content/themes/enfold/index.php on line 9[Sun Feb 08 18:45:33 2015] [error] [client 66.249.67.91] Directory index forbidden by Options directive: /is/htdocs/wp1026082_MQOSW0RJLQ/www_diva/wp-content/themes/enfold/framework/
[Sun Feb 08 23:39:26 2015] [error] [client 66.249.67.91] PHP Fatal error: Call to undefined function get_header() in /is/htdocs/wp1026082_MQOSW0RJLQ/www_diva/wp-content/themes/enfold/index.php on line 9
February 12, 2015 at 4:55 am #394826Hi!
Sometimes servers don’t do what you ask them to do unfortunately, does your page load when you access it? Do you get a lot of server errors?
http://www.checkupdown.com/status/E500.html
Cheers!
RikardFebruary 12, 2015 at 12:02 pm #394913I’m quite aware of sporadical server errors, but as You can see in the error log even one error is obvious, which is the directory listing. As You can read in the referenced support thread at the beginning this is because google tries to scan the directory which should not occur. The question remains whether this is possible to inhibit by robots.txt.
The other two errors regard the get_header() – as the page is loading quite regularly when opening it I do not suggest this to be a reproducable issue, but I though You’d perhaps seen this behaviour before for any kind of reason.
The server error is indicated in the webmaster console as 1 error, but referenced by almost each page on the site.
Regards,
GeorgFebruary 12, 2015 at 9:33 pm #395351Hey!
They only happened on the 8th? As long as your not getting them anymore when you view your site then you can ignore them or mark them as fixed.
For the directory index forbidden error you can try blocking it in your robots.txt but I do not know how Google will react to that. I would try asking on an SEO forum to see what some experts say.
Best regards,
ElliottFebruary 13, 2015 at 9:59 am #395564I added the entry into the robots.txt – the error currently does not appear anymore. So let’s wait and see – thx anyway
Georg
February 14, 2015 at 4:59 am #396096July 24, 2015 at 8:51 pm #478380I am an SEO guy and am experiencing the same problem with one of my sites using Enfold. While the front end of the site looks gorgeous, Google Webmaster Tools is throwing up this error on the dashboard:
Last crawled: 7/17/15
First detected: 5/11/15
Googlebot couldn’t access the contents of this URL because the server had an internal error when trying to process the request. These errors tend to be with the server itself, not with the request.As you can see this problem has been happening off and on for 2 months. I’ve marked it as fixed a number of times, assuming that it was a server problem, only to find it coming back. I have multiple sites on the same platform (WP Engine) which all use Enfold and this seems to be the only one showing this problem consistently over time. I logged a case with WP Engine (their support is as awesome as Enfold’s!) and they helped me fix the 403 on the framework folder I was having by adding this piece of code to the top of my .htaccess:
Options +Indexes
# or #
IndexIgnore *Moving back to the 500 error – I continued to work with WP Engine and we found this error in the server log file, which points a problem with the header call on line 9…
[Fri Jul 24 18:30:26.399224 2015] [:error] [xxxxxx] [client ……………] PHP Fatal error: Call to undefined function get_header() in ………/xxxxxx/wp-content/themes/enfold/index.php on line 9
WP Engine asked me to contact my theme developer as they cannot see an issue with any other sites of mine with Enfold. Any thoughts at this point are appreciated as I don’t want my Webmaster Tools showing 500’s – and to answer the earlier question, you can no longer get away with hiding CSS files via robots.txt. Since Google upgraded their mobile friendly algorithm on April 21st, they want to be able to completely render your site, so hiding front end files with robots is now frowned on 100%.
Anything I can do to assist in figuring out this issue please let me know as I’m eager to sort this. I’m about to go thru all my Enfold sites with a fine tooth comb and see if any others are showing 500 and 403 with those 2 folders.
Thanks,
KylePHP Fatal error: Call to undefined function get_header()
July 24, 2015 at 9:58 pm #478401Hey!
This normally happens because robots are trying to index wp-content/themes/enfold/index.php and in that enviroment get_header doesn’t exists (hence the error), add this to your robots.txt to prevent crawlers to index theme files:
User-agent: * Disallow: /wp-content/themes/
Regards,
JosueJuly 24, 2015 at 11:48 pm #478434I will try this and post the results in a few days (maybe a week if I get distracted :P) but as I said above, Google needs access to crawl the CSS files in here so it can render the site (and test desktop and mobile versions with this tool:
https://www.google.com/webmasters/tools/mobile-friendly/
Please see the Yoast article on this subject (he knows more about SEO than me):
https://yoast.com/wordpress-robots-txt-example/
Last time I tried to Disallow this folder, I just moved the problem. No 500 error, but I started failing the mobile friendly test and getting ‘blocked resource’ issues in Webmaster Tools. I will wait and see if Google starts throwing errors at me and report back :D
Thanks for your help – I really hope this works as I just completed my inventory and almost all my Enfold sites have the same SEO issue in Google Webmaster Tools.
Kyle
July 24, 2015 at 11:57 pm #478441July 28, 2015 at 8:05 pm #479890Hey Josue – are you suggesting we tackle this from the cro.ma link?
First we’ll look at a coding solution for this.
in your index.php file right at the top you will find the following:
<?php get_header(); ?>
orget_header();
You should replace it with the follwing:<?php if (function_exists(‘get_header’)) {
get_header();
}else{
header(“Location: http://” . $_SERVER[‘HTTP_HOST’] . “”);
exit;
}; ?>July 29, 2015 at 12:36 am #479958So I added the robots.txt restrictions you (and the link to cro.ma) suggest, and this is the result:
As you can see, Google reports the blocking of 4 resources inside the themes folder. I have more sites which are worse, but I’d prefer not to post client sites on here ;)
Any thoughts on next steps? I could add some specific ‘Allows’ to robots for each resource Google needs access to, but I’m here looking for a more reasonable option as that path would be pretty onerous to manage for one site, much less a lot of awesome Enfold sites…
Thanks for your cooperation – I can’t say how much I appreciate Enfold and what its done for me and WordPress.
July 29, 2015 at 5:17 am #480008Hi
This is an issue that I’ve been going around in circles with my developer for some months now.Has anyone managed to get consistently Zero issues on google webmaster tools using enfold (blocked resources, 500 errors on crawl, no crawl errors other than the usual fixable ones through redirects etc)?
Hope you don’t mind me asking, but is Kriesi support fully aware of google webmaster tools ? It’s just that I’ve followed every change there is from past forums and robot settings previously recommended do not work – I’ve tried the lot!
** I thought a separate article on setting robots would be very helpful – as previous references to yoast really don’t help, it’s theme- specific :-) ** All previous forum replies give different settings.
it really seems to be causing a lot of people a lot of headaches
Thanks guys
Richard
July 29, 2015 at 5:41 am #480020Glad to hear I’m not the only one who has been hitting his head up against this… Its happening on all my Enfold sites and I’m constantly going back and forth between blocking robots.txt folders so they don’t throw up errors, then getting other errors because resources in those folders are blocked.
I will say adding this to htaccess:
Options +Indexes
# or #
IndexIgnore *has removed my 403’s so far across the board. Now I’m just trying to figure out if the 500’s are going to go away or if they are going to linger…no verdict yet, but I am keen to hear Kriesi’s thoughts on whether we should or shouldn’t block these resources…I’m not in the habit of hiding things from Google just because I don’t want to see the error :D
July 30, 2015 at 8:19 am #480544Hi,
I tagged Kriesi on the topic, please wait for him to get back to you on this.
Thanks,
RikardJuly 30, 2015 at 8:59 pm #480942Thanks – FYI, Yoast’s article is no longer 1 yr old…he wrote a new one yesterday:
https://yoast.com/dont-block-your-css-and-js-files/
Looking forward to a response…maybe we just need to disallow a specific file instead of the entire folder?
Thanks,
KyleJuly 31, 2015 at 4:16 am #481073Hi Kylerollins
“Glad to hear I’m not the only one who has been hitting his head up against this… Its happening on all my Enfold sites and I’m constantly going back and forth between blocking robots.txt folders so they don’t throw up errors, then getting other errors because resources in those folders are blocked.”
Yes , exactly the same
I’ve allowed access to everything but get a 500 on
wp-content/themes/enfold/I wonder Kriesi / Rikard if there is a generic solution that is updated from previous forums such as
https://kriesi.at/support/topic/issue-with-indexing-of-theme-on-google/
And this is definitely inaccurate advice now: https://kriesi.at/support/topic/what-can-i-exclude-in-robots-txt/Google have changed so up to date advice on what to allow and disallow would be great – perhaps a cut and paste.
cheers
Richard
July 31, 2015 at 7:14 am #481109Josue – just wanted to let you know I reached out the folks at cro.ma via the email on their site and got this:
Delivery to the following recipient failed permanently:
(Email address hidden if logged out)
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain cro.ma by cro.ma. [192.185.141.87].The error that the other server returned was:
550 No Such User Here”While I think the gist of the technical knowledge is valid and provides insight and guidance to the cause, his point about robots is out of date, just like his blog which seems to have been abandoned in 2012…
Thanks again – I know if we all put our heads together we can find the best solution. Right now I’m wondering what happens if I only restrict the index.php file in my theme folder and leave the CSS and JS files… anyone know how Google will handle that? I know SEO, but not so much about how crawlers actually chew their food….
July 31, 2015 at 8:09 am #481125Hi!
Yes, having read the Yoast article i’d suggest not blocking all theme resources, however i think index.php should not be read directly by crawlers (or visitors) because it will always result on a PHP error, you could try one of these two workarounds:
Redirect theme index.php to root (this will apply to all visitors), .htaccess code (you could extend this to child theme directories or plugins):
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /wp-content/themes/enfold/index\.php\ HTTP/ RewriteRule ^wp-content/themes/enfold/index\.php$ http://DOMAIN.com/ [R=301,L]
Or simply disallow only index.php in the theme folder, robots.txt code:
User-agent: * Disallow: /wp-content/themes/enfold/index.php
Regards,
JosueNovember 4, 2015 at 4:47 pm #530208 -
AuthorPosts
- The topic ‘Crawling Errors 500’ is closed to new replies.