We’ve gotten several questions recently about whether website testing—such as A/B or multivariate testing—affects a site’s performance in search results. We’re glad you’re asking, because we’re glad you’re testing! A/B and multivariate testing are great ways of making sure that what you’re offering really appeals to your users.
Website testing is when you try out different versions of your website (or a part of your website), and collect data about how users react to each version.
A/B testing is when you run a test by creating multiple versions of a page, each with its own URL. When users try to access the original URL, you redirect some of them to each of the variation URLs and then compare users’ behaviour to see which page is most effective.
Multivariate testing is when you use software to change differents parts of your website on the fly. You can test changes to multiple parts of a page—say, the heading, a photo, and the ‘Add to Cart’ button—and the software will show variations of each of these sections to users in different combinations and then statistically analyze which variations are the most effective. Only one URL is involved; the variations are inserted dynamically on the page.
tedster
10:29 am on Aug 10, 2012 (gmt 0)
The key part of this article for me is beyond the definition of those terms - it's the advice for SEO itself:
No cloaking
Use rel="canonical"
Use 302s, not 301s
Only run the experiment as long as necessary
deadsea
11:27 am on Aug 10, 2012 (gmt 0)
Despite what the article says, I would recommend cloaking when running multivariate testing.
I always serve Googlebot the version that the most users are seeing. It may be technically cloaking, but the spirit is in the right place. I believe that it is less likely to get you penalized than randomly showing Googlebot different pages every time it visits.
abhishekmishra
12:00 pm on Aug 10, 2012 (gmt 0)
I seen in mostly Google Webmasters update's Google do
"Old wine in new bottle's"
Because if anybody will look at Google webmaster guidelines they know these common things; Like... *No cloaking *Use 302s, not 301s etc.
tedster
12:10 pm on Aug 10, 2012 (gmt 0)
In many cases, we need to use a 301 when we redirect, not a 302. I'm happy for this clarification from Google.
[typo fixed]
[edited by: tedster at 2:15 pm (utc) on Aug 10, 2012]
netmeg
12:33 pm on Aug 10, 2012 (gmt 0)
(I need a clarification from you - was one of those supposed to be a 302?)