Showing posts with label Redirecting. Show all posts
Showing posts with label Redirecting. Show all posts

Sunday, September 2, 2018

The "w i d g e t s e r v e r" Abandoned Domain Is Now Malicious

We've been dealing with a minor recent deluge of reports, from blog owners reporting mysterious redirection of their blogs.

The original typical report, which started like any report involving a respected Internet service going out of business, was annoying - yet benign.

Today, the status changed to malicious.

Right now, "w i d g e t s e r v e r . c o m" is redirecting to "l i b o s t u d i o s . com".

Please enter your email address to continue.

Many gadgets, long known for redirecting, are again redirecting - recently to "w i d g e t s e r v e r . c o m" - and now to "l i b o s t u d i o s . c o m". As some were diagnosed, a few owners advised that the misbehaving gadget had been installed long ago.

We've seen, so far, a few old (not!) friends. M a u k i e , N e o C o u n t e r, and "S u n a n d M o o n P h a s e" can be seen, in some topics.

A brief sample of forum topics involving "w i d g e t s e r v e r . c o m" mention gadgets previously installed by Blogger, using the "Add a Gadget" wizard. Recently, Blogger cleared out the third party gadgets from "Add a Gadget" - and the gadgets rejected by Blogger are now hosted by ""w i d g e t s e r v e r . c o m". And they are malicious.

We will not sell, rent, or share, your email address. Your privacy is important to us!

Yeah, right.

And what will you do, with my email address?



What more should be said?



For a week, we've been dealing with #Blogger blog owners reporting mysterious redirecting by their blogs. Many helpers have dismissed the issue, as another popular third party gadget publisher gone out of business.

Today, the redirection changed - to an email mining op.

Monday, May 16, 2016

Social Sharing Popularity, And URL Changes

As both custom domain publishing, and social sharing networks, become normal with many blogs, we see anguish when blog owners change the URLs of their blogs, without planning for the effects of the change.
What happened to my Likes?
This blog owner - and many others - do not realise that FaceBook counts Likes, based on the URL, not the blog.

FaceBook Likes, and Google+ +1s, are counted by URL - and are not controlled by DNS redirection, or simple name changes. If you rename your blog, you get a new URL with a new popularity counter, in FaceBook and Google+.

Some social sharing services allow for URL changes.

BlogLovin lets you transfer Followers from one URL to another.

BlogLovin, for instance, provides for transfer of Followers, to a new URL - as long as the blog owner owns both the old and new URL.

First, make sure that you've claimed both of your blogs.

Once both blogs are claimed, navigate to "My blog" and select the "Edit Blog Info" option next to your original blog.

From the "Move Followers" dropdown menu, select the blog you'd like to move your followers to and click "Move". This will remove your original blog and move your followers to your new blog of choice.


Start from any BlogLovin page.




Select "Blog analytics" from the drop down menu.




Click "Edit blog info".




Select a blog, from the drop down blog menu, in the "Edit blog info" wizard - and click on "Move Followers".



Whether you have a blog with a new URL, or a blog with multiple feeds and groups of Followers, BlogLovin lets you consolidate / move Followers so you can address your Followers, conveniently.

Blogger Followers stay with the blog, automatically.

With a Blogger blog, and Blogger Following / Google Friend Connect, your Followers Follow the blog - not the URL. You can rename the blog, and change the URL - but as long as you don't change the BlogID, your Followers remain with your blog.

FaceBook and Google+ give you a new counter, for each URL.

Neither FaceBook or Google+ provide a similar option. To both FaceBook and Google+, if you change the URL of the blog, you have a new blog. Google+ Followers - unlike Blogger Followers - Follow the URL.

With custom domain publishing, and the BlogSpot to domain redirect, the attention of your Followers may end up on your redirected blog - but the +1 counter and Followers community, that was based on the BlogSpot URL, stays with the BlogSpot URL. With the blog published to the domain, your blog gets a counter and community for the domain URL - and starts over.

With a BlogSpot to BlogSpot URL change, and a domain to BlogSpot URL change, everything starts over.

FaceBook Likes are counted, within FaceBook - and Google+ +1s are counted, within Google+. Both are based on the URL of the blog which accrues the Likes and +1s. If you change the URL of the blog, you get a new counter - and a new Followers community.

A URL change is effective for different changes, to a Blogger blog.

  • BlogSpot to BlogSpot name change.
  • BlogSpot to custom domain republishing.
  • Custom domain to custom domain change.
  • Custom domain to BlogSpot republishing.

All of these are URL changes - and are treated as a different blog, for most social sharing services.

BlogLovin supports URL changes. Neither FaceBook, Google+, or LinkedIn provides this ability. You change the URL, you start over with +1 / Like count, Followers community, and sharing reputation.



With most social sharing services, if you change the URL of a #Blogger blog, you start over accumulating +1s, Followers, and Likes. BlogLovin appears to be alone, in letting you transfer Followers from one blog to another - if you create a new blog, or change the URL of an existing blog.

https://productforums.google.com/forum/#!category-topic/blogger/ZiozKZOS07Q

https://productforums.google.com/forum/#!category-topic/blogger/gkmBV6s03Ck

Sunday, May 15, 2016

Changing Your Custom Domain - The Next Chapter

We see some blog owners deciding to change their custom domain URLs - and discovering an unexpected limitation, in re indexing the blog, under the new URL
I received email from Google, advising that my previous domain is pulling up a number of 404 errors. I've noticed that these are for individual blog posts.
When you change one custom domain to another, you may not see the domain re indexed, transparently.

Changing a Blogger blog, from one custom domain to another, is a reasonably simple project - if you're able to plan the change.

A domain change should involve simply re indexing the blog.

A simple custom domain name change involves republishing the blog, under a new domain. Retaining readers, and search engine access, requires slightly more work.

Renaming a custom domain - if it involves a BlogSpot rename - becomes significantly more complicated.

Renaming a custom domain - and having the individual post URLs in the old domain working, after the change - will require slightly more effort, than any of the above requirements.

With GoDaddy, using specific settings, you may be able to forward post URLs.

In one forum topic, a domain owner was able to forward a domain, using instructions provided by GoDaddy - so individual post URLs redirect properly.

In the GoDaddy domain settings for the old (original) custom domain, activate Domain Forwarding.

  1. Set the "Forward to:" address to the new custom domain.
  2. Choose the Redirect Type as "301 Permanent".
  3. Choose the Forward Settings as "Forward only".

This may not be the effect seen, by all blog owners. Not all registrars will provide this ability.


This is the GoDaddy DNS wizard, as of 2016.



If your domain was not registered by GoDaddy, you will have a different wizard - and most likely, ""Forward only" will be a different option. Maybe, "Forward without masking" will be a useful description.

Blogger does not support redirection, from blog URL to blog URL.

Blogger does not support redirection, between BlogSpot or custom domain URLs - as transparent redirection would simply encourage spam activity. Any redirection, from the old custom domain, has to be provided by the domain registrar.

Most registrars provide simple DNS forwarding, from one domain to another - if you are able to pay for both domains, simultaneously. Generally, most registrars will setup forwarding, from the old domain to the new published blog URL.

Not all blog owners may get the redirection, for their domain, correct.

With a domain forwarded to the published URL - using most registrar provided instructions - readers who click on the URL to a specific post, using the old domain URL, will find themselves unexpectedly viewing the blog home page, under the new domain. This will cause some confusion.

Search engine bots won't find a specific blog post, under the new domain.

A search engine bot, indexing a specific post, using the old domain URL, will be redirected to the blog home page, under the new domain URL. This will not enhance indexing of the blog.

Some search engine bots may report this as a "404 Not Found" - and blog reputation will suffer.

Here's an example of the problem.


The specific post URL ("www.chloellio.co.uk/2016/05/ fashion-river-island-plus.html") redirects to the main page ("www.chloeincurve.com").



For most obvious benefit, "www.chloellio.co.uk/2016/05/fashion-river-island-plus.html" should redirect to "www.chloeincurve.com/2016/05/fashion-river-island-plus.html" - not to the blog main page "www.chloeincurve.com".

Let's look at an HTTP trace. This shows an individual post in the blog, with forwarding provided by GoDaddy.

http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://www.chloellio.co.uk/2016/05/fashion-river-island-plus.html&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7978.66.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/50.0.2661.91+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO

Sending request:

GET /2016/05/fashion-river-island-plus.html HTTP/1.1
Host: www.chloellio.co.uk
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7978.66.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.91 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 79.170.40.4
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:

HTTP/1.1·302·Found
Date:·Sun,·15·May·2016·17:17:57·GMT
Server:·Apache/2.2.24·(Red·Hat)
Location:·http://chloellio.co.uk/2016/05/fashion-river-island-plus.html

http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://chloellio.co.uk/2016/05/fashion-river-island-plus.html&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7978.66.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/50.0.2661.91+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=TXT

Sending request:

GET /2016/05/fashion-river-island-plus.html HTTP/1.1
Host: chloellio.co.uk
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7978.66.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.91 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 79.170.40.4
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:

HTTP/1.1·302·Found
Date:·Sun,·15·May·2016·17:17:58·GMT
Server:·Apache/2.2.24·(Red·Hat)
Location:·http://www.ChloeInCurve.com

http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://www.ChloeInCurve.com&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7978.66.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/50.0.2661.91+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=TXT

Sending request:

GET / HTTP/1.1
Host: www.ChloeInCurve.com
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7978.66.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.91 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.28.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:

HTTP/1.1·200·OK(CR)

<meta·content='blogger'·name='generator'/>
<link·href='http://www.chloeincurve.com/favicon.ico'·rel='icon'·type='image/x-icon'/>
<link·href='http://www.chloeincurve.com/'·rel='canonical'/>
<link·rel="alternate"·type="application/atom+xml"·title="ChloeInCurve·-·Atom"·href="http://www.chloeincurve.com/feeds/posts/default"·/>
<link·rel="alternate"·type="application/rss+xml"·title="ChloeInCurve·-·RSS"·href="http://www.chloeincurve.com/feeds/posts/default?alt=rss"·/>
<link·rel="service.post"·type="application/atom+xml"·title="ChloeInCurve·-·Atom"·href="https://www.blogger.com/feeds/5573572064729110417/posts/default"·/>
<link·rel="me"·href="https://www.blogger.com/profile/03895481660022671513"·/>
<link·rel="openid.server"·href="https://www.blogger.com/openid-server.g"·/>
<link·rel="openid.delegate"·href="http://www.chloeincurve.com/"·/>

Even if the domain, redirected to the new domain home page, does not generate a "404", blog reputation will not benefit. An individual post, will not be indexed immediately, when hidden behind the home page.

Not all registrars will help you change domain URLs - and retain post URLs.

If you are going to change custom domain names - and transparently redirect readers and search engines, you will need the extra effort, as described above.

Alternately, simply forward the domain, to the published Blogger URL (generally, the "www" domain host) - then concentrate on getting the blog re indexed, under the new URL. Once the blog is completely indexed under the new domain URL, people won't bookmark the old domain - and the new domain URL will be the reference, for the blog. That's what you want, at the end of the day.

Your readers will see the home page of the blog, when clicking on individual posts, indexed under the old domain URL. Then add a Featured Post, mentioning the domain change - and maybe setup one or both blog searches, for reader convenience.



It's possible to redirect a #Blogger blog, as published under a custom domain, to a new domain. It's not always possible to transparently redirect an individual post URL, to the new domain, however.

If you change your custom domain, you may have to expect some problems from readers and search engines.

https://productforums.google.com/d/topic/blogger/ZiozKZOS07Q/discussion

https://productforums.google.com/d/topic/blogger/9rTL7U2ZMvU/discussion

https://productforums.google.com/d/topic/blogger/Yd5qUg77wUw/discussion

Saturday, May 7, 2016

Blogger Magic - Supporting A BlogSpot URL Change

Blog owners are always changing the URLs of their blogs - then asking why Blogger does not provide automatic redirection, to the new URL.

We see the occasional query, in Blogger Help Forum: Learn More About Blogger.
How do I redirect my readers, to my new URL?
And this is a need that will likely go unfulfilled.

If Blogger provided automated redirection, spammers would abuse it, as part of a spam publishing strategy.

Blogger wants to keep the Blogger infrastructure as free from spam, as possible.

Changing the URL is simple enough.

Just use the Publishing wizard, in the Settings - Basic page, and Edit the "Blog Address". Subject to availability, your blog will have a new URL - as you watch.


The change is not difficult. Just Edit "Blog Address".


But with a new URL, unplanned, you'll lose traffic.

Blogger does not support automated blog to blog redirection.

Trying to keep the Blogger ecosystem clean from spam, Blogger actively discourages automated redirection. Neither JavaScript or meta refresh redirection is recommended.

You can use passive redirection, though - and give your readers the choice, to read the blog using the new URL.

  • Setup a blog cluster.
  • Setup a stub blog, at the old URL.

Setup a blog cluster.

Publish a blog at the old URL - and pair the old and new blogs, actively. There are a number of possible techniques to use, to combine two blogs as equals.

You will need informative, interesting, and unique content, for both blogs, to get the most from this approach.

Setup a stub blog, at the old URL.

Publish a blog at the old URL - and add a single post, advising your readers about the change - with a link, taking them to the new blog. You can use a custom 404 display, to collect all existing links to posts in the blog, which will take your readers to the single post.

A Featured Post is perfect, as the single post in the stub blog.

You can redirect the blog posts feed, even though you can't redirect the posts themselves. Just redirect the old blog feed, to the new blog posts feed URL.

Combine the two approaches, if you like.

There's no need to consider the two approaches as mutually exclusive. You can use techniques from each, if you like. Simply pick an approach that suits your readers.

Just don't look for automated redirection. That's not likely to happen.



Some #Blogger blog owners decide to change the URL of their blog - then ask how to setup automated redirection, from the old URL to the new. That is, however not likely to be an option provided, or even allowed, by Blogger.

Thursday, March 31, 2016

CloudFlare, Custom Domain Publishing, And HTTPS

A few blog owners, who publish blogs published to custom domains, are becoming impatient, waiting for Blogger Engineering to finish the Blogger upgrade to support HTTPS / SSL.
If I get a domain through Google Domains, will I be able to get HTTPS?
Unfortunately, no. HTTPS / SSL is simply not available, to blogs published to custom domains.

HTTPS is not available, for non BlogSpot published blogs.

Whether registered by eNom, GoDaddy, or Google Domains, it simply is not possible to publish a non BlogSpot URL as a supported custom domain, and make HTTPS / SSL available. CloudFlare, a supposed alternative, does not produce a supported custom domain.

A proxied CloudFlare domain looks like malicious redirection.

In some cases, a CloudFlare DNS "solution" tried by some blog owners, will look like dangerous / malicious redirection. Some blogs will show up as "Deceptive sites", aka "phishing".


Some blogs using CloudFlare, for custom domain publishing, will be classified as "Deceptive" sites.



Others will produce alarming warnings about malware.


"This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware."




Click on "Details".



Look at the warning.

Phishing sites pretend to be other websites to trick you.

And there is the typical Dig log, with a redirecting proxy service, like CloudFlare.

kireisubs.id. 300 IN A 104.27.133.198
www.kireisubs.id. 300 IN A 104.27.133.198

or

topmovies21.biz. 300 IN A 104.28.0.106
www.topmovies21.biz. 300 IN A 104.28.0.106

This is the basis for malware / phishing classification.

Any observed malware warning is generally a false positive - most custom domain published blogs do not contain malware. Even so, it's not likely that the "Deceptive site" classification will be easily corrected - or the malware warning interstitial display removed.

And this is one more blog owner, who must next be provided instruction to correct the DNS addresses.

Having corrected as instructed, DNS addresses will be asymmetrical, and righteous.

kireisubs.id. 86400 IN A 216.239.32.21
kireisubs.id. 86400 IN A 216.239.34.21
kireisubs.id. 86400 IN A 216.239.36.21
kireisubs.id. 86400 IN A 216.239.38.21
www.kireisubs.id. 86400 IN CNAME ghs.google.com.

With DNS corrected, Google shows "Not dangerous" - but the warning still displays.


"Not dangerous".




Note "CloudFlare" is still seen as the host.




You can report an error, to SafeBrowsing.



False classification now requires time consuming site review.

Use "Report Incorrect Phishing Warning", if you believe the site is safe.

Finally, get the site reviewed, from the Security Issues page in Security Console (Webmaster Tools) - Security Issues.

And while the blog remains offline, search reputation - and the owner - will suffer.



Some #Blogger blog owners want to provide blogs published to custom domains - and offer HTTPS connectivity. Since Blogger cannot provide custom domains with HTTPS right now, the blog owners are using CloudFlare, which provides an HTTPS proxy.

Unfortunately, a CloudFlare proxy looks like malicious redirection - and blogs using CloudFlare are being labeled as "Deceptive" sites.

https://productforums.google.com/forum/#!category-topic/blogger/ApuJ58a4-kg

https://productforums.google.com/forum/#!category-topic/blogger/-LoJCeX6DEA

https://productforums.google.com/forum/#!category-topic/blogger/DhAFOtJFoCw

Thursday, February 25, 2016

Custom Domain Publishing, And Alias Blocking

Some blog owners setup their new custom domain, check all settings carefully (and correctly) - then find that it does not work.

We see the confusion, in Blogger Help Forum: Get Help with an Issue.
The addresses were right - and all the DNS servers updated correctly. But when I open the website, it does not open. It continuously reloads for 5 minutes and after 5 minutes it shows an error.
It's frustrating, when everything is setup properly - but still no results.

It's also frustrating, when you forget about unsupported tweaks that you made, to the blog - then have to ask for help.

Whenever changing the URL, check for - and remove - any redirecting scripts.

Before you publish a blog to a new URL, you need to check the template, for any redirecting scripts, that you may have previously installed.

<script·type='text/javascript'>
var·blog·=·document.location.href.toLowerCase();
if·(!blog.match(/\.blogspot\.com/))·{
  blog·=·blog.replace(/\.blogspot\..*?\//,·".blogspot.com/ncr/");
  window.location.replace(blog);
  }
</script>

Scripts which redirect - or block redirecting, when the blog is published to BlogSpot - will not work for you, when you publish to a non BlogSpot URL.

You will need to connect URLs, when possible - without scripts interfering.

Any time you change the URL of the blog, you're going to need some ability to link from the old URL to the new URL. Before you change the URL - either BlogSpot to BlogSpot, or BlogSpot to custom domain - check the template, for redirecting scripts.

Any redirecting scripts, that might have helped you with the blog originally published, will be a problem, when you change the URL. Remove any scripts, before changing the URL.

Better yet, don't add redirecting scripts. If you got this far, without having the blog classified as a malware host, consider yourself lucky.



Some blog owners install mysterious scripts, to "protect" against unwanted Blogger features - and forget about their unwise tweaks. When they change the URL of the blog - and the blog, under the new URL reacts to the previously installed tweaks - they are clueless.

If you make unsupported tweaks to your blog, only you can correct problems that arise, later.

Friday, January 2, 2015

Using A Custom Domain Outside Blogger

From time to time, we see questions about using a Blogger / Google custom domain, with publishing services outside Blogger / Google.

Some Blogger blog owners want to combine their Blogger blogs, with non Blogger blogs and websites - and others want simply to move their blogging activity to non Blogger services. And a few think ahead, and wonder how adding or moving to another service will affect the ability of their existing readers to find their blog, and / or their ability to get new readers.

As with using a Blogger blog with an existing non Google domain, this is not a simple project - and to do this properly will require research - and well informed decisions. Some assistance can be provided by Blogger or in Blogger Help Forum: Learn More About Blogger - and other portions of the project will require advice or instruction from the support groups for the new service.

Start by deciding how the domain is to be used, with the new website.

Consider The Options

There are several ways to add / substitute a non Blogger blog / website, in a domain purchased for use with a Blogger blog.

  1. Transfer domain registration, to the registrar, as required by the new hosting service.
  2. Update DNS for the domain, to use name servers, as required by the new hosting service.
  3. Update DNS for the domain, to use only addresses pointing to the new hosting service.
  4. Update DNS for the domain, to use additional addresses pointing to the new hosting service.

Which of these options, that you are able to use, will depend upon requirements of the new hosting service.

WordPress provides detailed instructions, in WordPress Support: Coming from Blogger?. Not all hosting services will be so helpful, however.

Retain / Transfer Existing Traffic

Options #1 - #3 will require you to start a new URL, published by the new hosting service. Blogger will not permit blogs to be used as gateways. You'll have to get your new blog / website indexed, from the bottom up - with no automatic traffic from your Blogger blog.

Any followers or readers, that are associated with your Blogger blog, will have to be redirected to your new blog / website using visual instructions - or at best a clickable link, in a stub blog. You may be able to redirect subscribers - if the new host offers a compatible newsfeed.

You probably won't be able to publish your stub Blogger blog to the domain, though - so chances are, any of these options will leave you starting over - with no instructions to your existing followers and readers, excepting what you provide before moving the domain.

Option #4 will require you to add an additional host, in the domain with your existing Blogger blog. If your new hosting service supports, you may be able to make your Blogger blog and new blog / website equal members of a domain based cluster.

For a domain cluster to be really effective, you will need to maintain both the existing Blogger blog, and the new non Blogger website as separate entities - and have unique content, regularly updated for each.

Access The Current Registrar Dashboard

Whether you transfer domain hosting, or update the domain, you will need access to the current registrar's dashboard.

  • For domains purchased using Blogger / Google "Buy a domain ..." or similar services, access to the registrar's dashboard will require access to the Google Apps / Control Panel utility.
  • For domains purchased directly from the registrar, access to the registrar's dashboard will require an account / password that (hopefully) was setup when the domain was purchased.

You will need access to the registrar's dashboard to obtain the EPP code, required by Option #1 - or to make changes to the domain, required by Options #2 - #4.

You May Need Google Apps Access

Most projects - but not all - which involve custom domains require Google Apps access - and establishing Google Apps access is the most common concern, when access to the registrar's dashboard is needed.

  1. Get access to Google Apps.
  2. That will give you access to the registrar's dashboard.
  3. Retrieve the EPP code, or update the DNS addresses per instructions of the additional / new blogging host service - depending upon which Option you are taking.

In some cases, and if you are considering multiple non Google services, choice of what new service you go with may start with identifying migration / setup options provided by each different service.

Regain Followers, Readers, Subcribers, Search Engine Reputation - And Traffic

A domain moved to use outside Blogger will be similar to a new blog / website - with some characteristics of a renamed Blogger blog, and / or a newly published custom domain blog. Just as all Blogger blogs are unique, so will be any domain migration.

You may consider moving existing blog content, to the new service. This will require planning, and testing.

Both the actual movement of the content - and preventing Blogger spam classification, if you move the content - will be important.

You need to understand all of these issues, to regain traffic sources. Blog / website traffic is a complex subject.

Respect Your Existing Audience

If the question of existing / new followers, subscribers, and readers, and search engine reputation, resulting from the move, is a serious issue with you, you may want to plan your move from Blogger with great care.

You won't be able to blatantly redirect your existing readers to your new website - you will need a carefully planned dual website publishing strategy.

Start With The Support Group For The Chosen Service

If you are going to host a blog or website outside Blogger / Google, you must start with instructions from the support group for the new blog / website. DNS is a key issue, in any domain migration - whether BlogSpot to non BlogSpot, or non BlogSpot to non Google.

---

Occasionally, a #Blogger blog owner decides to move their blog to a non Google website. Starting with advice in Blogger Help Forum, the owner learns that many necessary decisions, related to a hosting change, require support from the new website host.

Not every blog owner realises why setting up and publishing a Blogger blog is so simple, until they have to make decisions about hosting outside Google.

Sunday, November 2, 2014

Custom Redirects, And The Mobile Template Redirect, Are Now Compatible

One of the neatest features added to Blogger, this decade, has to be the Custom Redirects.

For many years, we asked, over and over, for the ability to optionally publish a blog with a static home page. 2 years ago, Blogger gave us that ability, and more, with Custom Redirects.

But, Custom Redirects had a problem - it did not work with a mobile template, and a redirected mobile home page. Recently, however, that changed.

If you want a custom home page - and you want to use a mobile template - just add one additional Custom Redirect.

From: /
To: /p/static-home-page.html

Add a second redirect.

From: /?m=1
To: /p/static-home-page.html?m=1

Maybe, even add a second redirect, to a mobile page.

From: /?m=1
To: /p/static-home-page-mobile.html?m=1

Now, you can have your cake - and eat it.

Check out my redirected home page test, from your mobile computer.

Thursday, July 10, 2014

Blogger Magic - A Blog Within A Blog

One of the most fascinating features of Blogger blogs is the various options to organise our content.

Long ago, I wrote a simple article, Adding A Blogger Blog To A Website. That's become one of the most consistently popular posts, in this blog. Most blog owners have multiple interests, and like to organise their different interests, by subject - and have a different blog, for each subject.

Some people like to have a blog, and a website - and host both the blog and website in one Blogger blog, under one URL. For a small blog / website combination, that's an easy way to start out - and a good alternative, to having multiple blogs / websites.

It's easy to create a Blogger blog, and have the blog host multiple virtual blogs and / or websites.

The simplest "blog" uses a static home page, and the posts accessed from Pages, as "Blog".

A static home page - and all posts accessed as "Blog".

First, redirect the Home page to a static page.

From: /
To: /p/Welcome.html

Then add a simple dynamic "Blog" page, using "Configure Page List" - if you want all of the posts visible from the "Blog" tab.

Caption: Blog
Link: /search/label/

But, there are more possibilities.

Organised right, you can do without an archive section.

Done carefully enough, you can maybe display an entire blog without archive pages.

Have enough sections - and consistently use Jump Break on the posts - may let you fit a dozen or so posts onto one index page.

Some people organise blog content, using static pages.

The most obvious solutions for this need - to some people - is to setup static pages, one page / subject. But sometimes, interests / subjects overlap - and material that's published on one static page (as in one blog or website) might be relevant to another page (or blog / website).

I recommend basing the blog on dynamic content - and dynamic accessories.

The easiest way to make all of the content accessible is to add various dynamic indexing and search accessories. But some static structural accessories are useful, too.

Then, add a Pages gadget, if not already added. You can have a linkbar / tab index - or possibly a linklist, positioned anywhere convenient. Or both.

Start by labeling your posts.

First, add labels, to the posts. You can use either the posts index, or post editor, to add labels. You use the former, to add one label to many posts - and the latter, to add many labels to one post.

With the posts well labeled, decide how you want to display the pages.

Dynamic content lets you display one post, in multiple pages.

Using this blog as an example, this post could be useful in my "Labels", "Magic", and "Redirecting" sections of this blog, to start. Look above, at the toolbar. Do you see the "Magic" button?

Hover the pointer cursor over "Magic" - and see what's there.
http://blogging.nitecruzr.net/magic

From: /Magic
To: /search/label/Blogger%20Magic

There's my "magic" blog, within this blog.
Magic

Just as easily, I could have "Labels" and "Redirecting".
From: /Labels
To: /search/label/Labels
From: /Redirecting
To: /search/label/Redirecting

You can separate the "Home" page from the "Blog" page.

Some people want to keep the blog and home page separate. They have 2 labels, "Blog" and "Home". All that they do is publish various posts, to either label - and setup 2 redirects.
From: /Blog
To: /search/label/Blog
From: /
To: /search/label/Home

And there's a blog
Blog

within a blog.

Making things simpler, if you want "Blog" to index all posts (as in an actual "blog"), you don't need to label the posts. Apparently, "... /search/label/ " retrieves everything, instead of nothing.
From: /Blog
To: /search/label/

There are several possibilities for "Home" page content, too.

As an alternate to redirecting the home page to a label search, you can always redirect the Home page to a single post - if that's your preference.
From: /
To: /2014/07/blogger-magic-blog-within-blog.html

And that is a very basic blog, within your blog.

And you can still use static pages, for truly static content.

And one final detail - add one or more actual static pages. For non changing content, that you don't want ending up in a search engine hit page, add a simple static page.

You may have to add the Pages gadget, using "Add a Gadget".

Most blog owners will use the Pages gadget, to index their dynamic and static pages (such as "posts" and "pages"). If the Pages gadget is not already present in the blog, you may use the dashboard Layout page and "Add a Gadget", to add the gadget. Then, use "Configure Page List" to add the pages created.

Saturday, April 26, 2014

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.

Friday, December 9, 2011

Our Reading Lists, Hijacked By Spammers

I've been writing about spammer activities, and about various blog hijacks, for some time. There's a special, rather devious blog hijack, involving spammer activity, that we've been aware of, for some time. In Blogger Help Forum: Something Is Broken, we occasionally see the query
How do I get rid of spam, in my Reading List? I did not Follow this blog!
Nobody will, intentionally, Follow a blog full of spam. In some cases, though, people Follow blogs that are published by naive blog owners, who have been conned by the spammers, into working for them.

The never ending need for more Followers, readers, search engine reputation, subscribers, and traffic, is a frequently expressed concern in Blogger Help Forum: How Do I?.

In discussions outside Blogger Help Forum, one might possibly find suggestions of other, more imaginative ways to get more traffic to your blog. With Blogger blogs, there's a very obscure and easily used feature, that can be used to publicise your blog, randomly, to readers that you would not, otherwise, address.

All that you need do is to redirect your blog feed into a "feed redistribution cloud", that randomly redirects the readers of any blog, to viewing the feed from another blog, similarly using the redirect.

By redirecting your readers, you are exposing them to other blogs, randomly selected. Similarly, readers of other participating blogs are randomly redirected to your blog - and there is the promised publicity for your blog.

This is such a great idea, isn't it? Think again.

  1. Your Followers (and subscribers) want to read the feed from your blog - not from some random blog.
  2. Many Blogger blog owners don't use this feature.
  3. Many users of this feature are not legitimate Blogger blog owners, but publishers of spam blogs and websites.
  4. Should you redirect your readers into a "feed redistribution cloud", the chances are greater that your readers will be reading a blog published by a spammer.
  5. No spammer will redirect the feed from his blog. He's going to keep all of his traffic, to himself
  6. Since no real people knowingly subscribe to feeds from spam blogs and websites, your blog won't be getting any reciprocal crowd of eager would be readers, originating from the spam blogs and websites.
  7. And, we are here.

As a Follower (and not a blog owner), having examined your Reading List and found yourself reading a blog full of spam - that you certainly did not Follow - what do you do? It's a simple - but possibly tedious - task to identify and remove the blog owned by the naive person, who was conned by the spammers, that you are Following.

Having done that, why not go one step further, and help us to help Blogger and Google to interdict the spammer activity?

If you can identify the URL of a blog, that you are Following, that is redirecting its feed in this manner, Blogger / Google can identify and terminate any Google hosted blogs and websites that are advertising this easy, random way to publicise your blog - that is simply another trick used by the spammers, into getting the naive blog owners to do their dirty work.

All that we need is the URL of any blog, that you were Following, that rudely redirects its subscribers (like you) into the "feed redistribution cloud". Blogger / Google can do the rest.

You can comment, here - or start a discussion, in Blogger Help Forum: Something Is Broken - it's your choice. Just help identify the naive blog owners.

Do your part, and help us clean up the Blogger Blogosphere.

Saturday, April 3, 2010

Use The Post Feed Redirect URL, When You Rename Your Blog

When we rename a blog, we use the Post Feed Redirect URL to redirect all feed references, from the old URL to the new feed URL.

When we setup a custom feed for a blog, maybe using FeedBurner, we use the Post Feed Redirect URL to redirect all feed references, from the blog, to the FeedBurner feed. That lets us use a FeedBurner feed without having to change all of the feed links in the blog.

Besides using the Post Feed Redirect URL to setup a FeedBurner feed, you can use the Post Feed Redirect URL when you re publish the blog to a new BlogSpot URL.

Please! Be sure to setup the Post Feed Redirect in the proper direction.

Using the post feed redirect is a simple, 1 - 2 - 3 exercise.

  1. Publish a stub blog, to the old URL.
  2. Determine the URL of the blog post feed, under the new URL.
  3. Set the post feed redirect, for the stub blog.

Publish a stub blog, to the old URL.

Immediately after you re publish the blog to its new URL, you should be setting up a stub blog, to visually point your readers to the new URL. Besides visually pointing your readers, you can re point your subscribers - again using the stub blog.

Determine the URL of the blog post feed, under the new URL.

Copy the updated feed URL from the blog header. Precision is essential when redirecting the feed, so let Blogger do the work for you here - determine the new post feed URL, properly.

Set the post feed redirect, for the stub blog.

Go to Settings - Other, for the stub blog, published to the old URL. Edit the "Post Feed Redirect URL", and paste the new feed URL, as just copied.

When you do this, all subscribers to your blog, under the old URL, should see the blog feed in its new home, with linked content. The search engines, indexing the blog using a sitemap based upon the old URL, should start indexing it using the new URL.

Properly done, this should give your blog, under the new URL, a good start towards regaining the search engine reputation that it had, under the old URL.

Wednesday, March 31, 2010

Renaming Your Blog - Planning The Change Properly

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as a change in the URL, affects the success of your blog. If you republish your blog to a different BlogSpot URL, as with migration to a custom domain, you will not lose any content. Both comments, posts, the template, and all custom settings, will stay with the blog. And if you plan the republishing effort, you can minimise the loss of traffic.

Properly planning the migration, to a different BlogSpot URL, will require different techniques than a simple custom domain republishing.

All 3 URL changes produce similar effects, though - and it's in your best interest to do what you can, to minimise the effects.

  1. BlogSpot to BlogSpot URL change.
  2. BlogSpot to custom domain re publishing.
  3. Custom domain to BlogSpot re publishing.

All 3 changes require your blog to be re indexed by the search engines - and leave the blog with less search engines generated traffic, while being re indexed.

A BlogSpot to BlogSpot URL change is different from a custom domain publishing.

Custom domain re publishing has a feature that BlogSpot to BlogSpot URL changes lack. This will reduce negative effects of the URL change - with the domain properly setup.

With a custom domain republishing, the old (BlogSpot) URL is redirected to the new (domain) URL, using a "301 Moved Permanently" instruction. A "301 Moved Permanently" redirect simply repoints each individual URL in the blog to the new URL.

Unlike a custom domain renaming, you cannot choose an available URL, before you begin.

This post (using the domain URL) is "blogging.nitecruzr.net/2010/03/renaming-your-blog-planning-change.html". I can, alternately, advertise it as "bloggerstatusforreal.blogspot.com/2010/03/renaming-your-blog-planning-change.html". That's the "301 Moved Permanently" redirection, in action. All traffic is forwarded, automatically.

There is no way to add "301 Moved Permanently" redirect to a BlogSpot rename.

Blogger won't provide a "301 Moved Permanently" for a BlogSpot rename, as this would encourage spammers to move their splogs around, endlessly. The best that you can do is to use a stub blog, with proper planning.

If you want the blog offline permanently - or if you don't want other people recreating the blog under its current name, you will want to plan the renaming - just as you would (or should) plan a deletion. If the URL becomes available, the same content / impersonation / privacy issues will exist.

Consider the categories of traffic sources, and the effects.

As with a custom domain migration, you'll want to consider the traffic to the blog, in categories.

  • Blog Feeds - Automated processes, that help your readers track changes to your blog, using a newsfeed reader.
  • Following - The two way community process, that lets you see who your readers are.
  • Google Webmaster Tools - Key diagnostic and management utilities, that - among other things - enable indexing of the blog by the search engines.
  • Search engines - Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.
  • Viewers - People who read your content from their browser.


Blog Feeds are the easiest and cleanest category to redirect. Even though Blogger won't provide a "301 Moved Permenantly" for the blog URL, they will provide this for the feed URL, using a blog post feed redirect URL.

With the post feed enabled for both the live blog (under the new URL), and the stub blog (under the old URL), set the Post Feed Redirect URL for the stub blog to the exact value of the feed URL for the live blog. Your Followers and subscribers, using the old URL, will continue to see newsfeeds for your live blog, while using the old URL.

Following, with the renaming done correctly, is easy to redirect. Your Followers, as mentioned above, can view the blog feed using the old URL, with no problem. With the blog renamed simply using Settings - Publishing, your Followers will continue to be associated with the blog, with no further action by you.

Google Webmaster Tools are a vital part of the migration, and should be handled immediately after you re publish the blog, and then immediately after you setup the stub blog. You'll have several challenges here.

  1. The "robots.txt" file for the blog, as renamed, may contain the old URL.
  2. The new URL for the blog won't exist in Google Webmaster Tools, so you have to add that. When you verify blog ownership, you'll have to remove the GWT verification tags for the blog, that were used under the old URL.
  3. You'll have to setup sitemaps for all posts in the blog, under the new URL, to complement / replace those under the old URL before the blog was re published.

The search engines will be the most frustrating part of any blog rename. Without any possibility of a "301 Moved Permanently" redirect, or anything remotely similar, any SERP hits will land the prospective viewer on a 404 display. Your best strategy is to manage the other categories aggressively, and hope that the search engines re index your blog promptly under the new URL.

Your viewers will have to be redirected using the stub post in the stub blog, published under the old URL. Your viewers looking for the main page of the blog will see the stub post, with no problem. Your viewers clicking on a direct link to a single post, an archive or label search, or possibly a SERP hit, will get a 404 display.

Page not found
Sorry, the page you were looking for in the blog The Real Blogger Status does not exist.

Go to blog homepage




The "Go to blog homepage" link will, hopefully, display the stub post - and they can follow the link to the new URL. That's a start, and it's all thanks to the Blogger custom 404 display.

OK, lets summarise the tasks involved.

  1. Is this blog published to a Google custom domain? If so, read about specific issues related to custom domain URL changes.
  2. Re publish the blog, under the new URL.
  3. Enable the feeds, and verify feed URLs.
  4. Setup Google Webmaster Tools for the blog, under the new URL. Look in the Sitemap list for the blog. Any sitemaps in there right now will likely point to the old URL, so these need to be removed. Then, add sitemaps for all posts.
  5. Setup a stub blog, under the old URL.
  6. Set the Post Feed Redirect URL, to point to the feed for the new URL.
  7. Check Google Webmaster Tools for the blog, under the old URL. Look in the Sitemap list for the blog. You'll probably have to re add all sitemaps for the blog, to enable the search engines to index the blog, starting from the old URL, through the redirected feed.
  8. Are you using a FeedBurner (or another custom feed)? If so, update FeedBurner, then check the Post Feed Redirect URL setting.
  9. Check and update all Google Webmaster Tools settings, between the old and new URLs. Think carefully about each setting, and decide whether it should apply to the blog under the old URL, under the new URL, or both.
  10. Are you using Mail-to-Blogger to publish to the blog? If so, check your Mail-to-Blogger addresses.

And if possible, read about the details involved in the rename process before you rename the existing blog. This last caution especially applies to changing one non BlogSpot URL to another non BlogSpot URL.

Monday, February 1, 2010

Blogger Magic - Custom Domain Redirects

Money is a popular artifact used in magic tricks - everybody loves looking at it, and playing with it.

The disappearing quarter - which starts out in your hand, and is found behind your ear - is intriguing. Equally as intriguing is the magician who can take two 50 cent pieces, and turn them into a dollar bill.

The two into one conversion is a neat trick - and that's part of a properly designed and properly setup custom domain.

  1. The BlogSpot URL is redirected by URL forwarding, to the domain URL. This picks up the traffic from the BlogSpot blog, and transfers it to the domain. And, it picks up the identity of the domain.
  2. The domain is redirected by "A" / "CNAME" referral, to Google (and within Google to the Blogger blog). This picks up the traffic from the domain (including the traffic forwarded from the BlogSpot URL), and transfers it to the Blogger blog.
  3. "CNAME" referral retains the identity of the domain, with the traffic.

"CNAME" Referral merges traffic to the blog, using the domain identity.

What we have here is traffic (BlogSpot + domain) merged together, to the domain. Blog content gets indexed by the search engines under the domain URL - and contributes to page rank, and search engine reputation, for the blog, as published to the custom domain URL.

Identity * Traffic == Search Engine Reputation, for the domain.

Remember that the value of a custom domain is based on the increased reputation - to the blog, when seen under the domain URL.

Frame / URL Forwarding merges traffic to the blog, using the blog identity.

An alternative to "A" / "CNAME" referral, provided and recommended by some registrars, is Frame / URL Forwarding.

  1. When re published to the domain, the BlogSpot URL is redirected by URL forwarding, to the domain URL. This picks up the traffic from the BlogSpot blog, and transfers it to the domain. And, it picks up the identity of the domain.
  2. The domain is redirected by Frame or URL Forwarding to the BlogSpot URL. This picks up the traffic from the domain (including the original traffic, forwarded from the BlogSpot URL), and transfers it to the blog - and back to the BlogSpot URL.
  3. Forwarding picks up the identity of the BlogSpot URL, with the traffic.

No Identity * Traffic == No Search Engine Reputation, for the domain.

All that work - and the identity (and search engine reputation) goes back to the BlogSpot URL.

If you pay extra to just merge traffic to the blog, what's the benefit?

In terms of magic, the latter trick is a dud. Nobody sees your domain. There goes your dollar bill, in a puff of smoke.

There's no benefit to the blog, if it's just seen under the BlogSpot URL.

Don't let your registrar sell you a puff of smoke!

If your registrar tries to tell you to use Frame or URL Forwarding, because they don't provide "CNAME" referral, or because they won't allow 4 x "A" referrals, your best choice is to find another registrar - or possibly, use a (free) third party DNS hosting service.

If you're here because you got technical advice to use URL Forwarding anyway, because it will work just as well as "4 x A" / "CNAME" referral, get better advice.

It's your domain - you want the benefits of publishing your blog to a domain URL? Publish it properly, using "A" / "CNAME" referral.

Wednesday, December 9, 2009

Blogger Magic - The FeedBurner Redirected Feed

One of the neatest bits of magic in the Blogger trickbox is the FeedBurner (external) feed redirection. A redirected FeedBurner feed requires 2 steps.
  1. Setup a FeedBurner feed, sourced from the blog native feed.
  2. In Settings - Site Feed, redirect the blog feed to the FeedBurner feed.

The native feed from this blog, "blogging.nitecruzr.net", is

blogging.nitecruzr.net/feeds/posts/default

That's how my blog started out (after I republished the blog to the custom domain URL). I setup a FeedBurner feed

feeds.feedburner.com/Nitecruzr-Blogging

after this blog had been long in existence.

Normally, when you change a URL, half the work involved in the change is going around to all of your readers and saying

Hey, check out my new blog feed, "feeds.feedburner.com/Nitecruzr-Blogging

Informing your readers is the complicated part of this change.

In this case, I spent no time doing that. Many of my readers don't even know about "feeds.feedburner.com/Nitecruzr-Blogging", they think that I'm still publishing "blogging.nitecruzr.net/feeds/posts/default" (which I am, actually).

All that I had to do was change one setting in my blog. In Settings - Site Feed, I set "Post Feed Redirect URL". Blogger took care of the rest.

A post feed redirect is the simple part of this change.

Let's look at a redirected feed, using an excerpted HTTP trace.


Sending request:

GET /feeds/posts/default HTTP/1.1
Host: blogging.nitecruzr.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.15) Gecko/2009101601 Firefox/3.0.15
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.53.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·302·Moved·Temporarily(CR)(LF)
X-Frame-Options:·ALLOWALL(CR)(LF)
Location:·http://feeds.feedburner.com/Nitecruzr-Blogging(CR)(LF)

...

Sending request:

GET /Nitecruzr-Blogging HTTP/1.1
Host: feeds.feedburner.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.15) Gecko/2009101601 Firefox/3.0.15
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.155.133
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·200·OK(CR)(LF)


A redirected post feed uses another DNS based redirection.

Yes, folks, another DNS redirected URL. If I ever tire of the FeedBurner feed name "Nitecruzr-Blogging", I just setup a new FeedBurner feed, then change the redirect for the blog. And the instant that I change the redirect, people reading my feed get the new feed.

I could even setup a redirected feed in another service. But be aware that not all online services will use a redirected feed.

Use whatever feed redirect you wish - just make sure that the "Post Feed Redirect URL" setting points to a valid feed URL, and you're good to go.

Thursday, April 10, 2008

The Blog Feed Redirect Option Needs To Be Used Properly

When you setup a Blogger blog, and use a properly configured feed, the combinations of comments, labels, and posts feeds can do wonders for making your blog more accessible and maintainable. You have a number of feeds, with URLs based upon the URL of the blog, to work with.

For more possibilities, you can use a custom feed, provided by an aggregation service like FeedBurner or FeedDigest. When you use a custom feed, you can even redirect references, within the blog, to the custom feed, so you don't have to manually reconfigure things like post footer feed links.

You redirect feed references using the dashboard setting in Settings - Other - "Post Feed Redirect URL".

Always use this setting properly - only put a valid feed URL in the box, or you will end up with a broken blog feed. A valid feed could be:

  • A feed from another Blogger blog, as when you move the blog to another URL, and setup a stub blog with a redirected feed.
  • A valid external URL - one provided by FeedBurner, FeedDigest, or a similar service.

Do not point this internally, to the same BlogSpot or domain URL. You cannot use this to simply change the URL of the feed for any one blog - it must be used in conjunction with a second blog, or a custom feed setup.

Here's the redirect setting, for this blog:
http://feeds.feedburner.com/Nitecruzr-Blogging
That's my FeedBurner feed URL. Yours will be similar, excepting the
Nitecruzr-Blogging

If you use the URL of a feed for the same blog, you'll end up with a feed redirect loop. If your readers see anything from the feed, when it's directed to itself, it will be something like

The page isn't redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

If you have no FeedBurner or second blog feed to redirect into, or if you don't know what is needed here, leave this setting blank. If you're using the setting, and you're experiencing a feed related problem, you should first clear the setting.

Also, be aware of the interaction between the Google Sitemap and the blog feed. A Google Sitemap will break, if you redirect your blog feed to a URL outside the blog naming space.

Finally, note that the blog feed is intended to let your readers read your blog, with greater ease. It's not designed to let you randomly distribute the blog content to the Internet, while abusing your Followers and subscribers.

Sunday, March 16, 2008

Your Blog, Moved Permanently vs Moved Temporarily

If you're lucky, and can afford to have 2 homes, you may occasionally plan an extended stay in the second for while. You may email (or snail mail or maybe Tweet) your friends and family
I'm going to be staying at the cottage (mountain lodge, desert camp, ...) for a while. Send all of my mail there for the next couple months, but keep my current mail address on file.
This is different from sending them, and your business acquaintances (and banks, credit card companies, etc) a second notice
I'm moving next month. Please change your address for me.

Your blog, or other web site, can use either of the above address changes too.

Understand the differences between a Permanent and Temporary redirection.

The first, a "302 Redirect", returns a "302 Moved Temporarily" when addressed by your readers browser. The second, a "301 Redirect" returns a "301 Moved Permanently", similarly. The effect, for your reader, is the same - they see the new address when they type the URL of the blog into the browser address window.

The difference between the 301 and 302 Redirects differs by how the search engines see your blog, and this is what's important.

A server based 301 or 302 redirect is most reliable.

A "301 Moved Permanently" causes the search engine to replace all references in its files, to the source URL (the current address), changing them to the object URL (the new address). This is quite legal, the old address is simply replaced by the new address. All search weight is transferred from the old URL to the new.

A "302 Moved Temporarily" will have a different effect.

This causes the search engine to retain the old address, and the new address, simultaneously. This, in turn, causes duplicate content indexing, which search engines see as a typical spammer tactic. They will penalize the search weight of any blog or web site using a "302 Moved Temporarily", for this reason.

You can use a browser based meta refresh to redirect your blog.

It's not hard to setup a meta refresh in the blog template, to redirect your readers from the old URL "myblogoldurl.blogspot.com" (where you publish a stub blog) to "myblognewurl.blogspot.com" (where you publish your current blog).

Find
<head>

Add
<meta content='0;url=http://myblognewurl.blogspot.com' http-equiv='refresh'/>

Giving
<head>
<meta content='0;url=http://myblognewurl.blogspot.com' http-equiv='refresh'/>

Browser based redirects are detected by Blogger as malicious.

Unfortunately, browser based redirects, using a meta refresh, or JavaScript redirect, will be seen by the search engines as a "302 Moved Temporarily".

Blogger may detect this as a browser hijack, as it's splog detection constantly detects splogs that are using this same tactic. Plus, the search engine will continue to index the content after the meta refresh as "myblogoldurl", giving no weight to "myblognewurl".

When you forward the address of your blog, for any reason, be it the BlogSpot address to the domain, or any secondary domains to the primary domain, using a "301 Moved Permanently" redirect is by far a better idea.

Wednesday, March 12, 2008

Custom Domains Use 301 Redirect, From BlogSpot

When you setup a Custom Domain, the setup wizard provides encouraging advice
We won't leave your readers behind!
http://myblog.blogspot.com will redirect to your custom domain.

Blogger accomplishes this bit of trickery, using standard Internet protocol - a 301 Redirect - but it's done in two steps.

Blogger redirects a Blogger blog, using two steps.

  • When you publish your blog, "myblog.blogspot.com", to your custom domain, "mydomain.com", all internal links within the blog are changed, from "myblog.blogspot.com" to "mydomain.com".
  • When the transition period ends 72 hours later, Blogger sets up a standard server based "301 Moved Permanently" for your blog.
  • Note that only the blog internal links are changed - any links which you added, from post to post, are your responsibility. Likewise, all external links are your responsibility.

The search engine spiders, which previously indexed your blog as "myblog.blogspot.com", now index it as "www.mydomain.com".

Everybody who looks at the URL sees the blog published as the domain URL.

Similarly, your readers see "www.mydomain.com". To everybody, even those intending to look at the old BlogSpot URL, you now have "www.mydomain.com" for a blog URL.

The "301 Moved Permanently" referral from BlogSpot is similar to the "301 Moved Permanently" referral used in Custom Domain DNS setups, to equate "mydomain.com" to "www.mydomain.com".

In both cases, when this technique is used properly, the clients - either the people who read the blog, or the search engine spiders that index the blog - see the contents of the blog as being part of the redirect target. Now, they see "www.mydomain.com", instead of "myblog.blogspot.com".

The BlogSpot to domain redirect is installed in the Blogger server, not in the blog.

This "301 Redirect" is server based. If you put a meta tag, or JavaScript, based "301 Redirect" or "302 Redirect" into your blog, you will cause problems for your readers. Both are treated similar to a "302 Moved Temporarily", and your blog loses search engine weight.

In some cases, your readers will see
Too many redirects!
or a similar error, following a gratuitous redirection to block country local domain redirection, installed by you. In other cases, the BlogSpot URL simply does not operate.

The "Too many redirects!" error is more frequently seen, with "HTTPS" accessible blogs published to custom domains - and with the "HTTP" to "HTTPS" redirection. Here, too, a properly setup custom domain is essential.

Some non Google services, which use a URL to identify you, must be updated.

Note that this redirect applies mainly to search engines, following links. It won't apply to feeds, which need the updated URL in their database. It will apply to your readers - but readers who monitor the address window in the browser may become confused, if they see the new, non-BlogSpot URL where they are accustomed to seeing a BlogSpot URL.

You still need to notify your readers, and you still need to update all external fixed URL references to the blog, such as FeedBurner and other custom feeds, Google Webmaster Tools, and the various visitor meters.

Navigate» Become author for this Blog