Lost no. of shares on my blog posts on moving from http to https

It looks like the HTTP version of your posts doesn’t redirect to the HTTPS version yet. As a result, Facebook currently sees those URLs as 2 different entities, with 2 sets of sharing counts.
https://developers.facebook.com/tools/debug/og/object?q=https://dogwithblog.in/how-to-identify-and-treat-common-dog-allergies/

Could you try to set up a redirect from HTTP to HTTPS? Once you do so, Facebook should understand and should merging the counts from the 2 URLs.

I hope this helps.

Hello,

I have exactly same issue, but 301 redirect is set properly nevertheless fb likes are gone FB debug link. So it is not about redirecting traffic, I guess. Somehow those folks managed to count http and https likes and shares: warfare plugin.
Anyway, any hint is more then appreciated.

Thank you!
Anna

• This reply was modified 7 years, 10 months ago by oliwkama.
• This reply was modified 7 years, 10 months ago by oliwkama.

@oliwkama You don’t seem to be using Jetpack’s Sharing buttons on your site. Did you remove them? If so, could you add them back?

If you’d like to add the sharing counts to your existing sharing buttons, I would recommend getting in touch with your theme author if the buttons were added by the theme.

Hi,

I’m sorry, I am just playing with different settings and options. I have reverted back to Jetpack sharing buttons.

UPDATE: As a workaround I’ve changed canonical to point to http version of post. It brought back number of shares but is producing some warning on facebook side. I can’t figure out better solution for now.

Anna

• This reply was modified 7 years, 10 months ago by oliwkama.

@oliwkama Thanks!

Interestingly, Facebook’s API appears to return correct sharing counts right; whether I query the HTTPS or HTTP version of the post URL, I get the same amount of shares (115 right now):
https://graph.facebook.com/?id=https://sprawdzonakuchnia.pl/biszkopt-idealny/
https://graph.facebook.com/?id=https://sprawdzonakuchnia.pl/biszkopt-idealny/

If that changes when you change the Open Graph tags back to using HTTPS, you’ll need to open a bug here to let Facebook know, so they can fix it for you:
https://developers.facebook.com/bugs/

Let me know how it goes!

Well, it seems it is not a bug but it is designed to work that way. If you look at facebook recommendations here this is what I did; 301 redirect and canonical and og:url pointing to http version. I’m not sure if there are any side effects, other thing is changing manually canonical for hundreds of posts. I was pointing in my post above to other plugins that count separately http i https version of post and display summary. If you could implement it in Jetpack that would save me from changing hundreds of posts and probably would be future proof.

Anna

This is not an ideal solution, as the real canonical URL of your posts is the HTTPS version now; you would want search engines like Google to index the HTTPS version, not the old HTTP version.

I’m not sure that Facebook documentation page is still up to date; as we can see when querying the API directly (like Jetpack does in its sharing buttons), Facebook’s API is able to follow the redirect from HTTP to HTTPS and does return the same sharing count for both the HTTP and the HTTPS version.

Have you had the chance to open a bug report with Facebook directly? They should be able to give you a recommendation that will work with their system.

If you could implement it in Jetpack that would save me from changing hundreds of posts and probably would be future proof.

I’m not sure how you’re changing this within Yoast SEO Open Graph Meta tags, but I assume there has to be a way to update all URLs at once, via a filter. Filters like wpseo_canonical and wpseo_opengraph_url seem useful for example.

I would recommend that you ask the Yoast SEO team for help about this.

Found a fix here for both Facebook and G+:
https://cognitiveseo.com/blog/13431/recover-facebook-shares-https/