Msg#: 4646897 posted 3:06 am on Feb 20, 2014 (gmt 0)
There has been a number of threads in the last few months where members were complaining that Google is not following 301 redirect and that the page that responds with 301 redirect is in SERPs instead of the redirect target page:
Q: And then shouldn't be that the target is part of the Google's index and not the first one? Because some pages are not basically indexed although they are the target of 301 redirect.
John Mueller answered:
That depends a bit on which how we actually index that, so what would happen here is we would crawl and index all of these pages and then we might see that one of these URLs is actually a nicer looking URL or we have more signals pointing to that URL, maybe canonical, maybe a lot of links pointing to that URL and we will actually show that other URL, the one that is still redirecting instead of the final destination URL in Search Results.
So oftentimes we'll see that, especially from URLs that redirect from the root of the domain to the lower level page and we try to show a more reasonable URL in Search Results even if we know that it actually redirects somewhere else in the end.
So it is not that there is anything technically wrong with that kind of setup but you might see that we just show one of higher level pages instead of the lower level URLs just because it looks nicer in the Search Results.
Although the example here is a case where the home page redirects to a lower level URL, from our threads we can also see that Google went for a shorter versioin of URL when the redirect was done from one internal page to another.
So if you are creating a new URL structure and need to redirect:
- make sure the new URLs are better (and perhaps shorter/less folders) than the old ones - make sure your canonical link element is implemented correctly - try to change as many external links as possible to point to a new URL
Otherwise you risk Google showing old URLs in SERPs.
Msg#: 4646897 posted 5:14 am on Feb 23, 2014 (gmt 0)
The TL;DR of John Mueller's response seems to be: Sometimes we decide to just throw protocol out the window these days.
If they're really doing this, it would be cool if they only did it when the redirect was within a domain rather than cross-domain as is being discussed here: [webmasterworld.com...] because even if the visitor ends up on the right site, when the "wrong" domain shows in the SERPs it still gains name-recognition by those who look at where they're going, which seems like a "not very cool" way for Google to do things.
Msg#: 4646897 posted 10:31 am on Feb 23, 2014 (gmt 0)
Some people have to change domains for legal issues and part of the legal settlement is that a 301 is put on a site to stop the old domain name from showing in the serps. This opens another legal can of worms. G needs to understand they don't know why a 301 was put in place and should respect the 301!