Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Fetch as Google - "Temporarily Unavailable" message

         

Broadway

7:35 pm on Aug 16, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



I regularly use GSC and the fetch as Google option.
Starting last night, fetches for pages began returning the status code "Temporarily Unavailable."
And when selecting the "fetch and render" option I get a "partial" status code.
When I check for details about the partial fetch, for the most part the resources that can't be reached are css files and images served by my server.
But clearly when I view my pages, they are formatted properly (hence the css file has been read) and I see the images that Google can't.
I contacted my hosting provider. They see nothing at their end that should be a problem (they aren't blocking Google).
My problem started occurring when working with and fetching a series of pages. It cropped up within a two minute time span last night (and still exists today). All I was doing was revising content. I implemented zero setup changes (CMS, htaccess, robots.txt, etc...) during the two minute window when the problem appeared.
Do I pursue this with Google (and how)?
Or can I expect this issue to resolve on its own?

aristotle

9:17 pm on Aug 16, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Have you checked for "Blocked Resources" in the Google Index section of GSC?

not2easy

10:17 pm on Aug 16, 2016 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



That is a good suggestion aristotle. It also could have been one of the "hiccups" GSC is known to suffer occasionally. If it persists it needs a deeper look, but I wouldn't assume that the problem was due to anything on your site when you see a response like status code "Temporarily Unavailable." Check after 24 hours to see if the problem persists.

Broadway

1:21 am on Aug 17, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Thank you both.
The problem lasted almost 24 hours but as suggested it seems to have resolved itself. I'm back in business with fetching.