• Resolved archon810

    (@archon810)


    Hi,

    How would Nelio work with W3 Total Cache in place, or any other caching really?

    Maybe it could implement support for W3TC’s fragment caching?

    Any other ideas?

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author David Aguilera

    (@davilera)

    Hi,

    Our plugin adds a testing parameter in the URL to identify the variation it has to load. Thus, for example, if you’re testing https://example.com/some-page/, the following URLs would “appear”:

    When the user accesses https://example.com/some-page/, a JavaScript added by our plugin kicks in, checks if the current page is under test (in this case, it would be), and performs a redirection so that the newly requested URL contains the testing parameter.

    Since cache plugins cache pages based on their URL, this means that the cache would be able to cache all the variations and serve different versions to different users.

    I hope this all makes sense.

    Regards,
    David

    Thread Starter archon810

    (@archon810)

    Thanks, this makes sense. I’m just trying to make sense of multiple title tests and canonical data that goes to the feeds, socials, Google News, Google Feed, etc. The main title, which would go to these places, is going to get an unfair advantage.

    I’m also unclear on Google Search. If there’s only one canonical url, it’s going to index just that title, without the variations. So who’s going to see the variations? Just people visiting the site already?

    Plugin Author David Aguilera

    (@davilera)

    I’m just trying to make sense of multiple title tests and canonical data that goes to the feeds, socials, Google News, Google Feed, etc. The main title, which would go to these places, is going to get an unfair advantage.

    It depends on the exact URL that’s being shared in Social Media. If the shared URL is https://example.com/tested-page/, then yes, the original title (and content) will be shared. If, on the other hand, a URL such as https://example.com/tested-page/?nab=1 is shared, then the first variation’s title (and content) will be shared. But you’ll be usually sharing the original URL so… yup, original content gets an “unfair advantage”, even though that’s an arguable claim.

    Here’s the thing: in most tests, it doesn’t really matter what you share on social media. You’re interested in testing the page and seeing which variation converts the best. Therefore, the test doesn’t care about how people landed on the page; all it cares about is the ratio between “how many people has seen each variation (a view)” and “how many people was converted from each variation (a conversion)”.

    This has an exception, though: headline tests. Headline tests are intended to test “which title, featured image, and excerpt attract more visitors”. So a “view” occurs whenever a user sees the title, featured image, and excerpt of one of your posts somewhere in your blog (for example, your in Blog listing or in a Related Posts widget), and a “conversion” occurs when the user actually accesses the tested post. In this particular case, you might be interested in knowing which variation attracts more visitors from social media (a “view”) to your blog (the “conversion”), but this is something that’s out of the scope of our plugin, as Nelio A/B Testing can’t know how many times a certain headline was shown to a visitor outside WordPress.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘W3 Total Cache support in Nelio?’ is closed to new replies.