In May, the Fetch as Google iswas updated. There are no details on the update other than adding the render feature. Prior to that, it was an older version of the googlebot and it is not fully up to datemoved outside of the queuing process. The differences were slight. It is good when you want a page indexed right away but not something I recommend unless it is important to update Google's index for expediency.
IfHistorically, if you fetch a page using Fetch as Google, you willwould see that Googlebot will come along again in just a few days. This is because the Fetch as Google is intended to be just temporary and doesdid not tie into the index the same way that the normal Googlebot doesdid. It may do so now. I suspect the popularity of the tool had something to do with the update. There are advantages to this option such as getting your page into the index fast. Previously, but draw backs in that the page will not fully perform as it normally would. For thisThe reason, Google extends was that a bitcertain amount of trust was given and give pages fetched with Fetch as Google a bit ofthe page could perform higher than normal- a pseudo boost in limited and obvious search terms where as the page would actually perform betterdifferently overall if naturally discovered.
Some try and game Google with Fetch as Google. It will backfire and your pages will only perform in limited ways. This isI do not recommendedsuggest over using the tool for this reason. However, thereThere are, however, times when getting a page in the index fast is a must. Then this option is perfect. Use it sparingly. But use it when it is important. Otherwise, I would just wait till the standard Googlebot comes along.