g1smd - 7:30 am on Jun 20, 2011 (gmt 0)
So, Google fixed the "302 hijack" problem a few years ago (this was a huge topic for many months), only to now introduce a "301 hijack" method now?
If there is no domain ownership validation and server/IP hosting validation within the loop, there will be utter chaos.
What could be the possible benefit of this? I don't particularly want to see domains I bought in order to keep typosquatters off, suddenly ranking - especially if the canonical domain is nowhere to be seen in the SERPs.
Imagine I own hexagonal-purple-widgets.com but Google decides to list an alternative that I bought and redirected to the main site. So, Google lists hecksogonall-purpel-wiggets.com in the SERPs instead of the real domain. Users shouldn't be clicking that. It looks like it should be a malware infested scraper site. It shouldn't even be listed, but if it is a popular typo I might want to own it and 301 redirect it to the real site.
Now consider I want to visit the bank website at bank-of-podunk.com and log in.
If I am now being taught to trust that hecksogonall-purpel-wiggets.com in the SERPs will get me to the right place, why should I not click on the entry for bonk-of-podnuk.cn and give it my login details? Surely, that too will get me to my bank website, no?
It will be interesting though, to see what crazy domain names various corporations and institutions have been buying up over the years.
It will also be very interesting to see if buying acme-corp-we-suck.com and redirecting it to the corporate website can result in a situation where the company website appears in the SERPs but is listed only with the ghosted domain name and not the real one.
We live in interesting times.