Facebook Share Counter is import for every website. If you recently migrated to HTTPS of your website you may see that shares are not showing. In this article, you will find out the technical requirements recommended by Facebook.
But don’t worry. If you are not a coder that is not a problem. Easy Social Share Buttons for WordPress can recover your Facebook shares after migrating to HTTPS/SSL with just a few clicks – no coding knowledge is required. So if you are not a tech guy jump to the second part of the article directly.
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:
- A HTTP 301 or 302 Redirect
- The use of an og:url open graph tag in the page
- 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 according to Facebook?
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.
Sounds complicated if you are not a developer? Do not worry about that. Here is the secret that will make it simple just by switching to Easy Social Share Buttons for WordPress.
In Easy Social Share Buttons for WordPress, we simplified all that with just a few easy to use options from settings. Once you activate them all your past Facebook shares (or shares from other networks that support official counters) will be back again – NO CODING KNOWLEDGE IS REQUIRED!
All you need to do is navigate to the Share Counters Setup and choose that you wish to recover shares when migrating to https.
The share counter setup screen holds all options related work of share counters on your site. In the settings screen, you will be able to configure the share counter update period, avoid negative social display, additional counter update options, counter recovery, fake counters, etc. But all those options will work only when you configure a design that uses social share counters. If you do not plan to use the share counters on your site the options below are not for you.
The most common reason for the usage of share recovery is when you move from HTTP -> HTTPS protocol.
The share counter recovery options are located in the Share Counter Setup settings.
To enable the recovery scroll to Recover my Shares panel and press the Configure button.
On the new screen enable only the marked options like in the screenshot (others should stay to default state like in the picture).