Latest News

Showing posts with label Plan First. Show all posts
Showing posts with label Plan First. Show all posts

FeedBurner, And Blogs Unwisely Deleted Or Renamed

Some blog owners delete or rename a blog, without proper planning - and later regret their action.

Some spammers track blog name availability - particularly with blog names that contain "English" (and some non English) language words. If a spammer discovers that a given blog name has recently become available, he will publish a stub blog to that name - and later, add spammy content.

Why is a spammer interested in recently available names?

A previously unavailable name, now available, has residual value - because it previously had content, and presumably, readers.

If a valuable blog name is made available by the owner, a spammer will take it.

If a blog owner just abandoned a valuable blog name, by deleting or renaming the blog, a spammer is going to make good use of it.

The unwary blog owner will soon get complaints, from former subscribers.

Shortly, the unwary blog owner will see that his blog, recently deleted or renamed, has been re published and is now full of spam. His former readers are now asking why he is filling up their blog feeds with spam. And he has lost control of the blog, that once was his.

Unfortunately, by the time the republished blog name is discovered, the spammer has taken legal control - and is now the rightful owner. And, short of deleting the blog as a TOS violation, Blogger will recognise the spammers right to own a blog that was legally obtained, using a spammer version of "Create blog".

If the unwary blog owner is you, you may be able to correct your mistake.

If a deleted or renamed blog used FeedBurner to distribute a blog feed, it's possible that the remaining readers are subscribed to the FeedBurner feed. This is where you - the formerly unwary blog owner - can correct your mistake.

A hacker / spammer, who now (legally) has control of an abandoned blog, may not have control of the FeedBurner feed, that is feeding from the blog. If you can regain control of the FeedBurner feed, you can redirect it to a different blog.
  1. Setup a stub blog, with one or more posts explaining your mistake.
  2. Edit the FeedBurner feed, to point to the feed from the stub blog.
  3. Publish a post or two, as an apology to your former subscribers.

Setup a stub blog, with one or more posts explaining your mistake.

You cannot do what you should have done originally - publish a stub blog to the abandoned blog name. You can, however, publish a stub blog to any other available and suitable name.

Then add a post, explaining what you did - and why the people reading the new blog (your new stub blog) are (or just previously were) seeing spam, in their bloglists and Reading List.

Edit the FeedBurner feed, to point to the feed from the stub blog.

With a new blog publishing an active feed, edit the FeedBurner feed that is currently re publishing the feed from the spammer owned blog. Change the FeedBurner feed, using "Edit Feed Details", to re publish the feed from your new stub blog.

The current FeedBurner feed, for
The Real Blogger Status, is
http://feeds.feedburner.com /Nitecruzr-Blogging



To change the feed source URL, simply edit the "Original Feed" setting - then click "Save Feed Details".

Publish a post or two, as an apology to your former subscribers.

With your FeedBurner feed now re publishing your new stub blog, publish a post or two explaining what you did. Hopefully, given a couple posts from your (reclaimed) feed that do not contain spam, your former readers may read one of your new posts, and be enlightened.

And the spammer will be none the wiser - until the people who are paying him report that his former spam channel has stopped producing traffic to their website.

---

FeedBurner Feeds, After Deletion / Renaming Of Blogs
FeedBurner Feeds, After Unwise Blog Delete / Rename
FeedBurner, After Blog Unwisely Deleted / Renamed

If you unwisely delete or rename a #Blogger blog, the name that was once yours will have some value to a spammer. If a spammer takes the abandoned blog name, publishes his own spammy content, and distributes it to you former readers, you will be powerless to do anything.

If you are using a FeedBurner feed to distribute the blog feed, however, you can edit the FeedBurner feed, and cancel the spammers channel.

If You Are Not Planning To Renew Domain Registration, Give Your Readers Advance Notice

One of the saddest answers given in Blogger Help Forum: Something Is Broken starts with the naive query
My domain registration expired last month, and my blog is now offline. How do I redirect the domain back to the blog?
The answer here is simple, and does not provide a lot of promise, to the blog owner.
If possible, you may be able to publish the blog back to BlogSpot - but the blog will have to be re indexed from the beginning.
Once the domain registration expires, you cannot use the domain address for reputation or traffic source. Any search engine hit entries, to the domain URL, will be 404 - and there is nothing that you can do, if you no longer own the domain.

If your blog depends upon reputation, or search engine listings, for reader activity - and you are contemplating changing from a non BlogSpot domain address back to a BlogSpot address - you need to plan this change, before you start.

Successful publishing, back to BlogSpot, starts well before registration expiration.
A successful change, back to a BlogSpot URL, starts before the domain registration expires - while you can use the domain to provide reputation, and search engine hits, to the BlogSpot URL. I like to advise people to allow at least a month for any blog to be fully indexed by search engines, when a blog is new.

If the blog is mature, and is indexed under a non BlogSpot URL, the process of re indexing under the BlogSpot URL may be only slightly briefer. A mature blog will have one thing going for it, that a new blog won't - inherent reader reputation.

Reader reputation will help some blogs - not all - survive the transition.
Unfortunately, reader reputation will be good for one thing, when re indexing your blog under the BlogSpot URL - links on the readers blogs, to your blog. If your blog has readers who don't publish blogs, or their own reader list, publicly - or if you let the domain registration expire before starting the process of re indexing the blog - you won't gain a lot from reader reputation.

All of the links on your readers blogs, just like all of the links in the search engine result pages, will be

404 not found

This sight will not provide you with reader traffic, or with any reputation.

Start at least a month before registration expiration.
If you must move from a non BlogSpot URL back to a BlogSpot URL, the time to start is a month before the domain registration expires. This is one of the few times when I will tell you to use domain forwarding. Use the Domain Manager wizard, hopefully provided by the registrar, and setup a "301 Moved Permanently" redirect to the BlogSpot URL - if the domain host allows this.

You'll also want to add a notice on the blog, announcing the change - again, well before the domain registration expires. An HTML / Text notice, visible on all pages, would be best.
This blog will move back to a native BlogSpot URL on (date). Please update your bookmarks now!
Plan the migration, and keep your readers - and maybe your readers readers, who use the links on your readers blogs to find your blog.

If you wait until the last minute, you'll be starting over - completely.
If you wait until the domain registration expires, you'll have nothing to do but publish your blog with new content - and hope that the search engines will continue to pick up the new content under the new URL - the old BlogSpot address. And maybe your current readers will find your blog. Maybe.

Contact Us

24x7 online , we happy to answer you
tamilcypc@gmail.com

Disclaimer

This Blog and its TUT's are intended for educational purposes only, no-one involved in the creation of this TuT may be held responsible for any illegal acts brought about by this Blog or TuT.



Featured Post

Custom Domains And HTTPS Redirection Code