Thu Jun 15, 2017 7:16 pm
SECOND TASK: PREP FOR FACEBOOK
The boss asked me to start a new thread for these tasks and tips posts, so this is it. To see the original announcement and the Google tips and tasks, see this post...
In that thread, Dan from [Domain Private] asked if switching to HTTPS will cause him to lose his Facebook and Pinterest likes and saves.
If you weren't using SBI!, the Facebook answer would be "YES, you would." (If you use SBI! for WP, you could have problems -- I haven't found any plugins that mention a fix for that issue with Facebook.)
What Is the Problem With Facebook
Good ol' Facebook. So big that it does what it wants. The other social media platforms recognize the switch from http to https. So a like on a page using http translates over to the same page on https. No loss of tweet numbers, pins, etc.
Facebook, however, does not recognize the switch. If you have 100 likes on your home page on http, after the switch you would have 0, none, nada, zip, zilch.
Not good, right?
Well, our developers have come up with an excellent solution to Facebook's intransigence. Whenever Facebook tries to access the https version of the page (that is, the new version), it will be redirected to the http version (the original version).
Only FB will do this. All the other platforms will see the https page, because they do things the way they should be.
Checking Social Media Tags and Codes
If you have Socialize It on your pages, or FB Like buttons or commenting that you added through Face It, there's nothing you need to do to prepare for HTTPS.
If you added +1 buttons, or Pinterest Follow/Twitter Follow buttons using the Social Block in BB2, you have nothing to do there either.
If you add the Save (Pin) code to your images using the Image Block in BB2, you have nothing to do.
All of the above will be taken care of by the dev team. And if you used code provided by SBI! for your uploaded pages (UYOH), there's nothing for you to do either.
If you've added anything else to your pages, then you'll want to check them and see if you need to update anything to HTTPS.
For example, the Facebook Page Plugin (it used to be the Facebook Like Box, for people to like your Facebook business page) may need updating. I just updated mine this morning to test that it works.
If you added the plugin to your site's Extra Column years ago, it's probably http. If so, you can simply add an s to http. However, I recommend that you log in to https://developers.facebook.com, click on My Apps, select what is probably called the Like Box app (if you named it that), and collect the code for it again.
Then return to BB2, edit a page, click on the Sitewide Dot that contains the FB code, and replace the code. Be sure to leave any div tags or other tags. You only want to replace the FB code.
Embedded Tweets, FB Posts, etc.
If you've embedded anything from Twitter or Facebook, check one or two. You probably don't have to do anything, since these are fairly new options for adding content to your site. But if you see http in any URL, you'll need to change it to https. Be sure to view the page after rebuilding it, to ensure that the embedded post or tweet is still displaying.
Do You Use WordPress?
As I mentioned above, I haven't seen any plugins that help with ensuring that Facebook and other social media don't drop all your social signals.
But, if you want to ensure that your site is always using HTTPS, there are some plugins to consider. Note, though, that we have not tested either of these. However, both have over 10,000 installs.
Easy HTTPS Redirection... https://wordpress.org/plugins/https-redirection/ -- this redirects all links to the HTTPS version
HTTP/HTTPS Remover... https://wordpress.org/plugins/http-https-remover/ -- this one removes http or https from the URL in each link, ensuring that your site will always appear secure.
That's it until next week!