Welcome to the Q&A Forum

I think what you're seeing here is intentional behaviour, Stephen. It's Volusion's hack for working around the fact their system doesn't handle 404's "correctly". Bottom line, when you see these, you still need to fix the issue with whatever URL was being sent to the 404 page, but don't worry that the 404 page itself seems to be "not found" according to its status code. Here's an explanation for "why" this is happening, if you're interested: Normally, when a user enters a URL that doesn't exist, the server sends back a 404 error header. In addition, the server's settings know that when sending back a 404 status because there's no such page, they should also show the server error page directly. For a number of reasons, Volusion can't do this, so instead, they've instituted a catch-all redirect so visitors to non-existent pages get a 301-redirect to a regular website page that has been faked to look like a 404 page. Because that 404-looking page has been found and shown, it would normally have a 200 status, which means page found OK. A little unorthodox, but OK so far as far as the user is concerned. BUT! When a user hits a "page not found", the search engines want to get an actual 404 status error code back so they know not to index that non-existent URL. See the problem? If the search engine gets a 200 response, it will assume that is the real page the visitor was trying to reach and will index the non-existent URL with the 404-ish looking content. Bad. So even though you - the user - can see the error page (200), Volusion has to give it a fake 404 status to give the search engines the correct information. For a demonstration, go to this non-existent page http://www.cochranemusic.ca/oops You can see in your browser's URL bar that the page address is still http://www.cochranemusic.ca/oops even though the page itself shows the server error page content. Now go to http://www.ecowindchimes.com/oops and notice that the URL in the address bar actually changes, because you've been forwarded to a page on your site called 404.asp. That's a real page on your website you're seeing that's been made to "look" like a server error page. Even though you've been redirected to a real (200) page, the server has to pretend it's a 404 status to mimic the correct behaviour. Whew - that was confusing to try to explain, so let me know if it's still not clear. Paul P.S. To server admins: I know I've oversimplified the difference between a server's own 404 error page and an actual website page made to look like a 404. I do know the difference, but for the sake of keeping this explanation as straightforward as possible, I've glossed over it.

Answered in order, Stephen: 1. Normally, the fact that ecowindchimes.com/ is getting redirected is a good thing. But in this case, there's a problem with how it's been done. If you want to see where it's redirecting to, just enter that exact address in your browser's address bar and watch what happens to the address. It will change to www.ecowindchimes.com/default.asp. Done correctly, it should redirect to www.ecowindchimes.com (no default.asp extension) This is called canonicalisation and it's designed to make sure your site's pages only get indexed under 1 URL. As far as the search engines are concerned, ecowindchimes.com/ and www.ecowindchimes.com/ are separate sites, even though the pages themselves are the same. By redirecting one to the other, you remove this problem. The problem here is that www.ecowindchimes.com/default.asp is yet another way to refer to what is simply the home page of your site. This means that now, instead of www.ecowindchimes.com/ and www.ecowindchimes.com/ being duplicates of each other you have www.ecowindchimes.com and www.ecowindchimes.com**/default.asp** being dupes of each other. This needs to be corrected in your .htaccess file using 301 redirects. You need to make ecowindchimes.com/ use a proper canonical redirect to www.ecowindchimes.com. This will catch ALL version of your pages that start without the www and redirect them to the correct URL with the www. (You'll need to delete the existing redirect as it's incorrect) Then you need to 301-redirect www.ecowindchimes.com/default.asp directly to www.ecowindchimes.com/. 2. I've answered your question # 2 as fully as I can on your followup question. in short, your Volusion system is faking that 404 status as a hack to deal with the fact they don't handle 404 errors in the normal way. The page exists fine and that particular error can be ignored. 3. For your last question, this demonstrates why the hacked method for 404s being used is a problem. URLs that should be 404s will show up looking like 301 redirects instead, because of the hack in use. To test this URL, again just put it in your address bar and watch where it gets redirected to. In this case, it's going to your 404 page (See answer to your followup question as linked above for explanation why this happening) So, yes you need to try to fix these kinds of errors. It's saying that somewhere, there is a page linking to ecowindchimes.com/index.html?lang=en-us&target=d2.html. That is a URL from your old site before you migrated to the Volusion system. It likely means that there are pages on another web sites still linking to your old page addresses.  It's also possible these are outdated links from within your own pages. By entering that URL in the Wayback Machine I can see that it was for a page for Gracenote windchimes, so you'll want to redirect it to your Gracenotes category page. If you want to figure out what pages those broken links are coming from, you can use Webmaster Tools 404 error report and SEOmoz's 404 error report as starting points. NOTE! You'll need to actually download the SEOmoz report as a CSV in order to see the Referrer column at the right side of the report. Hope all that helps, more than confuses? If anything's not clear, be sure to holler. Paul

Are you using a CNAME of your main domain for that server? Like sounds.example.com? You should, if you aren't. I don't think pagerank can flow to a sound file. But I am not entirely sure, tho.