How to do A/B split testing for SEO?

Table of contents

How to do A/B split testing for SEO?
How to do A/B split testing for SEO?

To achieve success in SEO, we want to possess an understanding of how users engage and interact with the websites that we manage.

One way we are able to do that is by running tests that show us what users want from our sites and the way they react to the content on our pages.

Website testing allows us to experiment with ways to extend conversion rates and UX by comparing an impression page against a test group to investigate the performance impact supported changes made.

This is something that search engines are pleased with because they need to direct visitors from their SERPs to sites that may provide them with a positive, seamless experience.

It’s a win-win situation.

In this article, our SEO experts have shared some tips that can help you perform A/B split testing for SEO. They include:

1. Ensure Google Is Served the first Content of a Page that you simply Want to Rank With

2. Don’t Create Pages That Are Too Distinctly Different From each other

3. You can use the rel=”canonical” Tag for Pages That Have Different Test URL Variations

4. Use caution When Using Noindexing or Blocking Test URLs

5. Use 302 which Redirects When Running Split Tests That Involve Redirection

6. Retain the initial Page and Make Content Updates There Where Possible

Before we get into the small print of the dos and don’ts of website testing, let’s take a better look at A/B testing and multivariate testing and therefore the key differences between them suggests our Jacksonville SEO experts.

What is SEO A/B testing and the way to style SEO split-tests?

Knowing what impact a change to your website has had on organic traffic from search engines is often challenging to live.

Merely making a change to your website and searching at the impact of metrics like rankings and click-through rates (CTR) isn’t ok.

Unless you’re able to control for external factors, there’s no way of knowing whether the changes in rankings or CTR are due to the change you made or other external factors.

Making a change and reviewing metrics is usually spoken as before and after testing. While before and after testing is healthier than not measuring anything in any respect, it’s not a controlled test and you can’t use it to draw firm conclusions. It’s easy to be misled and think that your change was chargeable for the observed impact.

In addition to not having a bearing group of pages in before and after testing, the actual fact that the length of your time it takes for search engines to crawl your site and take the changes into consideration is additionally unpredictable and complicates the analysis. It might be instant or it could take weeks. This produces observing data, like traffic or rankings, and trying to line it up with a change you made near impossible.

Controlled SEO split-testing is once you split a bunch of statistically similar pages into control, and variant groups then make a change to the variant pages.

You can compare the organic performance of both groups against one another and against an expected forecasted level of traffic had no change been made to the positioning.

Below I’ll walk you through how the SEO A/B testing process works, share some case studies and answer some commonly asked questions.

What forms of websites can run SEO experiments?

Some websites, and parts of internet sites, aren’t suitable for running SEO split tests. To be able to run tests, there are two primary requirements:

  • You need plenty of pages on the identical template.
  • You need plenty of traffic.

How much traffic? That’s an honest question, and it depends on your website. Generally speaking, the more stable your traffic patterns are, the simpler it’ll be to run experiments with less traffic. The more irregular the traffic to your website is, the more traffic you’ll have to build a sturdy traffic model.

In general, SEO experts work with sites that have a minimum of many pages on the identical template and a minimum of 30,000 organic sessions per month to the group of pages you would like to check on. This doesn’t include traffic to one-off pages like your homepage.

Is it possible to check if you’ve got less traffic? Some people do test on sections of their site that only get a pair of thousand sessions per month, but the changes in traffic have to be much higher to be ready to reach statistical significance.

The more traffic and more pages you have got, the better it’ll be to achieve statistical significance and also the smaller the detectable effect is.

The benefits of A/B testing for SEO

Earlier within the year, the Pinterest engineering team wrote a desirable article about their work with SEO experiments which was one amongst the primary public discussions of this system that has been in use on a variety of enormous sites for a few time now.

In it, they highlighted two key benefits:

1. Justifying further investment in promising areas

One of their experiments concerned with the richness of content on a pin page:

  • For many Pins, we picked a much better description from other Pins that contained the identical image and showed it additionally to the prevailing description. The experiment results were far better than we expected … which motivated us to take a position more in text descriptions using sophisticated technologies, like visual analysis.
  • Other experiments didn’t show a return, then they were able to focus rather more aggressively than they’d otherwise be ready to. within the case of the main focus on the outline, this activity ultimately resulted in almost a 30% uplift to those pages.

2. Avoiding disastrous decisions

For the non-SEO-related UX reasons, the Pinterest team really wanted to be able to render content client-side in JavaScript. Luckily, they didn’t blindly roll out a change and assume that their content would still be indexed just fine. Instead, they will make the change only to a limited number of pages and track the effect. After they saw a major and sustained drop, they turned off the experiment and canceled plans to roll out such changes across the positioning.

In this case, although there was some ongoing damage done to the performance of the pages within the test group, it paled compared to the damage that might be done had the change been unrolled to the entire site without delay.

How does A/B testing work for SEO?

Unlike regular A/B testing that several of you’ll be at home with from conversion rate optimization (CRO), we can’t create two versions of a page and separate visitors into two groups each receiving one version. There’s only 1 googlebot, and it doesn’t like seeing near-duplicates (especially at scale). It’s a foolish idea to make two versions of a page and easily see which one ranks better; even ignoring the matter of duplicate content, the test would be muddied by the age of the page, its current performance, and its appearance in internal linking structures states the experts from Jacksonville SEO Company.

Instead of creating groups of users, the type of testing we are proposing here works by creating groups of pages. This is often safe — because there’s only 1 version of every page, which version is shown to regular users and googlebot alike — and effective because it isolates the change being made.

In general, the method should look like:

  • Identify the set of pages you wish to boost
  • Choose the test to come across those pages
  • Randomly group all the pages into the control and variant groups
  • Measure the resulting changes and declare a test successful if the variant group outperforms its forecast while the control group doesn’t

All A/B testing needs a particular amount of fancy statistics to know whether the change has had a sway, and its likely magnitude. Within the case of SEO A/B testing, there’s an extra level of complexity from the actual fact that our two groups of pages don’t seem to be even statistically identical. Instead of simply having the ability to check the performance of the 2 buckets of pages directly, we instead must forecast the performance of both sets, and determine that an experiment could be a success when the control group matches its forecast, and therefore the variant group beats its forecast by a statistically-significant amount.

Not only does this deal with the differences between the groups of pages, but it also protects against site-wide effects like:

  • A Google algorithm update
  • Seasonality or spikes
  • Unrelated changes to the positioning

How long should tests run for?

One advantage of SEO testing is that Google is both more “rational” and consistent than the gathering of human visitors that decide the result of a CRO test. This suggests that (barring algorithm updates that happen to focus on the thing you’re testing) you must quickly be ready to ascertain whether anything dramatic is going on as a result of a test.

In deciding how long to run tests for, you initially have to choose an approach. If you merely want to verify that tests have a positive impact, then because of the rational and consistent nature of Google, you’ll take a reasonably pragmatic approach to assessing whether there’s an uplift — by trying to find any increase in rankings for the variant pages over the control group at any conversion deployment — and roll that change out quickly.

If, however, you’re more cautious or want to live the dimensions of impact so you’ll prioritize future varieties of tests, then you would like to fret more about statistical significance. How quickly you may see the effect of a change could be a factor of the amount of pages within the test, the number of traffic to those pages, and also the scale of impact of the change you’ve made. All tests are visiting differ.

Small sites will find it difficult to induce statistical significance for tests with smaller uplifts — but even there, uplifts of 5–10% (to that set of pages, remember) are likely to be detectable in an exceedingly matter of weeks. For larger sites with more pages and more traffic, smaller uplifts should be detectable.

Is this a legitimate approach?

As our SEO experts outlined above, the experimental setup is meant specifically to avoid any issues with cloaking, as every visitor to the positioning gets the precise same experience on every page — whether that page is a component of the test group or not. This includes googlebot.

Since the intention is that improvements we discover via this testing form the idea for brand spanking new and improved regular site pages, there’s also no risk of making doorway/gateway pages. These should be better versions of legitimate pages that exist already on your site.

It is obviously possible to style terrible experiments and do things like stuffing keywords into the variant pages or hiding content. This can be inadvisable for A/B tests because it is for your site generally. Don’t do it!

In general, though, whereas some years ago I would be worried that the winning tests would bias towards some variety of manipulation, I believe that’s less and fewer likely to be true (for context, see Wil Reynolds’ excellent post from early 2012 entitled how Google makes liars out of the great guys in SEO). Specifically, I feel that sensibly-designed tests will now effectively use Google as an oracle to find which variants of a page most closely match and satisfy user intent, and which pages signal that to new visitors most effectively. These are the pages that Google is seeking to rank on, and whether we are pleasing algorithms designed to please people or pleasing people directly isn’t too important — we’ll converge on the proper result.

What’s the difference between user A/B testing and programme A/B testing?

What’s the difference between user A/B testing and programme A/B testing?
What’s the difference between user A/B testing and programme A/B testing?

By far, one in every of the foremost common questions we get is a few versions of:

“Isn’t this just the same as user testing?”

That’s not surprising given product teams and marketers are doing user A/B testing for a protracted time, but there are some key differences.

Test design

Testing for users is comparatively simple. you create two versions of a page you would like to check, and your testing platform will randomly assign users to either the A or B version of the page.

Users metrics like conversion rate are then compared, and a winner is declared if there’s a statistically significant difference between the 2 pages.

We can’t do SEO A/B testing in this way for a pair of reasons:

  • Splitting the pages, not people: The “user” that we are testing for is Googlebot, not human users. Which means it’s impracticable, for example, to separate 10,000 “Googlebots” into control and variant randomly. There’s just one Googlebot. you furthermore may can’t make two versions of one page because it might cause problems like duplicate content. That’s why for SEO testing, we break a bunch of pages into control and variant pages as hostile splitting users.
  • Bucket selection: users are often assigned to regulate or variant pages arbitrarily. That’s not ideal with SEO testing. If you were to bucket pages randomly, you may find yourself with all of the favored pages in one group, which can skew results. it might even be harder to account for external factors. The 2 groups of pages must have similar levels of traffic and be statistically kind of like one another.  

Tips for Improving Your Tests & Processes

To keep search engines happy while we’re running these tests for our users, we have put together some key best practice tips to form sure that you just can continue testing to maximize the performance of your site, without damaging it within the process.

1. Ensure Google Is Served the first Content of a Page that you simply Want to Rank With

If you have got a variant page where a piece of key body copy has been removed, when the computer program accesses the page, nothing is left with which to assess the topic of a page and what it should rank for.

This will also apply to instances where you’re swapping out sections of content. I have seen tests where blocks of copy from subcategory pages were being inserted into the homepage, which caused cannibalization issues because the homepage started ranking for key terms related to those lower-level pages.

Carefully assess key elements like title tags, body content, internal links, and images, and ensure search engines can access a version of the page where these remain intact.

The most important question to ask yourself about your website tests: will this affect how Google can crawl, understand, and index the content on the page?

Changing the scale of the checkout button won’t affect this, but swapping out an H1 might, as an example.

2. Don’t Create Pages That Are Too Distinctly Different From each other

Don’t Create Pages That Are Too Distinctly Different From each other
Don’t Create Pages That Are Too Distinctly Different From each other

Search engines are able to detect when there are minor changes between pages for testing purposes, and in point of view with the users these changes doesn’t haven’t any problem with this.

However, if the page variations differ drastically, this might be flagged as cloaking and earn you a manual action.

The page that search engines find yourself accessing should match the first topic of the first page.

If your original page was targeting restaurant keywords, but the variant page is about life assurance, then this might be an enormous red flag for search engines.

3. You can use the rel=”canonical” Tag for Pages That Have Different Test URL Variations

If you’re running tests that make multiple page variants on separate URLs, Google recommends adding a canonical tag to specify the initial page that ought to be indexed.

This helps to avoid search engines choosing another duplicate test page to index rather than the first page.

The canonical tag is just a symptom and not a directive, so ensure other elements like your internal linking and sitemap URLs consistently point to the initial page, moreover to relinquish search engines a transparent picture of which page should be indexed because of the primary version.

4. Use caution When Using Noindexing or Blocking Test URLs

Adding a noindex tag to a page in an exceedingly set of duplicate pages is risky.

This is because Google will pick its own canonical tag supporting the opposite signals from your website, and it’d pick a variant URL instead of the initial URL because the one to index and show in search.

If you’ve noindexed this variant URL, however, Google will drop that page from the index and no version is going to be shown in search because the remainder of those pages will be grouped together as duplicates.

This has the identical effect as not indexing your original canonical page says the Internet Marketing Service providers. Also, avoid blocking test pages via robots.txt as search engines must see the differences between page variations to be able to respect canonical tags.

Blocking test pages during a robots.txt file could constitute as cloaking if you’re stopping search engines from seeing a test page version for users that differs greatly from the version they will access.

As long as you follow the remainder of the information during this article, there shouldn’t be an issue if program bots find themselves crawling your test page variants.

5. Use 302 which Redirects When Running Split Tests That Involve Redirection

Using a 302 redirect between your test URLs for A/B testing tells search engines that the redirect is temporary and therefore the original control page should be kept within the index, instead of indexing the test page that it’s redirecting to.

Using 301 redirects would explain to search engines that they ought to pass link equity and page signals to the variant page, and replace the first page within the index.

6. Retain the initial Page and Make Content Updates There Where Possible

Retain the initial Page and Make Content Updates There Where Possible
Retain the initial Page and Make Content Updates There Where Possible

It’s important to preserve all link equity that has been built for a page by maintaining the prevailing URL and making any required content changes off the rear of your tests thereto page.

If you run tests that involve separate URLs, don’t just flip the old page and leave the new one live instead if the variant performs better.

Update the prevailing page with the changes that appeared on the new page version.

If there isn’t a choice to update the present page, then confirm you add a 301 redirect to the winning variant page.

This will make sure that the bulk of ranking signals are passed across, and can prevent page duplication by leaving them both live.

When left unchecked, A/B and multivariate tests can negatively impact how computer program crawlers interact along with your site, and ultimately, your rankings in organic search.

However, these tests are still crucial for locating opportunities for increasing conversions and website performance.

By following the ideas outlined in this article and running your tests with SEO best practices in mind, you’ll be able to make the foremost of the advantages that website testing must offer – without hurting your rankings.