Googlebot can't access http://www.gospelhotspot.net

Avatar
  • Answered
Over the last 24 hours, Googlebot encountered 87 errors while attempting to access your robots.txt. To ensure that we didn't crawl any pages listed in that file, we postponed our crawl. Your site's overall robots.txt error rate is 14.1%.
You can see more details about these errors in Webmaster Tools.
Recommended action
If the site error rate is 100%:
Using a web browser, attempt to access http://www.gospelhotspot.net/robots.txt. If you are able to access it from your browser, then your site may be configured to deny access to googlebot. Check the configuration of your firewall and site to ensure that you are not denying access to googlebot.
If your robots.txt is a static page, verify that your web service has proper permissions to access the file.
If your robots.txt is dynamically generated, verify that the scripts that generate the robots.txt are properly configured and have permission to run. Check the logs for your website to see if your scripts are failing, and if so attempt to diagnose the cause of the failure.
If the site error rate is less than 100%:
Using Webmaster Tools, find a day with a high error rate and examine the logs for your web server for that day. Look for errors accessing robots.txt in the logs for that day and fix the causes of those errors.
The most likely explanation is that your site is overloaded. Contact your hosting provider and discuss reconfiguring your web server or adding more resources to your website.
If your site redirects to another hostname, another possible explanation is that a URL on your site is redirecting to a hostname whose serving of its robots.txt file is exhibiting one or more of these issues.
Avatar
Scott
Hello,

Thank you for your question on the Googlebot not accessing your site. I checked your robots file and it is simply denying all bots access to your wp-admin. This may be what is causing your 14% error rate, but it is not written incorrectly if that is your intent. Have you done as Google suggested to check the specific times the errors occurred?

Kindest Regards,
Scott M