has anyone gotten googlebot to correctly fetch gra...
# prisma-whats-new
m
has anyone gotten googlebot to correctly fetch graph.cool content? even with a fully prerendered solution like prerender.cloud it executes the queries and returns the error

https://puu.sh/waR7e/d9fb0a1c85.png▾

h
@mel do you serverside render or?
m
yes a version of serverside rendering using http://prerender.cloud/ so it returns the rendered html with the javascript so the javascript executes again on the client
It works great with twitterbot, slackbot, etc but google is doing fancy things with its crawler…
h
because twitter and slack dont crawl like google they only get tags
can you try proper server side rendering?
because google block request so they crawl faster
google can understand some of JS but still lacks in some ways 🙂
m
hmm it’s interesting because it seems to be able to fetch all the other endpoints just fine, just not the graph.cool endpoint…
s
@mel - is this screenshot from google webmaster tools?
m
yes it is
from what im reading, it seems to be related to the robots.txt file at the api endpoint
@sorenbs any idea what might be happening? is it something that can be fixed graph.cool side?
@nilan maybe you can provide an update? 😬
n
I am not quite sure what is happening here. I quickly checked prerender.cloud with my own app, and the prerendering seems to work fine: https://service.prerender.cloud/http://learn-farsi.netlify.com
m
So this isn’t a prerender issue. The prerendering works great and all other bots (twitter, slack, etc) are doing well reading the pages. The issue is that googlebot get the page and then insists on running the js so that when it makes the network request it gets blocked from the graph.cool servers 😕
@nilan have you tested your personal site on google webmaster tools? Specifically with the “fetch as google” tool? Sorry to keep bothering you with this …