input: [Status] Redirected [Fetch and Render] 1) At the fetching stage, when Google contacted the host server for your URL, the server told Google to visit a different URL. OR 2) At the rendering stage, HTML meta tags and Javascript code might tell the Google to visit other sites. [Notes & Next Steps] 
output: Although the actual Google crawler follows redirects, the Fetch as Google tool will not. You must follow a redirect manually: If the redirect is to the same property, the tool displays a button that allows to quickly follow the redirect by populating the fetch box with the redirect URL. If the URL redirects to another property that you own, you can click "Follow" to autopopulate the URL box, then copy the URL, switch views to the new site, and then paste the URL into the fetch box. You can inspect the HTTP response on the fetch details page to see the redirect details. Locate the HTTP error code to learn more. You can also search through your meta tags and Javascript code if the redirects are happening at the rendering level.