google and 302 server codes

how good is google at resolving these?

[mr_dredd2]

A number of sites I manage have other domain names that for various reasons can't be pointed directly to the same ip address. I've noticed that while google is good at resolving 301 server codes (permanently moved) it is not good at resolving 302's (temporarily moved).

It seems that google treats them as different sites - I know this because i do site searches on both domains and they come back with different results.

HAs anyone else noticed this?

[ciml]

If the PageRank is high, then Google can follow 302 redirects.

So if A links to B which redirects to C then C can be credited with the link from A, but not always.

[mbauser2]

It seems that google treats them as different sites - I know this because i do site searches on both domains and they come back with different results.

It's supposed to do that. According to RFC 2616 [w3.org]'s definition of status code 302, "The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests." In other words, Google is supposed to leave the first URL in the index, since it hasn't been told the redirect is permanent.

[ciml]

Good point mbauser. I guess that this is another case where Google will bend the rules in order to index a non-perfect Web.

[mr_dredd2]

thanks.
if thats the case, then i am hoping that changing them to 301's should sort out this duplication.

its amazing how many webmasters just throw on a 302..!

[ProfMoriarty]

Itīs not too amazing. E.g. every redirect via PHP header(location: ...) throws a 302 if the following page doesnīt set a 301 manually.

[jatar_k]

>>301's should sort out this duplication

It should.

The premise would be that with a 302 google would continually come back to the old url on the possibility that the content has returned because you said that it would.

If it finds a 301 it should follow the redirect and on the next spidering return to the new url because you told it the old one is no longer used.