301 Redirect and custom 404's

Hello

I am in the process of abandoning one domain name in favor of a better
one. I set up my site at the new domain and I would ideally like to
reidrect all traffic that was coming in through the old site to come to
the new site.

I used a snippet of asp code on my default.asp page for a 301 redirect
and it seems to be working okay. Instead of adding this code to every
page of the old site I deleted all other pages and created a new page
moved.asp as a custom 404. I added the same 301 redirect code to the
moved.asp page which brings users to the root of my new domain.

I used a server header tool and the root domain does return 301 moved
permanently but if I run one ot the subpage addresses I get a 302 for
the moved.asp page (it redirects to moved.asp first I guess, and then
again to the new domain).

Can anyone tell me if this is the wrong thing to do? Could I be subject
to a duplication penalty? The site hasn't been up all that long -
should I remove the custom 404 and just let the rest of the pages fall
dead? The original site has only been up for three months so its not
an enormous amount of traffic - building on the new site is what is
most important and I want to avoid getting it sandboxed if at all
possible.

TIA

~R

On Wed, 11 Jan 2006 16:56:28 +0100, <ryann.callaghan (AT) gmail (DOT) com> wrote:

should I remove the custom 404 and just let the rest of the pages fall
dead? The original site has only been up for three months so its not

In this case you may simply remove it from Google index:

http://services.google.com:8882/urlc...ler?cmd=reload

Best,
Borek
--
http://www.chembuddy.com/?left=pH-ca...right=pH-scale
http://www.chembuddy.com/?left=pH-ca...=pH-definition