11

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?

Stephen Ostermiller
  • 99,822
  • 18
  • 143
  • 364
NimChimpsky
  • 566
  • 1
  • 5
  • 13

7 Answers7

7

According to Google, it's because:

  1. Fetch as Google can't currently fetch your URL because the server took too long to reply.
  2. 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.

user399666
  • 2,319
  • 12
  • 13
2

Old thread but I had this issue, it was due to making changes on cloudflare supported TLS version. Google does not support tls 1.3 yet - make sure your servers allows tls 1.2

Aidan
  • 21
  • 1
1

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.

don magug
  • 123
  • 8
1

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

user2869931
  • 11
  • 1
1

I found the answer (that worked for me) here: https://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.

Drewdavid
  • 417
  • 1
  • 5
  • 12
0

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.

ABinJpn
  • 1
0

I've faced same problem and when i deactivate wordfence then fetch and render it shows me successful status

anondi
  • 1