Robert_Charlton - 12:06 am on Jun 21, 2011 (gmt 0)
While the anomalies persist, Google appears at least to be no longer displaying noncanonical forms of a domain in the url line... ie, if you've 301ed the non-www version to the www-version, Google is now displaying the www-version. This is very different from what was showing last night. So perhaps this is a work in progress.
In some cases, Google is still displaying redirected old domains. I'm seeing a bunch of examples of domains redirected many years ago still displaying the old domain, but in the context of their new sites/destination domains. Redirected TLDs are also still displaying.
I am also seeing an interesting inconsistency, though, where there's different behavior for different aliases redirected to the same destination domains. In this case, olddomainA.com and olddomainB.com are both redirected to example.com, and...
- Google shows example.com for olddomainA.com redirect...
- but it shows olddomainB.com for the olddomainB.com redirect.
(This latter is an example from another mod, and I'm not familiar with the hosting or where or how the redirects were done... whether, eg, in the destination domain's .htaccess, or from different registrar or hosting accounts).
With the listings that display different domains...
- mousing over the page titles still shows the displayed (old) url in the task bar...
- but mousing over various types of Sitelink displays or additional results shows the new domain in fully canonicalized form.
This is almost like watching DNS changes propagate. This may be the wrong choice of words for a simile in this case (and maybe one shouldn't make technical similes), or it may be an exactly right one, but I'm not sure of the explanation.
Little by little some things may be returning to what they were. It's hard to know whether Google wants to display the original redirected domains, and I can't imagine why Google would.
I should add that the redirected domains are displayed only when you search for them, but I agree with g1smd that it's bad training to have people click on redirected alias domains. With banks, I should add, it's bad enough that many banks are careless enough to sometimes use different domains for marketing than for banking purposes.
If your webserver displays .htaccess files in a way that leaves them open to be parsed by Google you should have it checked.
ADovervik - thanks for that observation. These are unrelated sites at different hosting companies, with servers set up by different people, and a good many of these are not domains I work with. The simile I used here... almost as if Google were parsing .htaccess files... was probably not a good choice of words to describe server operation, but it was the best I could come up with very late last night. Shared hosting was the common feature which came to mind. It will likely turn out that these sites all do not have publicy available .htaccess files, but it's most definitely worth a look. Again, I can't imagine why Google would want to display this in the index if it were true.
I should add I've just gotten a report of at least one site on a dedicated server having this problem, so that most likely shoots that theory.
Looking at all sorts of behavior I'm seeing, I think this is a glitch, but I'm also thinking there may have been an underlying change in how Google is indexing redirects which may be useful to know about.
PS: Instead of sending examples to me, please examplify them... keyword1 keyword2, or whatever... and add an asterisk after http if you can't use example.com for reasons of description. Eg, http*//www.keyword1keyword2.com will keep these from becoming live links.