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, unique, 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. That could make your blog look like one member in a well planned spam blog farm - and leave you reporting

Help! Blogger just deleted my blog!!

.

Read More

The Free Domain Registration Service "co.cc" Appears To Be Down

Some Blogger blog owners, trying to save a few dollars while publishing their blogs to a non BlogSpot URL, have used the free service "co.cc" for registering their domains.

As "co.cc" increased its base of "customers", their reputation for providing free registration grew - and they became popular with scammers and spammers.

Last year, Google, weary of the overall poor search engine reputation of co.cc customers, de indexed all websites registered by co.cc. This week, co.cc apparently stopped serving DNS information for its "customer domains".

Strictly speaking, "co.cc" was not a registrar - and the blogs and websites published by its customers were not using registered domains.

"co.cc" was the domain "co", registered by its owner, and providing subdomains.

The "Top Level domain co.cc" - which by its name implied an Internet service operating from the Cocos (Keeling) Islands - was in fact the domain "co", operating out of Korea, and registered in the Cocos (Keeling) Islands. All "domains" given out by "co.cc" were in fact sub domains to the domain co.cc - and this is where the problem started.

All blogs and websites, published to a "co.cc" subdomain, were aggregated by the search engines as the "co.cc" domain. As the number of co.cc registered scammy and spammy websites increased, their search engine reputation dropped.

Non spammy blogs and websites either went out of business, or were transferred to legally registered domains, because of the low reputation and lower search engine originated traffic.

The owners of "co.cc" realised that their scam had been outed, and closed down.

Finally, the owners of co.cc - supposedly "JONG SUNG, KIM" of "GOYANG,GYEOUNGGI" - realised that their run was over, and that they could no longer hide their scams and spams behind legitimate blogs and websites. Apparently, they have now shut their doors.




The old adage comes to mind.

You don't get something for nothing.

If you published to a "co.cc" subdomain, you have to publish back to BlogSpot.

If you registered your custom domain using co.cc - and your blog is now offline - you're going to have to publish the blog back to BlogSpot, to get it online again. If you want to use a domain URL, you have to repeat the custom domain setup process - starting with a new, properly paid for, domain URL.

---

(Update 2015/02): We now have more of the same, from "co.vu".

---

A free ".co.cc" "domain", when it was working, was worth precisely what you paid. Now, it's worth less.

Read More

How Not To Make Your Blog Private

Blog owners have been asking, for years, how to protect their blogs against viewing by undesired or unknown readers.

How do I password protect my blog?

When told that Blogger password protection involves membership invitations, accepted using a Blogger Google account, some would be private blog owners decline the suggestion.

That's too complicated for my readers! Can't I just give everybody a password?

But Blogger does not use common passwords.

Some blog owners, who are technically astute, find add on template code, provided by third parties - which demands a password, in a popup window, to continue. This is where their problems start.

The addition of third party supplied JavaScript code, to our blogs, has always been a dodgy process.

With third party JavaScript code used to provide password protection against unknown readers, this is even more hazardous to your blog. From time to time, we have a blog owner who installed password protection code in his blog template - and subsequently found his blog locked.

I received email saying that my blog has been removed, and has been marked as spam. The email is as follows:

Your blog has been reviewed and confirmed as in violation of our Terms of Service for: MALICIOUS_JAVASCRIPT. In accordance to these terms, we've removed the blog and the URL is no longer accessible.

Can you please review and unlock my blog?

But the story does not end there. Subsequent review of the blog was denied, by Blogger Support.

Your password prompt is not dismissable - and forces users to close their entire browser session, as the Cancel button does nothing. This is malicious behavior, and prevents anyone one on our team from even reviewing your blog content.

This leaves the blog owner with a deleted / locked blog, and no chance of getting the blog back.

Besides the potential threat above, which becomes actual only after spam classification detects the add-on code as malicious, any security expert will recognise two reasons why this solution is worthless.

1. JavaScript code can be blocked, by any reader with a well implemented security policy.
2. If not blocked, anybody can view source code and find the "password" right there, in plain sight.

This "solution" is therefore worthless for two reasons.

1. It is risky.
2. It does not work.

Why risk loss of your blog, for a risky solution that does not work? There's only one way to protect your blog from unknown readers.

1. Send each would be blog reader a membership invitation, using the Permissions wizard.
2. Instruct each reader to open and accept the invitation, using any preferred Blogger account.

Don't script your blog, and risk deletion - and incidental damage.

Read More