Does the simple api block googlebot? I'm getting t...
# prisma-whats-new
w
Does the simple api block googlebot? I'm getting the same issue as reported here https://www.graph.cool/forum/t/seo-and-googlebot/188/2 Unfortunately there was no definitive answer
@nilan, I'm trying to get my site to be more SEO friendly, and being unable to have events on my site crawled by googlebot due to the graphcool API being
Temporarily unreachable
is putting a damper on that 😅
h
Ssr?
w
No, I'm using a create-react-app based site. The parts that don't require graphcool data are crawled and rendered by google just fine... event fairly complex pages
but using google's search console 'fetch as google' tool, I can see that googlebot isn't pulling the data from graphcool properly, and it's reporting that the
<https://api.graph.cool/simple/v1/******>
url can't be accessed because it is
Temporarily unreachable
h
But you can avoid that with SSR a lot of search engines don't support crawling javascript apps
w
for now if I could just get it working on google I'd be happy. I worry that switching to an SSR friendly framework would be a lot of work/refactoring
if googlebot really is blocked from accessing the simple api, then I think my next course of action is using algolia to supply the data instead on those pages
When I proxied the request through netlify's rewrite rules (https://www.netlify.com/docs/redirects/#proxying) it worked, which makes me think that requests from googlebot are being blocked for some reason by graphcool
l
I had the same "temporarily unreachable" problem. And came to the same conclusion as you @wallslide. It would be nice to know if GC are blocking indexing deliberately.
👍 1
SSR is not always an option. And even if Google is the only one to index JS based pages, their market share is a great start.
I replied to the original forum post you mentioned hoping for a solution.
w
great, I'll do the same
ahh, never mind, you already summarized it well 🙂
👍 1