404 custom error page

duplicate content problem?

[fjpapaleo]

I have a site I've just re-done from asp to php. The old site has thousands of dynamic pages (about 70,000 to be exact) that are indexed. I originally intended on just doing a 404 custom error page with "this page has moved, please visit....." or even re-directing everything to my home page. Now I'm having second thoughts. Isn't this inviting a duplicate content penalty? If I have a page such as 404.html with thousands of pages going to it, won't those pages stay in the index and be viewed as duplicate content? I want those pages out of the index. I lose some traffic but isn't it better in the long run to just let those pages die rather than take a chance on having a massive penalty? Any thoughts on this?

[jdMorgan]

410-Gone [w3.org] is the proper response for HTTP/1.1 and extended HTTP/1.0 requests for intentionally-removed resources. If your site is not hosted on a name-based virtual server, then pure HTTP/1.0 requests should be answered with a 404 only. (Note that it's impossible to get a pure HTTP/1.0 request on a name-based server, because HTTP/1.0 clients don't send the hostname header that name-based servers rely on.)

If you follow the protocol, then all other worries go away.

Then there is the even more preferable approach of redirecting each old page to its new replacement, to a similar page, or to a 'related-pages guide' (if applicable). If you have no 'related-pages guide'-type pages, then a link on the custom 410 error page to your home page and site map would be appropriate.

Jim

[fjpapaleo]

Thanks once again JD. I have to go read that about ten more times now :)