|How to get rid of Smartphone specific URL errors in Google Webmaster Tools||princejindal8||12/24/13 12:30 AM|
I've read the FAQs and searched the help center and couldn't find any specific answer.
The website URL is - HealthyCeleb.com
I am seeing 25 Blocked URLs (all with replytocom parameters) in the "Crawl Errors" section of the Google Webmaster Tools (GWT) in Smartphone specific tab. There are 29 server errors (with mostly 500 error codes with little bit 503) and currently 1 Soft 404 Error (URL with replytocom parameter).
All these URLs, when I fetch with the tool "Fetch as Google" show me a "Success" and still I am seeing them. I am seeing no error (other than 404 Not Found) in the Web tab in GWT.
Almost 20 days have passed and I am doing "Fetch as Google" and still I am seeing these errors.
I actually blocked replytocom parameter in robots.txt on around Dec 4, 2013, but I removed the setting after almost 24 hours as I noticed this is not the good way to stop Googlebot to noindex the replytocom URLs. So, now these stubborn crawl errors in blocked category are reducing the website traffic and I want to get rid of them.
Additionally, I have made the "replytocom" parameter set to "No URLs" in the URL parameter settings page in GWT with the effect of "paginates". And, enabled the option "Remove the
The 29 server errors and 1 soft 404 error is also giving me "Success" on using "Fetch as Google" tool, but the crawl errors are not getting removed from there.
Any suggestions on how to get rid of these URL errors?
|Re: How to get rid of Smartphone specific URL errors in Google Webmaster Tools||princejindal8||12/24/13 6:37 AM|
Is there nobody here to help me out?
|Re: How to get rid of Smartphone specific URL errors in Google Webmaster Tools||cristina||12/24/13 10:45 AM|
Can you post some screenshots with the errors stats?
|Re: How to get rid of Smartphone specific URL errors in Google Webmaster Tools||princejindal8||12/24/13 11:54 AM|
Here is the screenshot for one of the URL already been fetched by Googlebot Mobile.
|Re: How to get rid of Smartphone specific URL errors in Google Webmaster Tools||JohnMu||12/25/13 9:32 AM|
Crawl errors will drop out on their own once they're recrawled & reindexed normally. You don't need to do anything special for that :)
|Re: How to get rid of Smartphone specific URL errors in Google Webmaster Tools||princejindal8||12/25/13 9:54 AM|
Thanks John for replying.
But, when those errors will be dropped?
Web based crawl errors are dropped every 24 hours, if I fix them.
But the smartphone specific errors aren't decreasing, instead, they increase after unequal intervals of time. However, the errors which Googlebot for mobile finds are not actually errors. They are always fetched with success, when I try to do that.
Once again thanks for clearing the things. I also hope the same.
|Re: How to get rid of Smartphone specific URL errors in Google Webmaster Tools||JamesParker||12/26/13 5:53 PM|
I have the same problem with Smartphone error URLs, plus two other problems:
The first, I have removed some error pages, everyday the same URLs are listed again, and you can remove the same URL for 10 times, 20 times, for unlimited times.
The second problem; I have added one directory to my robots txt file and still I have error pages from this directory!
|Re: How to get rid of Smartphone specific URL errors in Google Webmaster Tools||smarterror||1/1/14 1:50 PM|
I have no pb with web desktop crawling but I have the same problem too in webmastertools with smartphone crawling it's annoying me a lot because it last for weeks besides my whole site ranking has fallen deeply since i got an 503 unavailable error. Since i resolved any error (500,503) and my site is back online without any downtime, i don't get any improvement.
Please help us!!!
|Re: How to get rid of Smartphone specific URL errors in Google Webmaster Tools||Drew Dowdell||1/6/14 6:17 PM|
But they keep coming back when I mark them as fixed. I've verified they are working by fetching as Google:Smartphone....
In my case, the number of them is increasing, but when I test the recently added errors, they do work properly.