Once upon a time my blog was new and nothing was happening on it even after setting it up. It kept sitting idle from August 2013 until March 2015 when I took command of it in my hands and started working on it.
Okay but I do want to inform you that it is the real story faced by me and it will be just that story I am about to share with no headings, sub-headings, bullet points, etc. Just the story with words.
<start of story>
By the time I resumed the activity on my blog, I started to get great comments from really awesome folks and for sometime I was hardly getting any random, irrelevant and spam comments. So I thought it is just it. I will NOT get any spam comment and I am not sure why I had that mindset built inside myself.
The time went by and I was into some months until early July with just handful amount of spam comments per week.
Then sometime struck back with much power. And it boggled my mind for few days. Everyday I logged-in into my dashboard, I kept noticing 50+ spam comments.
Wow…. 50+ comments, everyday.. without any breaks and intervals and strikes.
I thought like what to do now? How to actually deal with it?
I knew of a solution from long ago but had never implemented it at all because I never had a need to do so. Why?
Because I was not getting any spam comments until the tsunami of such comments struck the shores of my blog limits.
At first, I kind of believed that this solution won’t work. The spam comments were out of control that nobody in physical or virtual forms will ever control it.
But I went ahead with that solution. I did it all and registered and setup everything to make it in effect.
.. but I sighed after finishing the setup that if it will really work at all.. even the one percent.
So, I logged off to wrap up the day with a slight belief that it will work.
Next morning, I hopped on my inbox and noticed … zero spam comments..
It was a big “wow” in my heart!
To re-confirm if it was really the reality I logged-in into my blog dashboard and found… zero spam comments in spam queue in unapproved queue of comments.
Seriously the feel of it was as awesome as a kid sees his toy. 😀
So, what it really was that I setup?
What it really was that I knew it as a solution but was hesitant to implement it?
It was a WordPress plugin, a little but most-powerful spam killer plugin called “Akismet“.
This Akismet was my savior. And I salute to its creator and the team for making it available to the people and for keeping it free.
</end of story>
Thank you, Akismet!
Guys, do have it installed if you are going through getting loads of spam comments because if you don’t do it now, you will end up needing it sooner or later.
Now, Akismet is screening and detecting about 97% of spam comments itself and without me even getting noticed of it.
But one major drawback of Akismet is you have to still check the spam queue to un-spam some comments from real and genuine people as you know that blogging is the international thing and there are many countries and ISPs that are blacklisted in much of databases where Akismet finds the information about the commentators through their IP, name and email used. So, be careful about it if you do not or do not plan to check the spam queue. Do it because it needs a little effort to check out the comments from spam queue.
Thank you for reading the story, guys!
I will so tell you so that it does not mess up your analytical data as well. Or if it has, you block this little piece of mess.
Well as you know that unwanted and unethical traffic hitting our webpages are really bad. So bad in terms of recording analytical data where they may easily destroy bounce rates, audiences, acquisitions, and behaviors that are recorded by Google Analytical bots.
The one bad picture is how worst these referral traffics are when they hit your webpage, they mostly target your homepage and nothing else. After a few seconds they exit because they are programmed to stay active for awhile and with it they do not hit any other links/pages from your home page so the bounce rate per visit from such referral traffics are at 100%. Scary enough, right?[Tweet “It is easy to fight with web spam if you know what is spam and its source.”]
Okay, I won’t go long and long with this post but straight towards the point to actually how to block YourServerIsDown.com with one easy way through Google Analytics.
Let’s begin the process which is as easy as boiling the water:
Okay, I am not that tech-savvy and wanted to search for available methods to check to see how I can verify that filter.
Since YourServerIsDown.com is a spam website, hits error when accessing and that you cannot put your website URL anywhere on that website to click and check if it is really blocking the incoming traffic; I was out of options. Probably I couldn’t get the working methods to confirm YourServerIsDown.com is really blocked.
What I thought of an idea that how if I block a website where I can enter my blog URL to see upon clicking it from that website I block and if it really works to block the incoming traffic/hits.
The method is … just simple!
Go through the same process as above but use FaceBook.com OR Twitter.com to test the filter.
Because you can put your blog URL there and clicking the link there will record the information whether the filter is working or not.
Now to verify if it is really working can be seen through the following steps:
In short, no.
Let me go in details as to why not.
Whenever anyone would be coming from a website for example, YourServerIsDown.com, your website will still be accessible and won’t block the page at all for that person like showing some kind of error message but the website and its content. Just that going with Google Analytics to filter the incoming traffic/hits from that particular site (in our case “YourServerisDown.com”), the Google Analytics won’t record any information ever as long as filter is enabled. Thus, your web hosting bandwidth would be using up as well as the incoming traffic would be showing up through the stats of your cPanel (control panel).
In order to block such spam referrals entirely, there’s another method done through .htaccess file which I will cover in later days. But, I won’t recommend it going this way until large incoming traffic hitting your blog where your web hosting resources such as memory and bandwidth are being used up and hitting high volumes.
Please, share it with your friends, who knows if anyone is in need of such material and lands to it. 🙂