Mobile app version of vmapp.org
Login or Join
Holmes151

: "Temporarily unreachable" when using fetch as Googlebot from Webmasters Tools The page I'm trying to fetch is public. The server logs show no request. Google reports that any page on my site

@Holmes151

Posted in: #FetchAsGoogle #GoogleAppEngine #GoogleSearchConsole

The page I'm trying to fetch is public. The server logs show no request. Google reports that any page on my site is "Temporarily unreachable". It won't even fetch the verification file, a static HTML file that was successfully used to verify with the webmaster tool application itself.

My site is running on the Google app engine.

What is causing this?

10.05% popularity Vote Up Vote Down


Login to follow query

More posts by @Holmes151

5 Comments

Sorted by latest first Latest Oldest Best

 

@Correia994

I'm not sure if it's 100% the same issue, but recently I tried using the fetch as google page in Firefox, not Chrome, and it suddenly decided that my most recent 'temporarily unavailable' request was actually a 'partial' success. Very strange, but it seems to work a bit more now.

10% popularity Vote Up Vote Down


 

@Nimeshi995

I found the answer (that worked for me) here: productforums.google.com/forum/#!topic/webmasters/IomjijWoCfU
See Tracy Brown 4's reply (found about 90% of the way down the thread):


You dont have a robots.txt file. Google appears not to fetch in WMT if
there is no robots file.


I added an empty robots.txt file, immediately tried again, and it worked.

10% popularity Vote Up Vote Down


 

@Kevin317

Another cause can be because you have recently moved to another hosting server, you have just changed DNS servers

10% popularity Vote Up Vote Down


 

@Reiling115

check htaccess and dns server connectivity. this often occurs in shared hosting. Besides, htaccess has been created before we upload our web file in shared hosting. try to check both of items. If OK in htaccess, then you should contact your host.

10% popularity Vote Up Vote Down


 

@Gloria169

According to Google, it's because:


Fetch as Google can't currently fetch your URL because the server took too long to reply.
Or Fetch as Google cancelled your fetch because too many consecutive requests were made to the server for different URLs.


I've witnessed this happening a few times in the past. More often than not, it's an intermittent problem that goes away after a short period of time.

Important note:


Note the URL is not unreachable for all of Google - It is just
unreachable for the Fetch as Google simulation tool.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme