Google Fetch and Render - Partial result (resources temporarily unavailable)

[dan_55]

Over the past few weeks, my website pages have been showing as partial in the Google Search Console. There are many resources/ files (js, css, images) that are 'temporarily unreachable'. The website files haven't had any structural changes for about 2 years (it historically has always shows as 'completed' and rendered absolutely fine in the search console).

I have checked and the robots.txt is fine as is the sitemap. My host hasn't been very helpful, but has confirmed there are no server issues. My website rankings have now dropped which I think is due to these resources issues and I need to clear this issue up asap - can any one here offer any assistance? It would be hugely appreciated.

Thanks,

Dan

[dan_55]

Can anyone suggest any answers or has anyone had similar issues? I continue to monitor the site via fetch and render and the issues remain the same - lots of images, css and js files 'Temporarily Unreachable' (yet they do exist and the link can be clicked on). The website functions fine otherwise.

As I say, I have changed website hosts and it is still the same. This is really affecting my rankings and if anyone has any clues I would be most grateful.

Many thanks,

Dan

[dan_55]

Hi Martijn,

Thank you for your response!

The results in terms of the fetch and render for a page of the website looks different everytime. Sometimes it is images that are "Temporarily Unavailable' , sometimes it is css/ js files and sometimes both. However, there is never a 'Completed' result and always some form of 'Partial result. All the files/ images are reachable when you click on them, however. Nothing is blocked in terms of robots.

From time to time the entire page itself says 'Temporarily Unreachable', although it comes back to 'partial' after waiting a few hours.

I have contacted my web hosts who haven't offered much help. I actually changed web hosts and paid for a more expensive, faster server (as I assumed the server was taking too long for Google)!

However, the results are the same, so really struggling to understand why this is happening. As before, the robots.txt file is fine without any blockingCould you explain what you mean in terms of crawling with the GoogleBot User Agent?

Having had a quick scan around different forums, it seems there are quite a few websites having a similar problem, but there doesn't seem to be a solution so far.

Thanks again for your time.

[Martijn_Scheijbeler]

Hi Dan,

Are there any more insights into what the screenshot actually looks like when the resources aren't being loaded? I would, in addition, try to crawl the site/page with the GoogleBot User Agent and see for yourself what happens. In some cases it could be that your CDN or server is blocking requests that are often done, obviously, this shouldn't happen with Google but it wouldn't be the first time that I see GoogleBot being blocked by a server.

Martijn.