Switching Wordpress Blogs to Https Without Losing Social Proof

How to Switch WP Blogs to Https Without Losing Social Proof

Switching WordPress Blogs to Https Without Losing Social Proof

Switching your blog to https has a significant impact on the social proof related to all published posts.

While the share count buttons for Twitter and LinkedIn will preserve the figures they previously displayed, the buttons for Facebook, Google+, Pinterest and Stumbleupon will reset to zero.

That’s because the latter social media networks don’t consider https pages as being the same thing as their relevant http versions.

As a consequence, these four networks track two sets of share counts for the same blog: one set for http pages and the other for https pages.

How the Regular Social Sharing Plugins Work

Using a non-tech language, this is how a regular social sharing plugin works for each blog post:

1) The plugin checks what the exact address of the blog post is

2) The plugin asks the social network how many shares are counted for the blog post located at that exact address

3) The plugin displays on your blog post the response received from that social network.

The problem is that – as in real life – if you ask a wrong question or an incomplete question, you won’t get the most useful answer.

The plugins should ask two questions: how many shares are counted for the http address of a page and how many for the https version of the same page. Then the plugin should do the math and display the aggregate number of shares.

Most plugins don’t ask two questions though. And if you ask the customer support what’s wrong, you get the usual, “It’s not our fault, we’re just displaying the counts received automatically from that social media network API.”

Is There a Solution For Preserving Social Proof Though?

Recover Your Social Share Counts Using Social Warfare Plugins

Install Social Warfare. It’s one of the few social media plugins that has a social proof recovery feature.

Actually I found out only one more plugin that has a paid add-on for this feature. But I didn’t test it.

Because Social Warfare has more useful functions (such as preventing the addition of frames to your blog posts shared on Twitter by third parties).

After you install Social Warfare, go to the tab “Advanced” from the settings panel and there you’ll find the module “Share Recovery.”

Choose the following settings:

– Activate Share Recovery: ON
– Previous Connection Protocol: http

That’s all!

Please note that:

– the updated share counts won’t be displayed right after you activated Share Recovery feature. It will take up to 12 hours or so; however, if you want to get immediately the new share counts for a certain blog post, edit it and then refresh your browser.

– in order to keep the plugin counting the http shares, after the actual recovery don’t switch Share Recovery off.

When Is It Better to Install Social Warfare Plugin?

Before switching your blog to https or after?

I tested it on three blogs.

On two blogs I installed Social Warfare after I switched to https.

Comodo SSL Certificates

On both blogs I got a similar result: some blog posts did not get back their social proof related to some social networks.

On this blog I installed Social Warfare before switching to https.

I waited until Social Warfare displayed the social proof for all posts (it doesn’t happen instantly) and then I switched to https. None of my old blog posts lost the social proof.

Here’s why: Share Recovery feature combines its power with another SW feature …

One More Cool Social Warfare Feature

From time to time, API requests sent by social plugins fail and return zero share counts instead of the actual count.

In such a case, most plugins display zero shares. As if you lost all your shares overnight.

Instead of blaming the social network that provided the wrong answer, Social Warfare developers assumed that it is very unlikely to lose overnight all the shares for a certain network.

So they added this feature: if the share count received from a social network at a certain time is lower than the previously one, the plugin keeps displaying the higher one. Problem fixed.

Social proof is important for any blogger. Get your Social Warfare plugin now!

To Your Blogging Success!
Adrian Jock

Adrian Jock's
Internet Marketing
Tips & News
Wanna improve your internet marketing skills in order to make more money online? Subscribe to my newsletter. Period!
Bonus: my list of free tools and resources that I use in order to run this blog and all related activities ;)

13 thoughts on “How to Switch WP Blogs to Https Without Losing Social Proof

  1. Thanks for sharing!
    The above is nice article and common trouble for bloggers who are intending to switch to https. Of course, I installed SSL certificate last few months and faced what you’ve mentioned here. However, I’m using Social Share Button for WordPress and there is an option for recovering https url change. I’ve heard lots of people said about the social Warefare, but thanks for adding more information.
    Kimsea Sok recently posted: How to Get AdSense Account Approved After Published 4th Article

    1. Hi Kimsea,

      1) I checked the source code of one of your blog posts. Your plugin actually is called “Easy Social Share Buttons”

      2) Previously I didn’t test that plugin. But I tested it now quickly and it doesn’t seem to work properly on your blog ;)

      I checked two of your blog posts: “Reduce Your Mortgage with Our Tips” and “How to Create A Charity Blog That Works- 3 Critical Tips to Consider”

      For both blog posts, your plugin shows zero shares on Twitter. I checked both NewShareCounts API and Twitter. The reality is different: your posts have been shared and the real Twitter share count isn’t zero.

      So… no, the plugin that you use is not an alternative solution for recovering the social share counts. It doesn’t do the job ;)

    1. Hi Sanjeev,

      It’s not important how new your blog is. It’s important to analyze whether you lose something of value or not if you don’t recover your past shares.

      For example, if your past blog posts weren’t shared a lot, then you don’t lose too much. However, if some of your essential posts got thousands of shares and you have in place a way to capitalize such a good image, then it’s important to recover your past shares.

      That’s why recovering the past shares isn’t a must for everyone. It’s a decision to be taken by each blogger based on the actual situation of her or his blog and also based on blogger’s goals and plans.

      1. Hi Adrian,

        I agree people need to take call based on the number of shares on the post. I had few posts which have good number of shares and now they are showing 1-2 shares. I could have recovered them with Social Warfare.

        My current plugin does not support the recovery and the counts will start from scratch because most of the social networks treat http and https as two different url’s.

Your thoughts or questions are welcome. Leave a comment...

Your email address will not be published. Required fields are marked *

Note: Whether you read the Comment Policy or not, it still applies to your comments.
 

Warning: It's OK not to subscribe to getting notifications regarding the replies to your comment. However, if you're not interested in reading such replies and you don't subscribe to get 'em, then don't expect me to write 'em ;)

Tick the box to enable CommentLuv