Menu

Thursday, June 19, 2014

Facebook block: Spammy or Unsafe (3)


As you all know, I have been battling against the giants of the internet for more than 3 years now, and I believe I finally got them by the Gotcha…


In my previous post I explained how I came to find out what the reason was that is causing Facebook to block domains for being “Spammy or Unsafe”. The thing is, it’s not really Facebook. They are just following someone else’s advice, who is trying to sell security software. If you want to know who...Check out the previous post here…


Even though there is absolutely no reason to block any of my domains, whom ever is blocking them, still does. So, why am I so happy? Well that is simply because, the domains are no longer as important as they were before. As a matter of fact, I probably will be using the domains, just to redirect to the new one:







As we started to organize our Facebook campaign for our new Techno Dance Event: Synergy...I came to realize that having blocked domains are going to make our campaign way to complicated to be successful. So I invested a few weeks to make sure this will never be the case again.


This is how I created a solution that is working even better then when I was using the domains.


A blocked domain is always HTTP. That means the information that travels thru the domain on your website is not encrypted. To solve this you will need an SSL certificate so all the information on your website runs thru an HTTPS connection. While on Facebook, look at your URL and you can see the green https://.


An SSL certificate however is needed when a website is storing personal information which should be protected. Our websites never did. The static websites that used the blocked domains, where only text, code and images. This meant I had to buy an SSL certificate, just to connect with Facebook. At first I believed it was quite expensive to get an SSL certificate, and did find Facebook to be so important. The Synergy Event promotions changed my mind.


So to cut a long story short, this is what went down:


1 - First you need a domain you can use as the secure entree to your websites. lets call it: yourdomain.com


2 - Get a SSL Certificate at RappidSSL for www.yourdomain.com. Don’t let the prices scare you, they are much cheaper than that. I paid $7,00 for one Domain for a whole year.


3 - Order the certificate and install it on your server. You can follow the instructions on the website, or check with cPannel.


4 - If you did everything right, your new URL should look like this: https://yourdomain.com.


5 - Now create subfolders inside your HTTPS domain for each website on your server. Hope you don’t have many links to change, cause that can be a B….tch.


So if you had a website called: site1, with the domain www.site1.com, Your URL would have been:
http://www.site1.com/index.html.
This is what Facebook is blocking.


Your new URL will look like this:
https://yourdomain/site1/index.html
Now you can link your website with Facebook again.


6 - Go to your cPannel, domains redirect, and redirect the domain:
www.site1.com >>> to >>> https://yourdomain/site1/index.html


Voila...No more “Spammy or Unsafe” B.S.


In my case I took it a step further, and am now using the SSL domain for all the websites. Even though the original URL’s are redirected.


So if any one was asking himself where I was and what I was doing? I was at DEFCON 1 with the two Internet giants for the last 3 weeks, and finally got a chance to stick it to them, at least a little bit.


In order to celebrate this monumental victory, I would like to invite everyone to visit the new website and join. Got some really cool tutorials, free music, Event guest list and other goodies you might like a lot.


Welcome to:

logo.png