IIS 301 Redirects Concerns

Is it or is it not good?

[adfree]

I IIS-redirect all incoming traffic from domain.com to www.domain.com.

Although I do not have any hard indication of any disadvantage I just want to make sure I am not missing anything here.

Is there anything problematic with this approach?

[benevolent001]

well i dont know too but i too added
redirect in apache few days back so that google may just index mydomain and www.mydomain as same website as earlier theywere having PR 3 and 4 respectively
i though it might help

looking for more views

[jdMorgan]

For the past eight years, every site I've built has had a 301 redirect from example.com to www.example.com from the very first second the site went live.

I've never had a bit of trouble, and 99.9% of all my incoming links point to the "correct" domain, because anybody who links to the site will see the redirected URL if they don't type the "www.". In other words, it is difficult to link to the "wrong" version of the domain.

As a further improvement, make sure that you always refer to your home page as either www.example.com/ or www.example.co[]m/index.html[/b], but never both. It's not important what you name domains or pages, just that you are consistent. This prevents all kinds of problems. It keeps the search engine's job simple, because they do not have to invoke special algorithms to analyze your site to determine if example.com and www.example.com are the same, and to determine if your home pages is "/" or index.html; Since you have "told" them with a 301 that only one domain and one home page URL exists, you simplify their job immensely.

When dealing with search engines, naming consistency is important, and can help you avoid technical problems and "duplicate-content filters." So neatness counts.

Jim