Rumbas
msg:222548 | 6:32 pm on Jan 15, 2004 (gmt 0) |
I'd wait it out for a few months. Hard to tell what will happen with ATW anyway :)
|
pageoneresults
msg:222549 | 6:37 pm on Jan 15, 2004 (gmt 0) |
I'd agree with Rumbas. It's a waiting game. Just to be on the safe side, make sure your 301 Moved Permanently redirects are returning the proper status in the Server Headers. Server Header Checker [searchengineworld.com] The response may look something like this... Server Response: http*//www.example.com/old-page.htm
Status: HTTP/1.1 301 Moved Permanently
Location: http*//www.example.com/new-page.htm
Server: Microsoft-IIS/6.0
Content-Type: text/html
Content-Length: 152
|
yves1
msg:222550 | 9:34 am on Jan 16, 2004 (gmt 0) |
Thank you for your advice. pageoneresults, the status in the header is OK. Unfortunately, I can't wait too long. My old domain will expire in 2 months. Given this short timing, is waiting really the best solution? I'm afraid it won't be enough for ATW to make the change. Do you think there is something else I can do? Thanks.
|
travelbuff
msg:222551 | 4:07 pm on Jan 19, 2004 (gmt 0) |
yves1 - If the domain expires the redirect goes away, so be sure all of your inbound links are changed to the new domain. I have the same situation with ATW, it has been about 4 mos and not only does it show the old domain, but also the new, and with the same content. Sometimes I am pos 1 and 2!.
|
pageoneresults
msg:222552 | 4:27 pm on Jan 19, 2004 (gmt 0) |
| pageoneresults, the status in the header is OK. |
|
Do you mean that the status is 200 OK? If so, that is the incorrect header status for a 301. The 200 OK means that everything is okay and the spider is instructed to index the URI without any other further directives.
|
yves1
msg:222553 | 8:33 am on Jan 20, 2004 (gmt 0) |
Sorry, by OK, I meant 301 ;-)
|
|
