Tarayıcınız güncel değil. Site düzgün görüntülenmeyebilir. Lütfen tarayıcınızı güncelleyin.

SplitSignal FAQ

What does the tool measure? Clicks, click-through rate, or rankings?

SplitSignal measures Organic Clicks (this includes clicks from Web, Image, News and Video search types) from domains connected to Google Search Console. Additional GSC data is available upon request for paid users. Have a suggestion on some other metrics? Feel free to contact splitsignal@semrush.com

Why are there minimums in order to run an A/B test? What are those minimums?

In order to run a test, we need a minimum of 300 pages and 100k clicks (on those pages) over the last 100 days. These thresholds guarantee that the test will have a statistical model that can support a significant result. In short, the more traffic and pages the domain has, the better the chances are for a statistically significant test. We may revisit these thresholds when more data becomes available.

How are the pages identified for the variants and controls?

SplitSignal splits the pages for you. It utilizes 100 days of historical clicks data to come up with two statistically similar groups of pages. Such split increases the accuracy of the test and controls to external factors like seasonality and spikes in clicks.

How do you know when the changes to the variant group URLs are visited by Google?

We provide an indicator of when the page was visited by GoogleBot once the Javascript snippet is installed (based on the URL information from Google Search Console). While we can’t be sure when Google will index the changes, in our experience, Googlebot visits about 60% of the pages during the first week and the rest of them in the next week. It may take a few days before changes appear on Google SERP after the page is visited.

SplitSignal FAQ image 1

What on-page changes can we test?

You will find a detailed answer in the dedicated article.

Can we run multiple tests at once?

Yes, you can run as many tests as your domain allows (as long as you have at least 300 pages per test and 100k in clicks to those pages). It is important to note that once a page is selected for a test, it cannot be selected for another test while it is still running with the first test. You would have to wait until the first test is complete or stopped in order to use that page again.

How does SplitSignal affect Core Web Vitals?

It is important to consider items like the impact of third-party code and Javascript execution time because this can indirectly affect your site's performance. We have yet to see any noticeable impact SplitSignal has had on any performance metrics, (from sites of 300k organic traffic monthly to 50m plus) but would welcome a Proof of Concept (POC) test to be run on either a staging or live site. For more information, contact the SplitSignal team at splitsignal@semrush.com

Can we preview what a test would look like before it goes live?
Yes! With our preview tool, you can see how the change would look to the user to ensure that not only Googlebot sees the change, but the user does as well. Our main stakeholder is Googlebot but we also highly value user experience and do not want that to be negatively affected. The preview tool available after JS code snippet is installed on the website.
What kind of information/data does SplitSignal have access to?
  • SplitSignal analyzes access logs of requests by SplitSignal’s JS snippet to improve the tools quality and for use in certain tool features (i.e. tracking Googlebot visits). The lifetime of logs data is 45 days. After 45 days, the logs are removed and SplitSignal no longer has any access to them.
  • SplitSignal or Semrush doesn't share any data related to your SEO split-testing with 3rd parties or other Semrush tools.
  • SplitSignal does not place any cookies onto the customer's browsers.
  • SplitSignal uses GSC data only for splitting pages before an SEO split-test. NOTE: Users can revoke access/connection to GSC at any time. More information is available in the official privacy policy statement.
How to install the JS snippet? 

To do this, you will need to add the JS snippet code to the HTML code of every page on your website.  You can do this either manually or using Google Tag Manager.

It is better to place the code as close to the top of the page as possible, inside <head> or <body> tags. This will allow the code snippet to load and apply the test changes faster.