Original Poster
Star Sports

Urgent: Fetch as Google - Temporarily Unreachable Issue

I've read the FAQs and searched the help center. 



For the past 6+ weeks, we have been seeing most of our URLs returning a ‘Temporarily Unreachable’ error when fetched in Google Webmaster Tools using the ‘Fetch as Google’ simulation tool. We have been unable to pin point what exactly could be the issue behind this considering we had a 100% success rate with this in the past.


Some important changes that have happened on the website since the beginning of this issue -

·         Website underwent a re-design

·         The DNS setting were not changed. However, the site uses Akamai CDN as the backbone architecture

·         The URL structure of all the major navigation pages were changed

·         Not all old URLs re-directed to corresponding new ones


Please note that we have not implemented any filter on the Akamai server. Also, there is no threshold value that we have placed for the number of request coming to the server.


Thanks for all the help.

Community content may not be verified or up-to-date. Learn more.
Recommended Answer
Was this answer helpful?
How can we improve it?
All Replies (3)
Hi Star Sports

We're seeing an extremely high response-time for requests made to your site (at times, over 2 seconds to fetch a single URL). This has resulted in us severely limiting the number of URLs we'll crawl from your site, and you're seeing that in Fetch as Google as well. My recommendation would be to make sure that your server is fast & responsive across the board. As our systems see a reduced response-time, they'll automatically ramp crawling back up (which gives you more room to use Fetch as Google too). 

Hope it helps!
Original Poster
Star Sports
Hi John,

Thanks for the response.

We are currently working hard to resolve the server level issue at our end. Hopefully, we should be able to tackle this asap!

Really appreciate the help here.

Original Poster
Star Sports
Hi John,

We have made a few changes to our DNS entry as we believed that was causing the issue of high response time to fetch a URL. By when can we expect to see a change in crawling efficiency (also Fetch as Google), if at all this has worked?

Will look forward to your response.

Thanks for the help!
This question is locked and replying has been disabled. Still have questions? Ask the Help Community.


Some community members might have badges that indicate their identity or level of participation in a community.

Expert - Google Employee — Googler guides and community managers
Expert - Community Specialist — Google partners who share their expertise
Expert - Gold — Trusted members who are knowledgeable and active contributors
Expert - Platinum — Seasoned members who contribute beyond providing help through mentoring, creating content, and more
Expert - Alumni — Past members who are no longer active, but were previously recognized for their helpfulness
Expert - Silver — New members who are developing their product knowledge
Community content may not be verified or up-to-date. Learn more.


Member levels indicate a user's level of participation in a forum. The greater the participation, the higher the level. Everyone starts at level 1 and can rise to level 10. These activities can increase your level in a forum:

  • Post an answer.
  • Having your answer selected as the best answer.
  • Having your post rated as helpful.
  • Vote up a post.
  • Correctly mark a topic or post as abuse.

Having a post marked and removed as abuse will slow a user's advance in levels.

View profile in forum?

To view this member's profile, you need to leave the current Help page.

Report abuse in forum?

This comment originated in the Google Product Forum. To report abuse, you need to leave the current Help page.

Reply in forum?

This comment originated in the Google Product Forum. To reply, you need to leave the current Help page.