Experts from TechWyse and around the world offer how-to's, strategy advice, interviews, infographics and insights to help your SEO and internet marketing campaigns Rise To The Top!
Social Media Marketing September 30th, 2011
Content extracted form a third-party website which is not SSL Certified will not be visible from October on, these changes are being implemented in order to enhance the internet security of Facebook users. To get Facebook secure has been one of the main topics raised over the past couple of months and the extra layer of security is being added after multiple hack and infection attempts.
If your custom fanpage is not hosted on an SSL (Secure Sockets Layer) certified location it will be disabled this coming October (2011). For a social media marketer or developer it is must to purchase a dedicated IP and SSL Certification in order to get the page secured and to let the content be visible to the public. If you don’t want to lose out on your potential customers then it’s a must to use an SSL protocol.
Imagine if your visitors get a “Switch to regular connection (http)” popup every time they view your fanpage, if it were me, I would cancel the request and move to another fanpage.
Another factor to consider is when using an Image or video from a third party source, e.g YouTube. YouTube now gives you an option to embed Https code so make sure to use that for hosting the videos via YouTube. Also there are wide spread reports that WordPress is not faring very well with SSL, but a few plugins for WordPress might help to cope with the shared SSL.
To secure your applications and URL you will need to make changes to your Facebook developers application settings. After securing your hosting go to your developer’s application page and edit the application by adding a link to the secured URL in the Secure Canvas URL and Secure Page Tab URL. Also note that both the tabs need to be updated with the https extension. See the example below:
According to Facebook now all the JS, CSS and images should be referred with https , for example <img src=”https://www.example.com/images/yourphoto.gif” />
Also the secure_callback_url and secure_page_tab_url must be a completely qualified URL starting with https:// and must point to a directory (i.e., end with a ‘/’) or a dynamic page (i.e., have a ‘?’ somewhere).
The FBML application should also include an SSL protocol in order to serve the users who are browsing over a secure connection. Since the FBML developers need to understand if the users are browsing using a secure connection, it’s a must to obtain an SSL certification in order to receive traffic from these users. Read more about it from the Facebook Developers themselves. There are also few third part tools ( sslabs) to help you analyse your SSL certification and to fix errors and warnings.
If you are hosting all the applications using your server then immediately check if the server is already set up with https, if not get it done as soon as possible. If you are getting the message “Sorry! We can’t display this content while you’re viewing Facebook over a secure connection” then test your fanpage and all the third party applications associated with it right now and be ready for the new changes!