SeaGreenMarketing
09-30-2005, 08:15 AM
I recently added a Blogger.com blog to a client's site. When I crawled the site the blog generated html pages showed broken links (401 errors). These links were all to blogger.com, and from what I can tell, used to pull in certain settings from the template stored on blogger.com servers. The following questions crossed my mind...
1) 401 errors are essentially a 'unauthorized' error. Are 401's looked upon negatively by the search engines like 404's?
2) Am I sabotaging my efforts by adding pages to the site that contain outbound links to blogger.com in the source code?
3) I briefly looked through the source code of the html files for opportunities to utilize a rel="nofollow". If these outbounds to blogger.com which are necessary for the blog to run have a negative impact, has anyone discovered a work around such as manually adding nofollows?
Thanks for your insight,
Greg
Here is MSN's Submit IT's defintion of 401...
401 Unauthorized The URL requires authorization to view page. The spider cannot access sites that require user-IDs/passwords or sites that require cookies. You may be unable to detect this problem because you are accessing the URL from a client that already has authentication (such as the server itself). Try accessing the file from another client, such as a friend's browser. To enable crawling, modify the access permissions of the file to make it viewable by everyone.
1) 401 errors are essentially a 'unauthorized' error. Are 401's looked upon negatively by the search engines like 404's?
2) Am I sabotaging my efforts by adding pages to the site that contain outbound links to blogger.com in the source code?
3) I briefly looked through the source code of the html files for opportunities to utilize a rel="nofollow". If these outbounds to blogger.com which are necessary for the blog to run have a negative impact, has anyone discovered a work around such as manually adding nofollows?
Thanks for your insight,
Greg
Here is MSN's Submit IT's defintion of 401...
401 Unauthorized The URL requires authorization to view page. The spider cannot access sites that require user-IDs/passwords or sites that require cookies. You may be unable to detect this problem because you are accessing the URL from a client that already has authentication (such as the server itself). Try accessing the file from another client, such as a friend's browser. To enable crawling, modify the access permissions of the file to make it viewable by everyone.