3 ms·
If you look at Google's cached page, it looks like they fetched http://qdb.taranen.co.uk/ http://qdb.taranen.co.uk/ at 2009-11-06 07:47:43 and your page came ba
by cperciva 17y ago
If you look at Google's cached page, it looks like they fetched http://qdb.taranen.co.uk/ http://qdb.taranen.co.uk/ at 2009-11-06 07:47:43 and your page came back.
When did you acquire your current IP address? If it was some time around that point, my guess is that they had your IP address before you did, and thir DNS (or google's cache of it) was out of date.
I am not sure what to do or how to resolve this.
I don't think there's anything you can do aside from waiting for Google to re-crawl. For future reference, though, this is a good reason to only serve up your site in response to HTTP queries which come with the right Host: header.
- dawie 17y agoI noticed that too. I have had this IP for about a month now. It's still pretty annoying and I don't really know what I can do about it.
- dpifke 17y agoFor future reference, though, this is a good reason to only serve up your site in response to HTTP queries which come with the right Host: header. Or add a <link rel="canonical"> tag, see: http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html http://googlewebmastercentral.blogspot.com/2009/02/specify-y...
- bkrausz 17y agoOr, even better, have a check to see if they're on the right host, and redirect them if not (that way you get the SEO+ from the other url).