Welcome to WebmasterWorld Guest from

Forum Moderators: phranque

Message Too Old, No Replies

How to fix following crawl errors in google webmaster tools

IP in excluded range and 404-like content

7:14 am on Jun 26, 2010 (gmt 0)

Preferred Member from IN 

joined:Sept 23, 2008
posts: 458
votes: 0

In Http Crawl Errors - IP in excluded range
In Sitemaps Crawl Errors - IP in excluded range and 404-like content
In Soft 404s - 404-like content
8:29 pm on June 27, 2010 (gmt 0)

Senior Member

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:Mar 31, 2002
votes: 0

Request some of these URLs using a server headers checker, such as the Live HTTP Headers add-on for Firefox. If you are getting any 40x response codes, then you'll need to correct that.

You can also try the "View as Googlebot" function in WMT.

I'm not exactly sure what "IP in excluded range" means -- I've never gotten one of those, and so haven't been able to click it to get a "translation" of what it means...

1:55 am on June 28, 2010 (gmt 0)

Senior Member from KZ 

WebmasterWorld Senior Member lammert is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Jan 10, 2005
posts: 2938
votes: 24

The IP in excluded range error is generated for URLs which are assumed to resided on a reserved IP address such as or 192.168.xx.yy. These errors are sometimes generated by WMT when a site has recently changed hosts and there has been a temporary problem in the DNS setup of the site during the transition period.

These errors should go away over time when the URLs are crawled again. To check if the URL can be reached now by Googlebot, you can take one of the URLs listed there and use the Fetch as Googlebot feature to see if the page can be loaded correctly. If WMT is able to download that URL, there is nothing wrong with that URL, but Google still needs to reload it from the new location to update its internal data. If Google can't fetch the URL, you need to check your DNS settings for inconsistencies.