Hi! First of all, thanks for making this happen, I've been playing with the different examples and I can't wait to see the progress on this, it's already really promising. I love the idea of having an end-to-end framework that answers the most recurrent questions.
I was wondering what will be the easiest way to enable SSR. I understand it shouldn't be that difficult as the stack is already using Apollo, any pointers?
I also would love to know how much of an impact will be on SEO having/not having SSR in the modern world, I've heard mixed opinions on the matter.
Thanks!
adrianmg
>All comments
We don't currently have any mechanism for SSR, as the only "server side" element right now is the GraphQL API deployed to Lambda functions. We do intend to provide an option for routes that will allow you to prerender portions of your website, which for certain cases, will provide similar benefits to SSR (especially around SEO).
As far as SEO in general, the latest I've read on the matter indicates that while the Google indexer will run Javascript just fine, there is always the chance that you deliver some JS code that is incompatible with their indexer and it fails to run your SPA as intended, leading to poor SEO. It's also possible that the way they run your JavaScript leads to slow "page loads" and your SEO suffers because of that.
Our main focus with Redwood right now is around developer experience and smooth integration of the fundamental technologies. We are definitely thinking about the impact of SEO and will be addressing that in the future, but for now Redwood is client-rendered only.
mojombo
on 11 Jan 2020
Related issues
cannikin
路
3Comments
josteph
路
3Comments
hemildesai
路
4Comments
Tobbe
路
4Comments
weaversam8
路
3Comments
Most helpful comment
We don't currently have any mechanism for SSR, as the only "server side" element right now is the GraphQL API deployed to Lambda functions. We do intend to provide an option for routes that will allow you to prerender portions of your website, which for certain cases, will provide similar benefits to SSR (especially around SEO).
As far as SEO in general, the latest I've read on the matter indicates that while the Google indexer will run Javascript just fine, there is always the chance that you deliver some JS code that is incompatible with their indexer and it fails to run your SPA as intended, leading to poor SEO. It's also possible that the way they run your JavaScript leads to slow "page loads" and your SEO suffers because of that.
Our main focus with Redwood right now is around developer experience and smooth integration of the fundamental technologies. We are definitely thinking about the impact of SEO and will be addressing that in the future, but for now Redwood is client-rendered only.