Hello, I used the service here ( http://whois.domaintools.com/ceint.com ) to check if ceint.com was blacklisted by google. It say's no. But the issue is that the whois at domain tools shows this: Website Title: 400 Bad Behavior What could it be that is causing this? My guess now is that this is what google also get when crawling the site. How can I correct this as I see no errors when browsing the website and MSN has no problems indexing the site.
code validation is unpopular but somet6imes helps to be more successful try to eliminate all errors in your meta tags see http://validator.w3.org/check?verbose=1&uri=http://www.ceint.com/ 400 is a server response correct all errors and load the page yourself and check in real time your log entries to see what server respnse you create the site http://whois.domaintools.com/ may collect its data by a bot who may be more sentive to errors of any kind in code than a normal browser
Thank you for your prompt response. I have now cleaned up the code and the site is now Valid HTML 4.01 Transitional. Any other suggestions?
now you still get the 400 server response quiet unusual look at your htaccess or robots.txt to make sure you have NO bot and NO referrer excluded from your site then check live yourself the access code in your site using either a realtime access_log monitor tool to see what server access you reate when loading the page in the worst of all cases of course it could be a wrong configuration of server response ( apache config ) the site surfs properly even using links text browser, hence either whois.domaintools.com is using a special bot that creates such response OR you have somewhere excluded one of their requests to create YOUR apache to create a 400 response. the key is YOUR site/apache configuration look at your access_log files ( raw logs ) and look how often and when your apache server creates a 400 responsa, then figure out why and solve the problem or contact your hosting if you know all details about why see also http://www.debianhelp.co.uk/errorcodes.htm about server responses finally - less likely but possible - a 400 can come from a wrong code request from the referrer website out of about nearly a 1 million qweekly requests i got a dozen or so 400 in my last access_log today i had a look at them to see what could cause your problem in my 400 responses the requesting site always ask for a URL from a HIGHER fodler than my public folders - hence a link problem from rquesting site - half of these 400 in my case come out of yahoo-mailboxes that have pictures HOT-linked to my site in emails all remaining 400 errors come from one referrer IP using the same OS and browser which may possibly cause the wrong request