Social Icons

Pages

Showing posts with label Spam. Show all posts
Showing posts with label Spam. Show all posts

Saturday, 14 December 2013

Blogger Blog Content Needs To Be Unique, And Properly Targeted

I've been studying spam, in Blogger blogs, for over 5 years.

This year, we've seen improvement in the automated spam classification process, implied by a noticeable reduction in spam review requests overall - and in a considerable reduction in the proportions of false positive classifications. During the past few months, blogs requested for review are 2 or 3 times more likely to be confirmed as legitimate spam blogs (true positives), compared to this time last year.

Of the blogs confirmed to be spam hosts, when I am able to examine cached copies of the content, 3 out of 4 of those appear to contain material scraped or syndicated from other blogs or websites.
  • Content scraped (stolen), or syndicated (copied, with permission), from other blogs / websites. Content scraped or syndicated to other blogs / websites.

Google describes the problem, in Blogger Help: Spam, phishing, or malware on Blogger, quite simply.
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.

Long ago, spam blogs were first encountered as startup components in large spam blog farms.

Later, we explored the involvement of various "get rich quick" schemes, and of affiliate marketing.
  • Content or links which reference referral-based activities such as GPT ("Get Paid To"), MLM ("Multi-Level Marketing"), MMF ("Make Money Fast"), MMH ("Make Money from Home"), PTC ("Pay To Click"), or PTS ("Pay To Surf").
  • Affiliate marketing (Please, don't confuse this with "affiliate networking"!).

Of these three broad descriptions of confirmed spam blog content - spam blog startups, get rich quick schemes, and affiliate marketing - the one common feature in most of the blogs, confirmed as spam hosts, seems to be the lack of unique content. One of the features of the Panda update to Google Search was described as "content quality" in search results.

The past year tuning to Blogger spam classification appears to be in keeping with Panda, in that it is targeting blogs which rely upon content intentionally replicated from blog to blog - whether "scraped" (stolen, without permission), or "syndicated" (copied, with permission).

The end result here is that Blogger blogs, to avoid spurious spam classification, need to contain as much unique material as possible. While some amounts of quotation of other blogs and websites is beneficial, the majority of blog content needs to be written by the blog owners and contributors, and properly targeted to the reader population.

>> Top

Tuesday, 19 November 2013

Market Your Blog, To Those Who Are Interested

We see many questions in Blogger Help Forum: Something Is Broken, about blog content, and (lack of) appreciation by the readers.

Occasionally, people become concerned about activity of the people reading their blogs - why they get so many new visitors (but nobody returns later, to read more), or why the main page is so well read (but nobody reads the archived posts).

In other cases, they wonder why the blog was deleted - even though it had the required warning protecting it. And sometimes, they may wonder why so many people read the blog, but nobody comments on the posts.

If your blog just uses Stats, to provide you reader activity statistics, you'll probably be only concerned with visitor activity, and pageview count.

If you use an actual visitor activity log, like SiteMeter or StatCounter, you may also look at new / return visitor ratio, or pages read / visitor count. In both cases, you're examining visitor interest.

Visitor interest starts with how you advertise the blog. You get good visitor interest when you advertise the blog where it will be welcomed, and in a style where your advertisements will be welcomed.

People who don't like your blog may read the first page, then go elsewhere. If they read more than the first page, they will probably be doing that so they can report the blog, for TOS Violation or similar. This is why some blogs are unrighteously clasified as abusive.

No matter how objectively you may write a blog discussing alternative lifestyles, if you advertise your blog where Bible Belt USA Conservatives may gather, the best result that you may see is "single pageview" visitors.

Occasionally, we'll see a problem report that starts out with a common complaint.
Why was my blog deleted? I don't spam.
When we're able to retrieve a cached copy of the blog, we'll agree with the owner.

Some blogs, deleted as abusive, will have a little known problem.
Commercially funded adult content.
Other times, the problem will be more subtle.
I set the "Adult Content?" flag to "Yes"! Why am I getting complaints? (Why was the blog deleted?).
The problem here starts with the nature of the "Adult Content" warning.

Not every blog owner realises that the warning is only advisory. Anybody, no matter their age or religious preference, may (by accident, or intentionally) click on "Agree". Having clicked, they may be subject to a faceful of content which is not in their best interest, or which they do not appreciate.

If a link to your blog appears in the wrong forum discussion, or on the wrong website - either a Bible Belt forum or School Children's website - don't be surprised if your blog continues to get content complaints. And in some cases, we'll see you in the forums.
Why was my blog deleted? I don't spam.

Be sensitive to both the stated, and unstated, policies where you post. If your blog contains controversial material, be very conservative about how and where you advertise. Publish properly targeted posts, with unique content, for the best future of your blog.

>> Top

Wednesday, 6 November 2013

Comment Notification Email, And Spam Classification

Comment moderation, and comment notification, have long been optional features of Blogger Commenting.

The sequence of comment moderation email, and comment notification email, was simple.
  • If comment moderation was selected, moderation email was sent to all blog administrators. Any one administrator could then select to Publish, or to Reject, a given comment.
  • If comment moderation was not selected, each comment was simply Published, immediately.
  • If comment notification was selected, notification email was sent to all recipient email addresses, when any comment was published.
  • All blog administrators could Delete any comment, after it was published, at their discretion.

When the new comment moderation system was provided, in 2010, comment moderation changed. As the comment filters became trained, some comments were automatically rejected - and sent to the Spam queue - and that is where the current problem starts.

With the new comment moderation system, spuriously filtered comments never generated notification email - and this was a problem.

Comments sent directly to the Spam queue could be moderated, and Published, at the discretion of the blog administrators. Comments which were not Published remained in the Spam queue - and never generated notification email.

As the filters in the new comment moderation system became trained, false positives became a problem. Comments, spuriously filtered as Spam, generated no notification email.

Blog owners, accustomed to moderating comments after they were published, and receiving no notification email from comments which went straight to the Spam queue, complained of lost comments.

Listening to complaints from the blog owners, Blogger Engineering changed the sequence of the comment moderation and notification emails.
  • If comment notification is selected, email is sent to all recipient email addresses, as soon as a comment is submitted for publication.
  • If comment moderation is selected, moderation email is sent to all blog administrators.
  • All blog administrators can Delete, or mark as Spam, any comment, before or after Published, at their discretion.

With comment notification email being sent immediately, this leaves recipients of the email occasionally confused. Comments immediately judged as Spam by the filters, or later by a blog administrator, will still generate email.

Recipients of comment notification email, not seeing a given comment published, who are blog administrators, can check the Spam queue - and in some cases, choose to Publish a comment which is spuriously filtered as Spam. This helps to train the filters - and later, see less spuriously filtered comments.

Recipients of comment notification email, not seeing a given comment published, and who are not blog administrators, will have to notify a blog administrator, who can check the Spam queue. In some cases, again, the administrator can choose to Publish a comment that is spuriously filtered as Spam.

As a blog owner, you need to properly select the moderation and notification options, to satisfy your personal needs. And, help to train the filters.

>> Top

Sunday, 6 October 2013

Team Blog Ownership, And Abuse Classification

We see some people, posting in Blogger Help Forum: Something Is Broken, who have problems with blogs under team ownership, and abuse classification.
My blog was deleted as spam but I don't spam! BTW, one of the other administrators of my blog recently had his Google account blocked.
We've observed, a few times, that team blog relationships create interesting complications, with various Blogger issues - and this appears to represent yet one more complication.

In most cases, when a Blogger account or blog is deleted or locked, the owner of the account or blogs affected should see an online notification, and / or receive email informing of the action taken.

There are several reasons why notification - email or online - may not always be provided.
  • Blogger accounts, based on bogus or inactive email addresses, will not provide email notification.
  • A person who uses multiple Blogger accounts, accidentally or intentionally, will only see the dashboard for the account currently logged in.
  • An owner of a Blogger account, recently unlocked after detected suspicious / unusual activity, will see only an empty dashboard, when logging in.

The team blog ownership relationship appears to provide one more reason for lack of notification.
  • Administrators of blogs under team ownership may not see notification, when one of the team members has a Blogger account deleted or locked.

Both Blogger accounts deleted for non repentant abusive activity, and Blogger accounts locked when suspicious / unusual activity is detected, appear to present this complication, with blogs under team ownership.

When a Blogger account is deleted after the owner repeatedly produces TOS violations, all blogs owned by the account are apparently deleted. It's possible that, when a blog is deleted, team ownership issues are overlooked in the blog deletion process - and the blog simply disappears from the dashboards of the other team members. It's also possible that this is a predictable group action - comparable to affiliate network detection.

When a Blogger account is locked after suspicious / unusual activity is detected, all owned blogs simply disappear from the dashboard of the owner. Blogs owned by a locked account are under automatic security review, with no appeal by the owner being possible. Team administrators are unlikely to have any alternative appeal opportunity, for a blog under review when an owning account is locked.

The latter two scenarios represent two reasons why, if we see the complaint in Blogger Help Forum: Something Is Broken
My blog has disappeared from my dashboard, and is not online!
One initial question should be
Was the blog under team ownership?

>> Top

Monday, 26 August 2013

Repeated TOS Violations Are Punished Gradually

Some blog owners don't understand the serious nature of repeated violation of TOS Policy, in Blogger blogs - and how offenses are handled, by Google.

We've seen several reports, in Blogger Help Forum: Something Is Broken, from blog owners who appear to be unclear about the consequences of repeated TOS Violations.
I got email from Blogger, about my Blogger account.
We'd like to inform you that we've received another complaint regarding a blog that you administer. Upon review of your account, we've noted that you've repeatedly violated the Terms of Service: http://www.blogger.com/go/terms. Given that we've provided you with several warnings of these violations and advised you of our policy towards repeat infringers, we've been forced to disable your Blogger service.
How do I get my blog restored?

This example appears to represent the final step, in a multi step policy.

It appears that Google takes a multi step approach, towards repeated TOS violations - such as hosting of malware, porn, and / or spam - in Blogger blogs. This is similar to the DMCA Violations punishment process.
  1. Unlike DMCA violations, individual posts are not deleted.
  2. Deletion of offending blogs.
  3. Deletion of offending Blogger account(s) (and blogs).

With a TOS initiated blog deletion, the blog owner is expected to have the blog reviewed. If the review determines the blog to be unrighteously deleted, the blog is restored - though there may be side effects.

If the blog owner does not wish to have the blog reviewed, he / she is allowed to start over, with a new blog - but will have to publish to a new URL. Content lost must be recovered by the owner - and the owner should be more careful with future blogs.

If the blog owner continue to publish blogs which violate TOS, any Blogger accounts involved, along with any other blogs owned by the deleted accounts, will be deleted.

We see that an appeal is possible.
Next steps for suspended accounts: If you believe your access to this product was suspended in error, contact us.

With any blogs published to a non BlogSpot domain, the domain URL(s) will remain in use, in the Google database - though the domain owner is free to use the domain outside Google address space. If the offender wishes to start over, both new BlogSpot and non BlogSpot URLs will be required.

As with other issues with email delivered warnings, there will be cases when the owner may not receive warnings in a timely fashion. Even so, the owner is responsible, when he / she offends, repeatedly.

Blogs under team ownership are apparently vulnerable to action taken against any team member. In some cases, blogs will simply disappear from the dashboards of the other team members, with no appeal or review request being possible.

It's possible that legal notice, provided by Google through email, will supercede ongoing forum advice - even if email sent is not received by the owner.

>> Top

Sunday, 18 August 2013

CAPTCHA Verification Is Broken, For Some Blogs, In Various Applications

We're seeing a number of problem reports, in Blogger Help Forum: Something Is Broken, about various problems which involve CAPTCHA verification processes.

The symptoms are fairly diverse.
  • Some blog owners report problems with commenting, on their blogs.
  • Some report problems with high posting volumes.
  • Some report problems getting abuse review requested, for their blogs falsely accused of hosting abusive content.
The reporting volumes, and perceived urgency, for each case, will vary.

The known problems involve various bX codes, issued in place of the CAPTCHA form.
  • An unverified code is being seen, by people trying to post comments, on blogs using CAPTCHA screening.
  • Blog owners are reporting various bX codes, when trying to post high volume blogs.
  • Other blog owners are reporting "bX-niui1k", when trying to request spam review, from the dashboard "Deleted blogs" list.
  • It's possible that there are other CAPTCHA applications, also seeing bX codes.
The audience observing the bX codes will differ - because the relationship of the people needing to use the CAPTCHA, and the volume of CAPTCHA use by the affected people, will differ.

People observing a bX code, when trying to post a comment, will be guests on blogs which use CAPTCHA screening - since blog members and owners are not subject to comment screening. CAPTCHA screening is optional for comment moderation, in general - and it's possible that many blog owners are not using CAPTCHA screening on their blogs.

It's also possible that only blogs which use the full page and popup comment forms are vulnerable, to this problem. The report volumes involving bX codes involved with comment moderation are low - and this will make affinity analysis difficult.

People observing a bX code, when trying to post at high volume, will be blog owners who post frequently. The reports of this problem are low to medium volume - possibly because many blog owners avoid posting excessively. This may be because we have observed that repeatedly solving a CAPTCHA will be inconvenient.

The people who report this problem are fairly insistent that this problem needs to be solved. Since the bX code is observed repeatedly (once for each high volume post attempted), by the blog owners affected, this case will involve the most controversy. Several blog owners have reported seeing differing bX codes.

People observing a bX code, when trying to submit an abusive blog review request from the "Deleted blogs" dashboard list, will be blog owners whose blogs were deleted or locked, spuriously, for abusive content (aka "spam hosting"). These people will post in the forums, and can be helped fairly easily, by our promptly offering a manual review, submitted to Blogger Support.

This case represents the most frequently reported symptom - but since the people affected can be helped with minimum fuss - and since this case is only observed once for each blog involved, this case will involve less controversy. This case has been reported, as noted, consistently producing the "bX-niui1k" code.

It's possible that CAPTCHAs are used in other unidentified applications - and we may yet have other cases to discuss, if the base problem is not resolved fairly promptly. Blogger Support is currently aware that there is a problem - and hopefully, where the problem lies.

>> Top

Monday, 12 August 2013

Getting Traffic To Your Blog - How Not To Do It 2

Here's a great investment idea.

Everybody who needs money (which is most likely, everybody reading here) can invest $10 each. Everybody, reading this, can send me $10. Surely, each of you have a spare $10, to invest.

What will I do with the funds received?
  1. I will, immediately, take 10% off the top. That's for my retirement account.
  2. I will let my friends (don't you wish that you were my friend?) take 5%, each, off the top.
  3. As I get investments from more blog owners, I'll send you - and the other initial investors - a token payment.
  4. At the end of a week, you, and the other investors, get to divide up the remainder.

Isn't that a great investment idea?

That is a great investment idea - for me, and for my friends. For you, not so great.

That is a simplified description of a Ponzi scheme.

Ponzi schemes exist on the Internet, also. From time to time, we have seen them reported in Blogger Help Forum: Something Is Broken, by people complaining of unknown websites, in their Reading Lists.

Similar to the blog feed redirection scam scheme technique, we have what's called a "traffic exchange". Want more traffic to your blog? Just add a link to the exchange, on your blog. Your blog gets traffic from all of the other blogs and websites, similarly providing links to the exchange.

A traffic exchange pays off, in real time. Your blog contributes traffic to other blogs and websites - and they contribute traffic, to your blog. But who will be contributing traffic, to your blog?
  1. Other blog owners - who, like you, have no source of real traffic.
  2. Various scammers and spammers.
Who will not be contributing traffic to your blog?
  1. Other blog and website owners, who know how to effectively get traffic to their blogs and websites.

People who know how to effectively get traffic to their blogs know to use search engines, for targeted traffic - and to use interesting, unique, and useful blog content, to get indexed by the search engines. Those people know that neither they, nor their readers, will benefit from traffic exchanges, and similar random traffic programmes.

Experienced blog owners know that they won't benefit from linking to blogs with no source of real traffic - either directly (using bloglists or linklists) - or indirectly (using link farms or traffic exchanges).

Only blogs with no source of real traffic benefit from link farms or traffic exchanges. Experienced blog owners know to spend their time publishing interesting, unique, and useful blog content.

Who really benefits from traffic exchanges?
  1. The exchange operators (who "take 10% off the top").
  2. The various scammers and spammers (who each "take 5% off the top").
Who contributes the traffic?
  1. You.
  2. Other blog owners, like you, who have no source of real traffic.

If you want relevant and useful traffic to your blog, publish interesting, unique, and useful blog content. Don't waste your readers time, with mazes of random blogs and websites.

>> Top

Wednesday, 3 July 2013

Hacking Detection Is (Generally) Not The Fault Of The Blogger Account Owner

We've been helping Blogger blog owners deal with spurious fuzzy content classification, for many years.

We started out, long ago, with blogs deleted because of spam classification. Later, Blogger added malware classification - and most recently, porn classification ("adult content", with objectionable advertisements). These three classification categories involve fuzzy blog content analysis.

A fourth category, which similarly results in blog(s) being deleted, I describe as "hacking detection". This category complements the other three, because the primary symptom of all four are remarkably similar.
Help me! Blogger has deleted my blog!!
This is a frequent complaint, seen in Blogger Help Forum: Something Is Broken.

One problem with using the term "hacking" is that some account owners take this diagnosis personally.
Why do you mention hacking? I am not a hacker!
And in almost all cases, the owners are correct.

Blogs are deleted by Blogger, currently, because of several different reasons.
  1. DMCA Violation.
  2. Hacking detection.
  3. Malware detection.
  4. Porn detection.
  5. Spam detection.
I list the different categories, collectively, because they are frequently reported, using the common symptom.
My blog was deleted, and I did not do it!

DMCA, malware, porn, and spam are generally based on what the blog owner did (though in many cases, what the owner "did" was simply to publish a blog). Hacking, on the other hand, is generally based on action by someone other than the blog owner.

DMCA, malware, porn, and spam classifications are based on content analysis (automated), or complaint (manual) - and these classifications can be somewhat avoided by the blog owner. Don't steal content or publish a blog containing malware, porn, or spam, to reduce your chance of having the blog classified.

Hacking detection, on the other hand, is based on analysis of Blogger account traffic - and this classification can not be avoided, as easily, by the blog owner. Hacking generally involves use of a cloud of computers, to systematically break into a Blogger account owned by the victim.

Though frequently, a hacking attack starts with unintentional disclosure of personal information by the victim, actual hacking activity is typically not initiated by the victim.

Detection of hacking attacks is best conducted by Google, because they can look for repetitive activity against multiple Blogger / Google accounts, from multiple computers located worldwide.
  • Most account owners can login to their accounts in one or two tries.
  • Very few account owners will, intentionally, attempt to login to their accounts, concurrently, from computers in Argentina, USA, and Zaire.
  • Very few computers will be used to access Blogger accounts owned by people in Brazil today, in China tomorrow, and in Denmark next week.

Recovery from hacking detection requires willful action by the victim - though Blogger makes the required action so simple, its purpose becomes transparent. The victim, or account owner, is simply required to change the account password, solve a CAPTCHA, and / or verify account ownership by providing various personal details.

Having initiated hacking recovery, the account owner is able to login to Blogger - but is greeted by an empty dashboard.
You are not yet the owner of any blogs. Create a blog, and get started!
This is where the confusion starts.

Not all Blogger account owners personally publish a blog. Some people setup Blogger accounts simply to comment on, and / or Follow blogs published by other people - and won't, necessarily, publish a blog using the account in question.

Blogger accounts with no owned blogs may still be under attack by hackers - and are subject to hacking detection. This makes the primary symptom so confusing.
You are not yet the owner of any blogs. Create a blog, and get started!
People who don't own any blogs (under this Blogger account) may, or may not, see this as a problem.

In cases where the initial symptom is a deleted blog, the blog owner must recover the hacked (locked) account, before the blog can be recovered. This is one more scenario where unplanned, anonymous blog ownership, just causes more confusion.

Having initiated hacking recovery, a blog owner is simply expected to wait patiently, until the blogs owned by the account are verified as free of content added by the hacker. Unfortunately, we sometimes see the blog owner, impatiently reporting in Blogger Help Forum: Something Is Broken.
I had to change my password, and having done that, Blogger deleted my blog!

Sometimes, hacking detection starts with the Blogger account owner, repetitively trying to recover access to the account, by sequentially trying every possible password (sometimes trying the same password, repeatedly).
I know it's one of these! But which one? Did I maybe type the one, incorrectly??
This repetitive action looks the same as any malicious hacking attack - and that is why hacking detection is so hard to canonically diagnose.

Please, consider these details, the next time you post your problem report.
Help me! Blogger has deleted my blog!!
In some cases, I may respond with a mention of hacking detection. If I do that, please don't take my response as a personal attack upon you.
Why do you mention hacking? I am not a hacker!

Even though being the victim of a hacking attack is not the fault of the account / blog owner, that person may still have to bear some of the responsibility. In general, blog owners have to support themselves - learn how to protect themselves, and use 2-step verification.

>> Top

Thursday, 27 June 2013

"Adult Content" Blogs, And New Blogger Monetisation Restrictions

This week, we're seeing some reports from a few blog owners who recently received a disturbing email message, mentioning their blogs and adult advertisements.
I received an email stating I have adult content on my blog, and that a new policy will cause certain blogs to be deleted. Is my blog vulnerable to deletion, under this new policy?

Like many spammers, these blog owners may be asking for a whitelisting of their blog - which is something that Blogger just won't provide.

The legendary email, recently received, is somewhat ambiguous in wording.
You are receiving this message because you are the admin of a blog hosted on Blogger which is identified to have Adult content.

Please be advised that on June 30th 2013, we will be updating our Content Policy to strictly prohibit the monetization of Adult content on Blogger. After June 30th 2013, we will be enforcing this policy and will remove blogs which are adult in nature and are displaying advertisements to adult websites.

If your adult blog currently has advertisements which are adult in nature, you should remove them as soon as possible as to avoid any potential Terms of Service violation and/or content removals.

The policy discouraging monetised "adult content" blogs is not new - we have actually been warning people about this for years, in the Malware / Spam Appeal Guidelines. We cite the Guidelines a dozen or so times daily, in various malware and spam review discussions in Blogger Help Forum: Something Is Broken.
Blogger / Google has repeatedly stated that some blog content is not acceptable, because it constitutes or encourages abusive activity, such as hacking, porn, and spam, in the Blogger Internet space.

Here is the current list of examples, developed by Blogger / Google, and the Top Contributors of Blogger Help Forum.
  • Affiliate marketing (Please, don't confuse this with "affiliate networking"!).
  • Automated traffic redirection, to another Blogger blog, or to non Google hosted content.
  • Commercially funded adult content.
  • Content created with scripts and programs, rather than by hand.
  • Content or links which reference account hacking / password distribution / password sharing.
  • Content or links which reference code deconstruction / reverse engineering, to bypass normal use of proprietary
  • software.
  • Content or links which reference referral-based activities such as GPT ("Get Paid To"), MLM ("Multi-Level Marketing"), MMF ("Make Money Fast"), MMH ("Make Money from Home"), PTC ("Pay To Click"), or PTS ("Pay To Surf").
  • Content scraped from other blogs / websites.
  • Copyright Infringement.
  • Large blogs with multiple, unfocused / unrelated subjects.
  • Links to Illegal Downloads / Streaming / Torrents.
  • Monetizing of adult content, aka porn spam.

The specific blogs, targeted by the email, are not difficult to identify. "Adult Content" blogs will generally bear an interstitial "Content Warning", awarded either voluntarily or involuntarily.

In odd cases, people may receive the email, but may not have any blogs affected by the policy - and in this case, they will simply have to ignore the email. Blogger Support can only review blogs, when they are actually deleted or locked.

In other cases, people may not receive the email. Just as with malware and spam classifications, all blog owners won't be contactable by email.

If the adult content classifier is designed similar to the malware and spam classifiers, it will use a fuzzy detection process to identify the undesirable "adult content" advertisements.

Since fuzzy malware / spam classification does not support whitelisting, porn classification won't either. Blog owners asking "Is my blog safe?" are unlikely to get any useful answers.

My suspicion is that owners of the most popular and productive "adult content" blogs will move to alternate hosting. Some of them may relocate to WordPress - until WordPress, similarly, rejects them.

Some owners, choosing to remain in Blogger, will take the warning seriously, and remove any ads.
If your adult blog currently has advertisements which are adult in nature, you should remove them as soon as possible as to avoid any potential Terms of Service violation and/or content removals.
Various possible "adult content" blogs, with and without "adult advertisements", remaining in Blogger hosting, will be classified and deleted, and will result in more reports in Blogger Help Forum: Something Is Broken.
Why was my blog deleted?

We'll simply end up with more discussions with requests for review and reinstatement - and more uncertainty. Some blogs will be restored promptly, with others requiring careful deliberation. And some blog owners will simply be told
Sorry, your blog cannot be restored. It was recently confirmed as a adult content host, with unacceptable advertisements.


>> Top

Monday, 24 June 2013

Hacking / Malware / Porn / Spam Classification, And Effects Upon Search Engine Reputation

Occasionally, we see concern in Blogger Help Forum: Something Is Broken, about the long term effects of Blogger hacking / malware / porn / spam classification or detection.
My blog was deleted, because of spurious spam classification - and later restored to service. Did my blog lose search engine reputation, in Google?

Any time a blog goes offline, its reputation is affected, to some extent. How much effect a hacking / malware / porn / spam classification or detection has, on any given blog, will vary widely.

Every blog or website has different factors, which affect its reputation.
  • Readers, and links in their blogs and websites.
  • Readers, and inherent reputation.
  • Search engines, and inherent reputation.
These factors will differ, from blog to blog, in almost infinite variety.

If your blog has readers who maintain their own blogs and websites, some will see you as a useful source of information, and will link from their blog / website, to your blog. As a readers blog / website is indexed by a search engine bot, and a link to your blog is encountered, your blog is indexed. This causes indirect search engine reputation.

Any time your blog is offline, even briefly, it loses reputation. If you use Google Webmaster Tools, look at the indexing logs. One event which you will see, from time to time, mentions "404 Not Found". Any time a search engine bot is indexing your blog, and it encounters a "404 Not Found", your blog loses reputation.

Loss of search reputation is similar to a person dying from blood loss. How fast the blood loss, and how long the loss continues, will affect how likely death will occur.

The longer your blog is offline, the more "404 Not Found" events will be logged, as the search engine bots attempt to index the various pages in the blog. Each succeeding "404 Not Found" represents your blogs reputation, leaking away, drop by drop. The longer your blog is offline, the more reputation loss it suffers, from indirect and direct indexing.

Until reputation is regained, your blog appears lower in search results, because of lower page rank. You suffer from less search engine generated traffic, and less new readers. This is a circular effect - less search engine reputation leads to less new reader traffic, which leads to less search engine reputation.

When your blog is reviewed and restored to online status, indexing resumes. Each time a search engine bot indexes the blog, and does not encounter a "404 Not Found", reputation picks up, again. Slowly, your blog regains its former reputation.

All 3 factors contribute to the loss of reputation, while the blog is offline - and to the regaining of reputation, when the blog is restored. This is similar to the effect of re indexing after the URL is changed.

How much reputation is lost and regained will vary, from blog to blog.
  • Each blog has different readers, with differing links in their blogs and websites.
  • Each blog has different readers, with differing inherent reputation.
  • Each blog has differing search engine relationships, with differing inherent reputation.
The direct result, of all of this, explains the frantic posts, in Blogger Help Forum: Something Is Broken
My blog was deleted by Blogger. How promptly can I get it restored?

If this threat concerns you, use Google 2-step verification, to protect your Blogger / Google account - and your blogs - from hacking. And be discrete in advertising and publishing your blog.

>> Top

Saturday, 8 June 2013

Comment Spam And Referer Spam Has Various Purposes

One of the most intriguing subjects discussed in Blogger Help Forum: Something Is Broken involves the seemingly purposeless spam which torments us in our comments and our Stats logs.
I see this random garbage on my blog - and the sites advertised are complete junk. Is there any actual reason for this?

Interestingly, both nice blog spam (in our comments), and referer spam (in our Stats logs), have purposes - though with the continually varying content used in both, it all looks very much like random garbage.

If we analyse the content, structure, and volume of the various spam attacks, we can see patterns - and an understanding of the overall purpose of the spam.

Both our comments - and our Stats logs - are continually assaulted by seemingly random and useless noise, in large volume. This is similar to the random spam which attacks our email.

If you look at enough comment and Stats log spam, you will start to see patterns - and reasons for the spam. The spam, though apparently random in content, is not purposeless.

First, some warning may be appropriate.
  1. If you wish to examine the sites advertised in comment or referer spam, learn to use a proxy server.
  2. Unless you are a computer security expert, with a properly protected (or intentionally sacrificial) computer, do not surf these sites advertised, using an unprotected computer. Avoidance is the best way to protect yourself.
  3. If you do, even inadvertently, surf a comment or referer spam site, quarantine and scan your computer as soon as convenient. If you must surf the sites advertised, while unprotected, diagnosis is the next best way to protect yourself (and others around you).

Examining the comment and Stats based spam diagnostically, you'll see various purposes behind the spam.
  • Spam delivery. It is called "comment spam" / "referer spam", after all.
  • Malware delivery. This is the secondary purpose, known by many people - and the reason why I provide the above advice.
  • Attacks against third party, non spammers. Various third party blogs and websites, who do not subscribe to the service, may be maliciously targeted, by some spam.
  • Strategic malware delivery. Some malware may be packaged in portions, delivered through multiple attacks.
  • Filter poisoning. Some spam may be simply intended to overwhelm the malware / spam detection systems.
  • Email address mining. Some very special comment spam, which I call "Nice Blog" spam, is a very imaginative email address mining technique.

The best way to identify comment and referer spam may be to simply follow the various forum discussions - and observe which spam techniques are reported by multiple blog owners, being assaulted in identical style. As the old saying goes,
If it quacks, it's probably a duck.

>> Top

Thursday, 23 May 2013

Abuse Reporting Is Not For Deleting A Blog For Which You Lost Control

Sometimes, people lose control of their blog, with no ability to regain control - and simply want the blog deleted.
How do I have Blogger delete the blog, for me, since I can't prove ownership?

When advised that Blogger does not delete blogs on behalf of former owners, the next thought by the former owner is to have the blog deleted as abuse.
What category of Abuse should I use, to have a previously owned blog, deleted?

While not genuinely fraudulent, the latter approach is misuse of the Abuse reporting process.

The Abuse Reporting process is properly used to report blogs owned by another party, for TOS Violations.

Blogger currently provides the Blogger Help: Report abuse form, which has specific categories of abuse.
  • Legal issues
  • Hate speech, violent or crude content
  • Harassment
  • Spam, phishing, or malware
  • Nudity
  • Posting of private information
  • Impersonation
All of those categories refer to content published by another person. Nothing there is for reporting a blog previously owned, with control lost by negligence.

Whatever the loss of control, it's yours to correct.
  • Corporate blog, control lost.
  • Personal blog, control lost.
  • Team blog, control stolen.
None of these scenarios warrant abuse / TOS violation reports.

Note a very specific warning, about misuse of the DMCA Violation complaint.
Please note that you will be liable for damages (including costs and attorneys' fees) if you materially misrepresent that a product or activity is infringing your copyrights. Indeed, in a recent case (please see http://www.onlinepolicy.org/action/legpolicy/opg_v_diebold/ for more information), a company that sent an infringement notification seeking removal of online materials that were protected by the fair use doctrine was ordered to pay such costs and attorneys fees. The company agreed to pay over $100,000. Accordingly, if you are not sure whether material available online infringes your copyright, we suggest that you first contact an attorney.

If your company publishes a blog, you are responsible for retaining control of the blog, as with any corporate asset. If you lose control of a corporate asset, you don't contact the vendor, and demand that they delete the asset that you lost. Your problem is with the current owner - whether it's a civil or criminal issue, it's not the responsibility of the vendor to correct an ownership problem.

If the blog was personally yours, and you forgot the account name and / or password, it's your responsibility to regain control.

If the blog was under team ownership, and another team member stole the blog, your problem is with the former team member. If the team member was (righteously or spuriously) classified as a non repentant spammer, you may have to get the blog reviewed, to regain control.

If you believe that you can prove your right to control (or delete) the blog, you may hire a lawyer, and have a judge certify your identity. None of these cases can be resolved, using abuse / TOS violation reporting.

>> Top

Thursday, 9 May 2013

Empty Or New Blogs Can Be Classified As Possible Spam Hosts

We're seeing a few recent reports, in Blogger Help Forum: Something Is Broken, from owners of empty and / or new blogs, about spurious spam classification.

Very few owners of empty or new Blogger blogs understand why their blogs should be classified as possible spam hosts, by the Blogger anti-spam processes. Most blog owners seem to think that only blog content is considered, in spam classification.

Spam classification considers many characteristics of a Blogger blog, in classifying any blog as a possible spam host.

Blog content is an obvious - but not the only - factor in spam classification. Given previously observed behaviour of spammers, many characteristics of blogs, besides simply the extracted and analysed content, are used in classifying possible spam blogs. Using fuzzy spam classification techniques, one might also consider
  • Overall behaviour in Google, by the owner.
  • Past posting habits of the owner.
  • Previous classification of similar blogs.

Some spammers are active in multiple Google activities and features. It's possible that some spammers even try to make their spam in Blogger harder to detect, by spreading their activity across other Google functions. Some spammers may not realise that spammy activity in other Google areas can be tracked, and included by Blogger spam classifications processes.

Blog owners who use one or more techniques involved in setting up and maintaining spam blog farms may be classified as spammers - and their blogs then classified as possible spam hosts. The term "blog owner" must itself be considered fuzzily, as some spam blog farms contain blogs owned by multiple Blogger accounts and profiles. Some Blogger accounts, similar to known spammer accounts - even with no blogs owned, or with empty blogs published - may then appear as possible spam hosts.

Empty blogs, that appear similar to blogs in known spam farms, may themselves appear as possible spam hosts. Various details such as blog name, blog design, and use of various blog accessories and features, can make a blog appear similar to known spam blogs - with no other content.

Given the need for Google to reduce the volume of spam blogs, fuzzy spam classification might use any of the above details, in classifying any empty or new blog as a possible spam blog. This will, unfortunately, lead to spurious spam blog detection. Given the ability of spammers to publish multiple blogs in the Blogger name space, classifying empty and new blogs is necessary, in making it possible for Google to keep up with spammy activity.

>> Top

Sunday, 28 April 2013

The Mysterious "Deleted blogs" Dashboard Link

Occasionally, we see signs of confusion, in Blogger Help Forum: Something Is Broken.
Where is the "Deleted blogs" link?
or
How can I recover my blog, if there's no link on the dashboard??
These blog owners don't understand that "Deleted blogs" only appears, when there are deleted blogs that can be recovered.

Not all blogs, having vanishing from the dashboard, will be recoverable by the owner.
  • A blog deleted / locked after hacking activity was detected won't be recoverable.
  • A blog owned under another Blogger account won't be recoverable.
  • A blog that does not exist won't be recoverable.
If the Blogger account owns no blogs that are recoverable, there won't be a "Deleted blogs" link on the dashboard.

If the Blogger account owns other blogs, that are not currently deleted, those blogs will be listed. If the Blogger account owns no recoverable blogs, the blog owner sees a monolithic message
You are not an author on any blogs.

In some cases, the blog owner will be advised to clear cache, cookie, and sessions - then restart the browser, and login to Blogger. In other cases, the solution will be to wait 24 to 48 hours, and check again. Just don't waste time looking for a link that may not be there - and try to understand why the link may not be there.

>> Top

Monday, 15 April 2013

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

Tuesday, 9 April 2013

Consider, Carefully, The Decision To Use A Third Party Commenting System In Your Blog

Not all Blogger blog owners appreciate the features provided, in Blogger native commenting.

Some suggest that third party commenting systems, such as Disqus, provide a superior service. It's possible that, to some, third party commenting systems are more feature rich - but only Blogger native commenting provides one essential feature, in comment moderation.

Blogger commenting is one component, in the global Blogger / Google spam classification and mitigation strategy.

Blogger blog classification, Blogger commenting moderation, and various Google services, all contribute globally to spam detection, and to spam removal, in Google Internet space. Each service both provides input into - and accepts input from - other services.

Third party commenting products, while they may have some interesting design features that Blogger won't include, won't necessarily contribute to the Blogger blog spam classification effort, or to the community commenting moderation process. Nor will they accept input from Blogger blog spam classification, or from the community comment moderation process.

If you, as a blog owner, believe that Disqus - or other non Blogger commenting products - provides more useful service to your blog, you're entitled to use any service, that you can make work, in your blog. It is, after all, your blog - and this is one feature in our blogs which Blogger / Google leave to our discretion.

As with all third party accessories and services, however, you will get limited support, for any problems. If you break your blog, you'll have only yourself (or the provider of the third party service) to support your problems. You may even see the blog deleted or locked, because of suspected malware.

When you use a third party commenting system, there are two details to consider.
  1. Integration of existing comments.
  2. Post template modification.

When you install a third party commenting service, you'll have the service import existing comments into their database. And, you will have to install the necessary code into the post template - and deal with ongoing changes to the post template, in the future.

If, in the future, you want to return to use of Blogger commenting, you'll have both of the above details to consider, in reverse. Third party services, while they may provide importation of Blogger comments into their database, may not provide a reverse service. Nor are they likely to provide easy reversal of post template changes - particularly as the Blogger post template may have been changed after installation of the third party service.

If your blog uses Disqus, right now, you'll probably find it easiest to refresh the post template, to return to Blogger comments. If you have various custom tweaks in the post layout, you may not find this to be a pleasant solution.

If you are contemplating changing your blog, to use Disqus - or another alternate commenting system - you may do well to consider all of these issues, before changing.

>> Top

Monday, 8 April 2013

Blogger Blogs Cannot Be Used As Gateways

We see evidence of confusion, from time to time, in Blogger Help Forum: How Do I?.
How do I move an established blog to WordPress (or any other platform), while retaining the history, reader interest, search engine reputation?
Some blog owners think blog readers are cattle (to be herded from blog to blog) - or monkeys (to be attracted by shiny things).

We've known for some time, that Blogger blogs cannot be used as gateways, with traffic automatically redirected from one blog to another - or from a blog to a non Google website. Use of traffic redirection scripts is a known cause of blogs classified as malware hosts.

If you wish to relocate a Blogger blog in another hosting service, you can always publish your Blogger blog, and a non Google blog / website, as dual hosts, in a non BlogSpot domain.

With your Blogger blog and non Blogger website published to the same domain, you can then combine the two, dynamically. Just remember to add unique content to each, periodically, to retain search engine reputation.
  1. Publish your Blogger blog to a host in your custom domain.
  2. Publish your WordPress (or any other platform) blog to a host in your custom domain.
  3. Combine the two blogs.
  4. Let your readers access either blog, as their choice.
  5. Update both blogs, to retain search engine reputation, regularly.
  6. When the WordPress (or any other platform) blog receives enough reputation and traffic, make the Blogger blog into a stub blog.

Just don't build a maze of blogs and web sites - and don't waste time or money artificially developing traffic. Blogger blog readers are attracted by interesting and useful content - and are retained by new content, added periodically.

And don't try adding clever code, to shuffle your readers from one blog to another.

>> Top

Tuesday, 12 March 2013

Comment Moderation Provides Limited Movement Between Queues

Not every blog owner understands the limited ability to moderate comments - and to correct a moderation decision, previously made in mistake.

We see occasional evidence of confusion in Blogger Help Forum: Something Is Broken.
I deleted a comment by mistake. How do I get the deleted comment back?
and
I marked a comment as "Not Spam" - but now it's not in "Awaiting moderation"!
The ability to move comments, in the moderation queues, is limited - and it's asymmetrical.

There are 3 queues, which are visible from the dashboard Comments wizard.
  1. Published.
  2. Awaiting moderation.
  3. Spam.

Besides the 3 queues, there is a fourth possible state - Oblivion, which is not visible, and from which comments cannot be moved. Some blog owners may confuse Oblivion with a desktop computer standard - "Trash Can". This confusion can cause problems.
  1. The contents of "Trash Can" can be viewed. Comments in Oblivion cannot be viewed.
  2. The contents of "Trash Can" can be recovered. Comments in Oblivion cannot be recovered.

A comment, starting out in the "Awaiting moderation" queue, can be moved in several ways.
  1. Into "Published", using the "Publish" button.
  2. Into Oblivion, using the "Delete" button.
  3. Into "Spam", using the "Spam" button.

A comment, in the "Published" queue, can be moved in two ways.
  1. Into Oblivion, using the "Delete" button.
  2. Into "Spam", using the "Spam" button.

A comment, in the "Spam" queue, can be moved in two ways.
  1. Into "Published", using the "Not spam" button.
  2. Into Oblivion, using the "Delete" button.

It's apparently possible to move comments back and forth, between "Published" and "Spam". Presumably, either movement provides some training of the comment spam filters.
  1. From "Published" to "Spam", using the "Spam" button.
  2. From "Spam" to "Published", using the "Not spam" button.

There is no similar symmetry of movement, for the "Awaiting moderation" or Oblivion states.
  1. A comment in "Awaiting moderation" can be moved into either of the other 3 states - Oblivion, "Published", or "Spam". Once moved, a comment cannot be moved back into "Awaiting moderation".
  2. A comment can be moved into Oblivion, from any of the other 3 states - "Awaiting moderation", "Published", or "Spam". Once moved, a comment cannot be returned from Oblivion.

If you're moderating comments, you need to understand the asymmetry. Once you move a comment, and you recognise a mistake, you cannot always move it back to correct your mistake.

>> Top

Sunday, 10 March 2013

Blog Owners, Unable To Request Restore Of A Deleted Blog

One of the more intriguing issues, seen in Blogger Help Forum: Something Is Broken, involves people unable to recover control of their blogs.
I recently changed ISPs, and now I can't login to update my blog.

Occasionally, this issue becomes more complicated, because the blog is deleted - and the owner can't request that it be restored, using the automated review request wizard. Sometimes, the would be blog owner may to try to bypass the current blog recovery policy, by claiming special circumstances.
The blog has been deleted. I received no suspicious activity or password change notification emails, or emails of any kind related to my blog.

What is the story here? Can blogs just disappear from the Blogosphere, without the involvement of the blog owners - and be unrecoverable?

Recovery of a deleted blog starts with the requirement that only a blog owner can un delete a deleted blog - and this is where many mysterious disappearances start.

Since a Blogger blog is the property of the owner, and the owner is allowed to delete a blog any time required, it would not be right to let people who are not the owner un delete a blog - or demand that the blog be un deleted. To enforce this requirement, Blogger added the dashboard based Restore wizard.

Since only the owner will have the deleted blog listed in their dashboard "Deleted Blogs" list, only the owner can request restore of the blog in question.

The dashboard Restore wizard serves blog owners, with blogs deleted under various circumstances.
  • Deleted by the owner.
  • Deleted by Blogger, as a suspected spam host.
  • Deleted by Google, for TOS Violation.
Any deleted blog will appear in a special dashboard list, "Deleted Blogs" or "Locked Blogs" - when it can be recovered. If the blog is not recoverable by the owner, there may not be a link.

There are specific cases where a deleted blog may not be recoverable using the recovery wizard.
  • The blog is locked, pending integrity check (following account lock for suspicious activity).
  • The blog is owned under a different Blogger account, and is listed on another dashboard, under "Deleted blogs".
  • A blog owner deleted the blog, long ago - and the blog is no longer recoverable.

A blog locked, pending integrity check, cannot be requested for restore. The owner has to first have the owning account unlocked. Similar to the account recovery process, Blogger / Google will require that the owner provide proof of ownership, before the account will be unlocked. With the account unlocked, security specialists will inspect each blog owned by the account, and verify that each does not contain evidence of tampering by a temporarily successful hacker.

While a blog is under integrity check, it won't be listed on the dashboard of the owner - either under "Deleted blogs", "Locked blogs", or "My blogs". Neither the owner, nor any third parties, will be able to do anything except wait, patiently.

Blogs found to contain malware can be locked as TOS Violations, with the owner later required to remove the malware found. This requirement will apply for malware installed by the owner (intentionally, or unintentionally), or for malware installed by a hacker.

With a blog locked pending malware removal, the owner is given the benefit of the doubt, and allowed to simply remove the malware, no questions asked. In some cases, Blogger may be able to assist by providing specific identification of the malware found - but this won't happen, consistently.

A blog owned under another account must be un deleted by the owner of the other account. Again, only a blog owner can have a blog restored - whether deleted by an owner, or by Blogger / Google.

A blog deleted over 90 days previously cannot be recovered. It won't appear on the dashboard of any (former) owner, since it can't be recovered.
It's dead, Jim.

The basic rule is simple. If your blog was deleted, and if you're able to un delete it (or request un deletion), you'll have a link on your dashboard. If a blog is not listed on your dashboard, you can't request, with any predictable success, that it be un deleted - any more than you can demand that a non deleted blog be restored to your control.

>> Top

Sunday, 3 March 2013

Some Blogger Blogs Being Locked As Malware Hosts, Because Of Malicious JavaScript

For a long time, we've been dealing with various malware / spam mitigation issues, in Blogger Help Forum: Something Is Broken.

Recently, malware detections, long simply identified as "Malicious JavaScript" in the well known Spam Appeal Guidelines, was given its own identity, and a separate classification / appeal process. We're now seeing several common types of JavaScript, included in blogs which are typically mentioned in forum reports.

It may be helpful to describe some examples of JavaScript code being seen, so blog owners can avoid making the same mistakes, by not including these scripts in their blogs.

There are 3 common types of JavaScript applications, found in many blogs with the owners requesting review / unlock action.
  1. CPA / Cost Per Action.
  2. Traffic Redirection, targeting other blogs / websites.
  3. Traffic redirection, targeting the canonical URL for the host blog.


CPA / CPALeads / Cost Per Action, and similar online marketing terminology, involves providing a reward for viewing a blog, or for subscribing to the blog feed. Some CPA scripts may be used to collect email addresses, also known as "email address mining", later used for hacking activity or spam distribution.

CPA scripts present another problem. Since Blogger blogs are intended to reward the readers by providing interesting and unique content, blogs which use CPA may be improperly designed or maintained. Blogger wants the blog owners to publish blogs which entertain or inform their readers - not blogs which require artificial or ingenious techniques to generate traffic, and visitor activity.

Traffic Redirection, targeting other blogs / websites is a technique enjoyed by many hackers and spammers. The use of some blogs as gateways, leading to redistributors, which in turn lead to payload blogs or non Google websites, is part of many hacking / spam attacks. Google is trying to restrict the use of Blogger blogs as malware / spam hosts - and actively prevents scripts, which only shuffle readers from one blog to another, without choice.

Even though Blogger will not encourage you to move your blog, to Tumblr, Weebly, WordPress, or wherever, you are allowed to do this - if you feel the need.
Hello, faithful readers:

This blog is now hosted at my new blogging host. Please update your blog lists and bookmarks!
If you must do this, it's OK to post a notice, in your Blogger blog. You can even put a link, to the new blog, in the notice. You just can't use JavaScript, to automatically send the reader to the new blog.

Traffic redirection, targeting the canonical URL for the host blog, is a technique used by some blog owners who perceive Country Code Alias Redirection to present a problem. Some accessories installed on their blogs, and various non Google services which may be used to provide activity on their blogs, may not properly reference the canonical URL tag included in all Blogger blogs.

Since Blogger / Google wants all Blogger blog owners to benefit from improved world wide access to Blogger blogs, blogs which employ automatic canonical URL redirection may damage the effect of CC alias redirection. Blogs which host scripts which immediately redirect readers to the canonical URL, and are considered undesirable by any host government, may force an offended host government to block the entire Blogger service, in their country.

To prevent malicious misuse of Blogger by hackers and spammers, and to encourage effective long term use of Blogger by legitimate blog owners, Blogger / Google may detect any blogs which use these types of scripts as part of their general malware / spam classification strategy. Given the ability and willingness of the blog owner, to remove the JavaScript code in question, most blogs can be returned to service - but each blog will remain offline, until the removal is verified.

It's to everybody's benefit to identify, and to avoid use of, these scripts in our blogs, before it's too late. If your blog contains one of these scripts, why not remove the problem now, instead of waiting until you too have to post your problem report, in the forum
Help me! My blog was just locked for
MALICIOUS JAVASCRIPT
What do I do, now?

>> Top