A couple of days ago, I faced an issue with Google Webmaster's Fetch as Google functionality. The page was going into an infinite refresh loop. I started a thread on Google's forum. The issue disappeared by itself.Unfortunately, this issue is happening again. Google still does not have the latest copy of my main page in its cache. The Fetch as Google page is going into an infinite loop again. Anyone knows why? Any idea/suggestion is welcome... Thanks!
Fetch as Google goes infinite loop (again)
google search console;fetch as google
This is a known problem with Webmaster Tools as you have first hand experience when you noticed it before. You can test your own site using firebug and reading the response you get.Test Your Own PagesWhile Webmaster Tools is good it should be noted its not perfect and more than often out of date as it's not interlinked in real time with their indexer or caching service. You can test your own pages if you have Google doubts, simply install firebug and your be able to see from the header messages what your site is returning.I've just tested your site and can confirm that its work as intended I get 200 with no 301 redirects meaning the infinity loop doesn't exist and something that is clearly wrong with the Google Fetch Bot. You can review the response I got from below.GET yourcurrencyconverters-tostaky.rhcloud.com 200 STATUS OKChances are Google will fix the problem in a few days time so test it then but in the mean time just test it yourself using Firebug.Additional ReadingI've read your post on http://productforums.google.com/forum/#!topic/webmasters/Voqv-_Ts2AE and I can confirm that the index.html also returns a valid responseGET index.html 200 OKWebmaster Tools is often bugged, outdated, or just plain annoyingAs mentioned in the previous question and adding to this one, Google Webmasters, Googles Rankings and Indexing and Even Google cache service are all independent services when one gets updated it can often take many days afterwards to update in Webmaster Tools and in other services. Trailing SlashesOne small possiblity is that your site is causing a redirect on the trailing end slash, its unlikely but make sure you test the fetch with and without the ending slash to see if theres any different. http://yourdomain.com/http://yourdomain.com Things to DoAs mentioned Google takes time and rather concerning yourselve too much maybe and I hope you don't take offence but maybe you should focus more time on getting your site out of This site is still under construction! Come visit us again later! and into a live site, since watching it on Google won't do any good. Simply get on with more construction things and care little about Google. 