3 ms·
Can you please explain to me how this oversight on my behalf makes the situation better? Does the fact that Google is also disallowing client-side A/B testing o
by saurik 15y ago
Can you please explain to me how this oversight on my behalf makes the situation better? Does the fact that Google is also disallowing client-side A/B testing of this fashion cause it all to make sense? Seriously: you can tell me I misunderstood the article (which I will happily admit I skimmed: I read the various paragraphs as "different common mechanisms for implementing split tests", one per paragraph), but can you honestly tell me that this misunderstanding would have changed anything about my rant, excepting possibly making Google come off even worse?
http://www.youtube.com/watch?v=xepQgGcit2A#t=3m23 http://www.youtube.com/watch?v=xepQgGcit2A#t=3m23
^ This is the reason why I went in that direction, by the way. This is a video from Matt Cutts, one of the many that I sat through watching during a massive five-hour- MattCutts-and-GoogleWebmasterHelp -a-thon that I force myself through a week or two ago. I am hotlinking to 3:23 into the video as this video answers multiple questions (as is common on the MattCutts channel, as opposed to on GoogleWebmasterHelp, where each question tends to get its own video).
In this question's answer, it is clearly stated that Google may very well consider the same page returning different loads of the page for purposes of A/B testing as "cloaking", and that webmasters should instead use client-side mechanisms to perform these tests. If tests /are/ done, it is claimed that the webmaster should only do so on areas of the site that are not being indexed (which may involve explicitly telling Google to stop indexing that part of your site).
- fpgeek 15y agoYour rant doesn't make sense because your starting point "Google is evil and despicable for making rules for the Internet" is incoherent. Both Google's action and Google's inaction "make rules for the Internet". In an alternate universe where Google didn't implement this penalty, attacks using this kind of client-side redirection could easily be common and a serious problem. In that universe, alternate-saurik could come to Hacker News and complain that "Google is evil and despicable for not clamping down on these client-side hacks that are almost always used by attackers, not legitimate developers." Google has to make choices. Those choices are going to feel like "rules for the Internet" for many people they influence. That's unavoidable. If you're going to criticize Google for this sort of issue, you need to focus on the details of those choices. In this case, your lack of attention to detail makes it clear you're not making a credible case.
- saurik 15y agoIn my rant I provided a specific example of how Google's rules regarding content cloaking make it difficult to search or build sites like Hacker News (and will now further point out that Yahoo provides that feature); I have also provided evidence that Google disrecommends doing A/B testing using some mechanisms as it may be considered cloaking, and that webmasters should first deindex their content from Google. I can even, if you demand, find other videos from Google (also from Matt Cutts) that show that the heavily-hedged suggestion in this video to serve different content from the server (even small snippets of text, such as titles or breadcrumbs) that is not based on IP address (and thereby might not be stable for GoogleBot) is also highly dangerous and can lead to Google believing that you are cloaking. I therefore take issue with the fact that, once I misunderstood this specific article, that somehow means that all of the other research that I've done on this matter, and even the arguments that I state in my rant (where the specific paragraph that is currently under contention I am backing up with evidence outside of this single article, which is from someone none of us have ever heard of and for all we know could be lying about what Google did anyway) are now void.
- saurik 15y ago(Also, if you spent any time at all to look into who I am, what I do, or the things that I stand for, you'd realize that your appeal to alternate-saurik in a world where Google built an open system that was capable of being abused doesn't really have much basis, and is honestly a little insulting.)
- Matt_Cutts 15y agoHi saurik, that's one of the earliest videos I ever taped, back in 2006: http://www.mattcutts.com/blog/more-seo-answers-on-video/ http://www.mattcutts.com/blog/more-seo-answers-on-video/ I had to move that video over from video.google.com, which is why the YouTube date appears more recent. I should probably make a new video or blog post about A/B testing, but I can try to summarize here. In the original video, I said: - it's nice if you can A/B test on a part of your site that Google doesn't see. Then it's a moot point for us. - failing that, it's helpful to do something server-side. - don't do anything special for Googlebot. The state of A/B testing has evolved quite a bit in the last six years though. If I were making a fresh video, I'd say: A/B testing is a perfectly fine thing to do. You can do A/B testing via either server-side or client-side technology. In both cases, don't do anything special or different for Googlebot. Treat Googlebot just like any other user and don't hard-code our user-agent or IP address. If you have any other questions, refer to http://support.google.com/websiteoptimizer/bin/answer.py?hl=en&answer=72507 http://support.google.com/websiteoptimizer/bin/answer.py?hl=... or http://www.youtube.com/watch?v=QHtnfOgp65Q http://www.youtube.com/watch?v=QHtnfOgp65Q to review best practices and avoid actions that search engines could potentially view as cloaking.