Can A/B Testing Cause An SEO Problem?

Aug 21, 2009 - 8:33 am 7 — by

A/B testing is the process of setting up two or more styles for a page, for the same piece of content. For example, let's say you had a page where you sold blue widgets and you wanted to try using a blue button versus a red button to buy the widget. What you can do is A/B test the two types of buttons against each other.

How would you accomplish this? Well, you can send 50% of your traffic to example.com/widget.html?button=red and the other 50% to example.com/widget.html?button=blue and see which page converts better. But that can lead to duplicate content, i.e. the same URL, example.com/widget.html with three URLs for the same content. Or would it? Google and some search engines are smart enough to pick up on this. There are other ways to test this using JavaScript (potential cloaking issue?) or CSS or use Google Website Optimizer.

How would you handle it? That is the question asked in a WebmasterWorld thread. Honestly, I am not sure what the "best" method to handle this is. So please join the thread or comment here.

Forum discussion at WebmasterWorld.

 

Popular Categories

The Pulse of the search community

Google Search Volatility

More Details

Search Video Recaps

 
Video Details More Videos Subscribe to Videos

Most Recent Articles

Google Search Engine Optimization

Google Search Console Generative AI Performance Report Data Bug Nov 9 - 11

Nov 12, 2026 - 2:55 pm
Google

Google Search Gets Massive Upgrade With Gemini 4 Hydrogen

Nov 12, 2026 - 1:20 pm
Google Search Engine Optimization

New Google Help Doc Explains How To Identifying Traffic From Google Search

Nov 12, 2026 - 12:08 pm
ChatGPT Ads

OpenAI ChatGPT Ads Updates: Intelligent Bidding, New Cost Targets, Geo-Flexibility & Product Set Filters

Nov 12, 2026 - 11:38 am
Search Forum Recap

Daily Search Forum Recap: November 12, 2026

Nov 12, 2026 - 10:00 am
Google Ads

Google Ads New Invalid Traffic (IVT) Overview Card

Nov 12, 2026 - 8:00 am
Previous Story: Daily Search Forum Recap: August 20, 2009