3 ms·
It's really despicable that Google has decided there is a single way that the Internet must be used, and that if you don't abide by their rules they can use the
by saurik 15y ago
It's really despicable that Google has decided there is a single way that the Internet must be used, and that if you don't abide by their rules they can use their near-monopoly on both search (discovery) and advertising (revenue) to entirely exclude you from it. We are now living in a world where Google has managed to replace the URL bar for 99% of users with a search box (whether or not the URL bar actually is a search box, which it now actually is in many browsers).
Hell, I myself am guilty of not bothering to type in URLs anymore (yes, just like those poor people who used to search "Facebook login" and one day got highly confused when an article about logging in to Facebook that happened to support Facebook Connect to leave comments ranked higher): I just search for things like "cdnetworks portal" and "1and1 client login"; I even, and I shit you not, do a Google search using the Chrome OmniBar for "google images", as I don't remember what the URL for that part of Google is.
[edit: As adgar correctly points out below, the following paragraph is a misunderstanding of the mechanism that was used by this website to implement this split-test algorithm. However, it seems fairly obvious to me that the mechanism used to implement the split test does not matter. Meanwhile, the reason I went in this direction is due to Matt Cutts specifically stating the trade-off in the below paragraph on the Google webmaster video series; it is not because I assumed something from this article's conclusions.]
Seriously... there is /nothing wrong/ with a site choosing to A/B test people by returning different results from the server, and yet Google insists that doing so is somehow harmful and that it would be better to wait entire extra round-trips to do client-side testing using JavaScript, a process that in the end is not only a worse experience for the user and a more complex and less secure mechanism for the developer but has /the exact same fundamental behavior that Google claims is evil/.
It is /exceptionally/ irritating as their rules may have some (highly arguable) philosophical purity, but in the majority of cases leads to a /worse result/. For example, it would be /much more correct/ for sites like Hacker News to mark that the comment/title at the top of each page "is what search engines are allowed to see and index" and that the rest of the comments below it are "ancillary content that absolutely must not be indexed". Otherwise, when you search for a comment using Google, you find every single point along the tree that connects from that comment up to the root of the page, as the comment is present on all of them.
I found myself thinking about these issues a lot recently while working on writing some custom forum software, and even went and skimmed through every single Google web masters video that Matt Cutts put out, and the end result simply made me angry: I was finding myself purposely designing worse things so that they could be "indexed better", and when I'd look at what I was doing and go "this is nuts: is Google really that important?" I'd have to sigh and sadly remind myself "yes, it probably is".
- adgar 15y ago> Seriously... there is /nothing wrong/ with a site choosing to A/B test people by returning different results from the server, and yet Google insists that doing so is somehow harmful and that it would be better to wait entire extra round-trips to do client-side testing using JavaScript, a process that in the end is not only a worse experience for the user and a more complex and less secure mechanism for the developer but has /the exact same fundamental behavior that Google claims is evil/. Halfway through your rant, you clearly demonstrate that you did not bother to adequately understand the linked article before ranting about Google, throwing words around like "evil" and "despicable" without even knowing what you are ranting about, like so very many well-intentioned but woefully ignorant commenters in today's technorati. FTA, emphasis mine: > [The split-page approach used] is sort of a hybrid of Client-side and Server-side variations. Here’s how it works. Let’s say you want to test your landing page at yourdomain.com/landinag-page. You would create additional pages and using javascript, the visitor would be redirected to one of the pages. You seem to have completely misunderstood what the author was saying. Naturally, since you are both misinformed and critical of Google, that makes you the most highly upvoted comment on today's Google Hacker News thread!
- saurik 15y agoCan 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).