Sunday, 25 October 2015

Not seeing your virtual tour on FaceBook?

Well, this is a reasonable question. How do I get my virtual tour onto FaceBook?

The first thing to note is that FaceBook uses https by default. ‘https’ means it has secure browsing which helps to prevent hijacking of your pages by others. It has a higher level of encryption.
The impact is that if you want to reference other media (such as a virtual tour) then that needs to be on an https server too! Many people struggle with this. It means that if you try to embed a tour held on a non secure server it will never ever show up on FaceBook.
How do you know if you have a web site on an https server? Easy, look at your web address. If it says http (before the www) then it is not https! You can also check with your host.
Google Street View Trusted tours is https. So these can be displayed easily on FaceBook. We have many examples on our own customised FaceBook tab of 360 virtual tours (above) that we have completed, and many of our clients have included these tours on their FaceBook pages too. They wanted to integrate their tour with their social media. It makes perfect sense. It’s really great for retailers, galleries, restaurants, gyms…. and anyone wanting to make the most of their social media.
You don’t have to use your tour on FaceBook of course, instead you can embed it in your blog and in web sites whether using http or https.
As ever, it’s horses for courses. For instance, we also do customised tours (see next blog) which don’t go on FaceBook unless someone uses https for their web site.
If your expectation is that you want your tour to integrate with your social media then you need the higher level of security afforded by a Google Tour, (unless you have an https web site already). Don’t waste your money on anything less.
Depending on what is requested by a client, we can produce both sorts of tour, all at the same time, thus saving some time, and giving clients both options and freedom of choice.
Next a little more on those customised tours.

No comments:

Post a Comment