I've got rid of robots.txt error
Yesterday I had this error in robots.txt
<script src="//mysite.com/hashcash.js" type="text/javascript"></script>
see my yesterday blog:
https://my.wealthyaffiliate.com/dorina62/blog/robo...
After I read a lot of articles about robots.txt and test it in Search Console for my second site( because it is not so big), I reached the conclusion that none is blocked!
If you want to play just put the second part for your URL and test it in Search Console:
You can see where I highlighted GoogleBot-News, GoogleBot-Images,etc.
It is no need to do this, but I did it.Only if you write your robots.txt and you do not allow them to have access for your images, for ex., you can do like this.
You can see for these theme details in the article, to have a general idea:
https://www.elegantthemes.com/blog/tips-tricks/how...
I used http://smallseotools.com/website-seo-score-checker... to see what do they say about my robots.txt
So, it looked good but the error was there, an error with Warning 0, I did not worry about, but I remember I tested my site with a tool( I can't remember tool right now but I'll look for it, too many, sorry) and this tool warned me a have an error with robots.txt.
For my first site I manually put in Stargazer theme the alt text for gravatar:
https://my.wealthyaffiliate.com/training/how-to-ad...
but for my second site the theme Dark Elements had the alt text in it?( so no need to add manually)!
But I found "America", I found Virtual Robots.txt plugin, which solved my problem!
The plugin wrote properly robots.txt
you can see this in preview your robots.txt file here, I did not change anything in Settings for this plugin
I went to Search Console, I did a Fetch and Render for my site, and after doing this the robots.txt error dissapeared!
I installed the plugin for my first site, too, after I did a Fetch and Render the error is not there, too!
You must keep this plugin active!It is a very light plugin according with P3!
Recent Comments
25
Hi Liz
- just a note
I have the same issue, but before I do anything I will PM Kyle because I looked up hashcash.js and it has something to do with preventing spam in comments.
Now, for me this problem was never an issue until just recently, after Carson's announcement about the new "spam" protection here at WA.
I wonder if they are connected and do not want to proceed in getting rid of it until I check with Kyle.
I'll PM Kyle later - too busy at the moment.
When I get an answer I'll let you know. Only my websites hosted at WA have that error - not outside hosting.
The hashcash.js is NOT an error. You can totally ignore that, it will be unique to Google because they have never seen it before, but it is very sophisticated and powerful technology used to prevent spam and attacks on your website (and speeds it up drastically).
Completely ignore this error in Google if you get it, they will deem things quite often as errors that actually aren't (simply because they don't have an understanding of other people's sites and how different website platforms operate).
I think it came from gravatar, after I did this for how to add an alt text to your Gravatar my first site this error was there
For my second site, it was not necessary to do this, because the author of the theme did it, the error was present. I think it comes from that hash we have in our comments.
See more comments
Hi Dorina,
We've made a network change that will correct this issue for all Robots.txt files. All Google Webmaster Tools errors or warnings related to this will be gone now.
There is nothing that anyone needs to do, we've made the changes on the network side.
An error or warning from WMT for your Robots.txt file will never affect rankings or your site trust with Google, they are just suggestions...and we've corrected the suggestions. Thanks for being our eyes and ears on this one!
Cheers,
Carson
Thanks, I deactivated the plugin for both sites after I read Kyle's message! I'm glad we are very safe in WA thanks to great work you and Kyle do.
OK but if you were using a plugin to mange your robots.txt file, you can turn it back on if you wish. The issue was in the implementation of our SiteProtect system - an easy solution that is now live across the network.
OK, I'll check in Search Console robots.txt in a while, this plugin is a light one so if you say is better to live it, I will!
The error is not there! It is no need to activate the plugin!