Skip to main content

Improvements To The Blogger Spam Classification And Review Processes

Too many Blogger blog owners ask what is allowed, when they publish a Blogger blog.

Asking what is allowed is a waste of time. We have explained, repeatedly, that whitelisting of blogs is not possible.

It would be better to ask what is required, when requesting advice or assistance, in Blogger Help Forum: Something Is Broken.

Since the purpose of publishing a Blogger blog is to have content for people to read, what is required is unique content, that is composed to satisfy the targeted reader population.

Blogger TOS forbids hosting of spam content.
Spam blogs cause various problems, beyond simply wasting a few seconds of your time when you happen to come across one. They can clog up search engines, making it difficult to find real content on the subjects that interest you. They may scrape content from other sites on the web, using other people's writing to make it look as though they have useful information of their own. And if an automated system is creating spam posts at an extremely high rate, it can impact the speed and quality of the service for other, legitimate users.

If your blog uses content that's shared with other blogs and websites, it will be classified - righteously or spuriously - as a spam blog. If the blog is reviewed, judged to be spuriously classified, and restored to your control - and if you continue publishing shared content - you will be seen, righteously or spuriously, as a repeat offender.

Long ago, spam classification was a fuzzy process. The fuzzy techniques used made both false negative classifications, and false negative classifications, unavoidable. Recent tunings to the spam classification process appear to make classification much more reliable.

Blogger will continue to provide a forum based classification appeal and review process. Since the initial classification processes now appear to be more reliable, we may see less spurious classifications, reported in the forums. This may offer us opportunity to provide more in depth analysis of blog content, during some review requests.

It's possible that in depth content analysis, conducted during the review request, may provide useful examples to other blog owners, what is allowed - and what techniques should be avoided. Maybe this will help some blog owners to avoid making the same mistakes - and reduce later spurious spam classifications, and avoid damage to reputation.

This may be a win - win - win (blog owners - forum helpers - Blogger Support) situation. The only losers will be the intentional spammers, who will become more obvious.

>> Top

Comments

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.

Free Domain Registration By "UNONIC" Is Fraudulent

Blogger blog owners, like everybody else, like to save money.

Some blog owners prefer to save money when registering a custom domain, for their blogs. We've seen several free domain registration services, providing what is claimed to be a two level Top Level Domain "co.xx" (where "xx" == various country codes).

The latest in this ongoing story appears to be "net.tf" - and 13 other "top level domains".There is also an additional free service offering third-level .tf domains, under the name United Names Organisation. They occupy 14 second-level domains, including .eu.tf, .us.tf, .net.tf, and .edu.tf. They are run by the same company as smartdots.com, and are given away as URL redirections.