How to Recover Facebook Shares After Moving to HTTPS/SSL

If you’ve lost your Facebook shares because you move your site to HTTPS/SSL, this article is just for you

Websites with a lot of Facebook likes are bound to lose some likes when they move their site to https. That is because Facebook sees your https URL as a completely different URL. You can’t move the likes, shares or comments directly to the new URL but you can use the old URL as the canonical source for the number of likes or shares at the new URL.

How Facebook see your page?

When resolving which URL a like or share action should be attributed to, Facebook uses a process to resolve the canonical URL for URL that’s been loaded. When a URL is loaded, the crawler will look for:

  1. A HTTP 301 or 302 Redirect
  2. The use of an og:url open graph tag in the page
  3. The use of rel=canonical as described in RFC 6596. (Facebook’s crawler only supports content, not HTTP headers.)

If any of these methods result in an URL that’s different than the URL originally loaded, the specified URL will be considered the “canonical URL” for the original URL. If required, the crawler will also follow a chain of redirects to find the canonical URL.

All likes and shares will be attributed to the canonical URL instead of the loaded URL.

What did you need to do to make a proper migration without losing my share counters?

By controlling the canonical URL you can move content from one URL to another and retain like and share counts, as long as you allow Facebook to continue to resolve the new URL into the old one. This can be done with one of two methods:

Add an og:url tag to the new URL which points at the old URL (Preferred)
In your new URL, you should include a link to the old URL. For example, if your new URL was https://example.com/post-url, and the old URL was http://example.com/post-url, you should include this snippet in the https://example.com/post-url:

<meta property="og:url" content="http://example.com/post-url" />

Using this method tells the crawler that the canonical URL is at the old location, and it will use that to generate the number of likes and shares on the page. Any new likes and shares will continue to aggregate on the old URL as well.

Read more about the whole process and specific redirection settings you may need to apply inside Facebook Documentation

Sounds complicated if you are not a developer? Here is the secret that will make it simple

In Easy Social Share Buttons for WordPress, we simplified all that with just option switch inside social share optimization tags. All you need to do is visit Social Sharing -> Sharing Optimization and activate under Facebook Open Graph Settings the option that you wish to Use HTTP version of page in social tags

opengraph_httpfix

[button color=”primary” size=”large” type=”round” target=”_blank” link=”http://go.appscreo.com/essb”]Learn more for Easy Social Share Buttons[/button] [button color=”green” size=”large” type=”round” target=”_blank” link=”http://go.appscreo.com/essb-buy”]Get your copy for just $19[/button]

appscreo

Written by appscreo

AppsCreo is a team of web professionals who has delivered Envato market best selling social networking plugin of all time. Our mission is to create a perfect product that is easy to use, highly customizable and including innovative features you cannot find anywhere and has not seen before.

2 thoughts on “How to Recover Facebook Shares After Moving to HTTPS/SSL

    1. Hello,

      If you are using Easy Social Share Buttons for WordPress for Pinterest recovery of shares you need to use the build inside plugin share recovery function. Pinterest unlike Facebook is not able to move the history of migration in any form and all share counts are split on each URL. With share recovery you will generate a summary of both page versions.

      To get help with settings this inside Easy Social Share Buttons for WordPress please contact our support team at http://support.creoworx.com

      Best Regards,
      AppsCreo Team

Leave a Reply