Skip to main content

Spammers, And Content / Risk Management

Spammers protect their content against "unfair" deletion, and provide uninterrupted service to their "customers", by publishing multiple blogs, in spam blog farms.

Owners of better designed spam blog farms minimise the risk to their blogs, by separating the hacking / porn / spam content (Payload), from the immediately visible Blogger blogs (Collector). Spammers use a tiered structure of blogs, in their blog farms.
  • Collector blogs.
  • Distributor blogs.
  • Payload blogs.
Only the Payload blogs contain easily identified hacking / porn / spam material - and only the Collector blogs are immediately visible to the abuse detection processes.

A tiered blog structure makes a more easily managed spam blog farm.

Collector blogs (lots of these) link to the Distributor blogs (many of these), which link to the Payload blogs (a few of these). This is good risk management, by the spammers, because it separates the visible content from the identifiable content.

In some cases, the Payload "blogs" might be non Google websites. Content hosts which have no objection to hacking / porn / spam content can host the Payload, with no risk.

Risk levels differ, according to content in each blog.

  • Payloads (much risk, because of the detectable hacking / porn / spam content).
  • Collectors (some risk, because of the detectable ads - plus invisible, automated links, to the Distributors).
  • Distributors (little risk, only because of the invisible, automated links, to the Payloads).

As an example, one spam blog farm might be structured in geometrical progression.
Collectors (25) --> Distributors (5) --> Payload (1).
See the triangular structure, and the redundancy?

If automated links were permitted, only the Gateway blogs would be need to be advertised, to Blogger blog readers. If any of the Collector and / or Distributor blogs are detected and removed, the spammer can simply activate more blogs - and the Payload blogs can remain undisturbed.

If any Payload blogs are detected and removed, the spammer simply adds more Payload blogs - then updates the links in the Distributor blogs, with the URLs of the new Payloads. This is good project and risk management.

To interfere with this activity, Blogger prohibits automated linkage of blogs to other blogs and to non Google websites. This forces the spammers to provide visible links between the blogs and websites - and requires them to imaginatively publish both "legitimate" Collectors and Distributors with interesting and unique content and links.


Some of my readers are reporting hearing a short blast of music when they open my and other Blogger blogs in a variety of browsers, and I've experienced the same both on my own blog and elsewhere. I'm assuming this blast of song is coming from an invisible ad. Malware checks etc. reveal nothing, although using Google Chrome to inspect the page source I did see a iframe that I didn't recognise. Is it possible for spammers to embed invisible links in Blogger blogs somehow?
Chuck Croll said…
Hi Annie,

Thanks for the question, posted long ago.

A Blogger blog can contain an invisible link, as easily as a non Blogger website.

What you're describing though is probably blogs that (used to) use SiteMeter.

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: