shaunm - 4:49 am on Jun 17, 2013 (gmt 0)
Thank you for replying on my post :-)
This part, by itself, can be ignored. It's a long-standing known issue. You can test it for yourself using Fetch As Googlebot.
I see this message now and then with various sites, and Google reports that there is something wrong with DNS Server IP set up. Since you must have had so much of experience in this, did you try to change something in your DNS set up which solved the problem? Or you just ignored it only testing it with 'fetch as G?
Thank you! Could you both please help me with my following question?
@lucy24 & phranque
You have to put in both versions explicitly, even though g assumes it is the same domain
it's definitely worth verifying both www and non-www hostnames to detect any issues with that
I have put a server level redirect from non www version to the www version. So, how can I actually verify the site without the www? Sorry if it sounds stupid, because when I am going to type in the verification URL such as http://example.com/google0514411.html it will get redirected to the www version, won't the verification fails by that?
And again @lucy24
Yes, you yourself have to maintain Duplicate Content in wmt ;)
Why should I be needing to do that? Will that work when I have a canonical tag to the www version on non-www version? Because each page in www version acts as its own canonical.
Some areas, notably Links To Your Site, carry separate information for the two forms of the name.
Isn't the site preference setting for this? Where you select your preferred domain with or without www and save changes? Also there is a server level redirect on the site, any backlinks from external sources added without www, will be redirect to the link with www. Won't G reports all this backlinks under http://www.example.com?
Thank you for all help!