Forum Moderators: open
[w3.org ]
How is Google likely to take that?
The type of redirects that increase your risk of getting into trouble are javascript and meta redirects. Since Google doesn't normally parse JS, it will continue to inedex the old page while humans are redirected somewhere else.
With an HTTP redirect, Google is aware of the redirection.
However I have been waiting for nearly 2 months for google to follow a 301 redirect from http*//site.com to http*//www.site.com and it still continues to ask for the old pages.
That is, waiting for the bot to follow it, Imagine the wait to see this in the index.
Just doing my usual Saturday cruise throught the forums ... and what if a META redirect is the only instrument available to you? If OT, apologies, but I'm curious.
I'm on an IIS server and don't have root admin priviledges so no access to 303s etc.
When our customers upgrade from www.mydomain.com.au/custom/index.html to www.theirdomain.com.au, I use a META redirect to point humans to the new site (robots noindex too of course!), but I do have some pages which I'd love to have 303 type control over.
Any suggestions short of changing ISPs or learning asp? ; -)
Cheers and Hooroo
JP
A 303 is a dangerous weapon. :)
This thread [webmasterworld.com] has a message showing you how to do a 301 in asp. Try it.
Ash in VIC 3030