Welcome to the Q&A Forum

Thanks. That was helpful. So I can use Google's Feedburner and that's sufficient to get maximum exposure? Or do I also have to use others like Bloglines? As previously mentioned, I was using "RSS Builder" some time back. Any recommendations for managing the actual feed given it's being used for a website? Can I start a new feed based on the newer pages added over the last so many months?

No its not. the rank for the old domain is not transfered to the new domain using frames. calling and old page may cause it to be loaded in a frame located on the new domain, but a 301 will do this and transfer the link juice also. So the 301 wins hands down every time.

I contacted the help desk as instructed an was told: "I took a look at the campaign and it looks like our crawler can't parse the 301 redirect you have in place on the main page. The reason for this is the redirect in place, adds two https when rogerbot tries to crawl through it. Roger can’t parse the redirect as is, but it can identify it (as it did in your notice’s report on the crawl diagnostics page). This isn't a problem for browsers since they are made to ignore redirects of this nature. Crawlers on the other hand have a strict code to follow and can't follow redirects like that. When I load up your site [mywebsite.com] right now, it redirects to www.[mywebsite].com. Try creating a new campaign under the domain you are redirecting to, this should clear any issues up." And so I did that and it looks like that worked after the new crawl, however I then set up another campaign for another website I manage being sure to use the "www" in front of the domain and got the same problem again -- the home page appears twice as duplicate content. So I'm back to asking my primary question again: What is the definitive redirect code to use to convert a non "www" request to a "www" request? The same redirect code mentioned in my first post is being used on all of my sites.