7 ms·
On 29 June 2018, we posted an question about this on Google's Webmaster Central Help Forum: https://productforums.google.com/forum/?hl=en#!topic/webmasters/YO0
by ap_org 8y ago
On 29 June 2018, we posted an question about this on Google's Webmaster Central Help Forum:
https://productforums.google.com/forum/?hl=en#!topic/webmasters/YO0jYLfb-VM;context-place=forum/webmasters https://productforums.google.com/forum/?hl=en#!topic/webmast...
- JackCh 8y agoAre you aware that your website cannot be accessed from many Tor exit nodes without solving a google captcha?
- ap_org 8y agoYes, and we very much regret that. We're on a shared server, and our webhosting company recently added security software called Imunify360 that does this.
- pdkl95 8y ago(ack! accidentally submitted early; major edits included with this header) The hypothesis about how the "anti-" prefix is being parsed is interesting; deploying some type of updated (probably machine learning) ranking algorithm with wild and unpredictable consequences to random subjects of that algorithm is consistent with other environments like YouTube (random & unexplained demonetization, etc). However, this doesn't change much; the results are the same regardless. Google is responsible for the decision to de-rank antipolygraph either deliberately or indirectly with their design of the ranking algorithm. If it was due to an algorithm, this is another example of the need for algorithmic transparency. You don't get to abdicate responsibility for decisions simply because an algorithm was used; the choice of algorithm (and the data used as input) is itself a decision.