Google isn't seeing the content but it is still indexing the webpage

[jacobfy]

When I fetch my website page using GWT this is what I receive.

HTTP/1.1 301 Moved Permanently
X-Pantheon-Styx-Hostname: styx1560bba9.chios.panth.io
server: nginx
content-type: text/html
location: https://www.inscopix.com/
x-pantheon-endpoint: 4ac0249e-9a7a-4fd6-81fc-a7170812c4d6
Cache-Control: public, max-age=86400
Content-Length: 0
Accept-Ranges: bytes
Date: Fri, 14 Mar 2014 16:29:38 GMT
X-Varnish: 2640682369 2640432361
Age: 326
Via: 1.1 varnish
Connection: keep-alive

What I used to get is this:

HTTP/1.1 200 OK
Date: Thu, 11 Apr 2013 16:00:24 GMT
Server: Apache/2.2.23 (Amazon)
X-Powered-By: PHP/5.3.18
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Thu, 11 Apr 2013 16:00:24 +0000
Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
ETag: "1365696024"
Content-Language: en
Link: ; rel="canonical",; rel="shortlink"
X-Generator: Drupal 7 (http://drupal.org)
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8

xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/terms/"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:og="http://ogp.me/ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:sioc="http://rdfs.org/sioc/ns#"
xmlns:sioct="http://rdfs.org/sioc/types#"
xmlns:skos="http://www.w3.org/2004/02/skos/core#"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#">

<title>Inscopix | In vivo rodent brain imaging</title>

[jacobfy]

Well I didn't see all of that but I did recognize the site wide redirect and GTW wasn't updated to the new https website so I was trying to pull data from the old one and obviously I wasn't getting anything.

Thanks for looking into this and laying it out for me. I appreciate it.

[CleverPhD]

I just looked.  Your entire website is 301 redirecting from the http version to the https version.  You have a site wide 301 in place.  If you are submitting the http URL to GWT fetch as googlebot, then you will see the 301 response and that is it.

It looks like you also changed web servers from Apache to Nginx.  Nginx IMHO is a better setup than Apache so that is a good thing.

This just all gets back to that whoever develops/manages your website updated your webserver and also converted you over to https site wide and put 301s in place to move users from the old URLs to new URLs.  So, the response from fetch as google is expected.

[jacobfy]

Doh! I just figured it out. But thanks for the help, it was just a stupid over-site on my part.

[CleverPhD]

Just to verify, is that the URL you are submitting to GWT?  Has that changed?

[jacobfy]

Just to clarify (because I'm a newbie) the _location: https://www.inscopix.com/ _in the first fetch example is the website the 301 is directing to correct?

[CleverPhD]

The page is not invisible, it is responding to the 301 redirect you have in place.

If this is Page/URL A and you used to get the response with the content.  Then if you put a 301 in place, there is no "content" on Page/URL A, there is just the redirect.  The response from GWT is good in that it can see the 301 redirect.

If you setup a 301 redirect from page A to page B.  Enter the URL for page B to see the content of the page.  The Googlebot, when crawling a website and indexing page will follow the redirect.  I am not sure that the fetch as Googlebot does this.

#Update#

According to this page the fetch as Googlebot tool does not follow 301 redirects

http://www.webnots.com/what-is-fetch-as-google.html

Cheers!