Skip to main content

Blog Owners, Marking Stats Log Entries As Referer Spam, Won't Accomplish Much

We see the occasional optimistic suggestion in Blogger Help Forum: Something Is Broken, from blog owners tired of the referer spam, in their Stats logs.
Why can't we just tell them which Stats entries are spam?
This is, admittedly, such a simple suggestion - it surely must present part of the final solution.

If one considers the purposes behind referer spam, one can see a problem with having individual blog owners designate specific pageview entries, in their Stats logs, as referer spam.

There are actually multiple purposes for referer spam.

Look carefully at the entries, in your Stats logs. Are all of the websites, which are being advertised by non existent links to your blog, actually spammy? Chances are, if you look closely enough, you'll find one or two which just don't seem to fit the pattern.
  • The volume of hits makes the pageview counts look suspicious.
  • There's no link to your blog, from the websites.
  • Looking closely at the content of the blog or website, it just does not look like the typical referer spam target.

This blog was honoured, as a false target, in October 2011. I have no doubt that other blogs and websites are also the targets of similar, deliberate attacks.

With referer spam used strategically, the spammers could simply adjust the volume of their attacks, to make innocent victims more visible, and more vulnerable to false accusation by the less observant blog owners, who simply want all referer spam stopped.

To guard against referer spam being used strategically, to attack innocent blogs and websites, any designations "This is referer spam!" would have to be complemented by "This is not referer spam!". Ultimately, all Stats pageview entries would have to be verified as "Spam!" or "Not spam!", to prevent referer spam from being successfully used as an attack technique. How many blog owners would want to scan their entire Stats log, daily, and mark all pageview entries as "Spam!" or "Not Spam!"?

Understanding the nature of referer spam, one sees that the only way to effectively combat it is to have Google globally examine all pageview activity for all blogs, over long periods of time, to identify actual referer spam - and to avoid falsely designating innocent third party blogs and websites as being intentional referer spam customers.

>> Top


Susan said…
I am having this problem on my blog ( The traffic entries on my stats page are from websites that do not link to my blog and have nothing to do with my content. For example, this is one such trafic entry link

It seems that all of my post stats are incorrect as they have been redirected through filmhill. Can you please help me solve this problem and stop this from happening.

Any help you can provide would be much appreciated.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: