Understanding SEO impact using Client-Side Rendering w/ Chakra UI
Answered
Barbary Lion posted this in #help-forum
Barbary LionOP
I am looking to use Next.js for a new project but need some help understanding the impact of client-side rendering. I will be using Chakra UI, which only works in client-side components. I am also considering using the App Router.
Can you give me a better understanding of the impact using Chakra UI would have on SEO when set up as shown in their documentation. I am using Chakra UI in a custom design system, so I would essentially be using it everywhere.
Thanks
https://chakra-ui.com/getting-started/nextjs-app-guide
Can you give me a better understanding of the impact using Chakra UI would have on SEO when set up as shown in their documentation. I am using Chakra UI in a custom design system, so I would essentially be using it everywhere.
Thanks
https://chakra-ui.com/getting-started/nextjs-app-guide
Answered by Asian paper wasp
The short version is that: there is no impact on SEO.
The biggest misconception here is Client Component = client-side rendering. This is incorrect. A client component essentially tells React that "this component needs to go through hydration for it to be working correctly", but it doesn't prevent the component from being processed/rendered on the server. In fact, the client component is how things work when we are talking about traditional SSR, e.g. Next.js Page Router.
The biggest misconception here is Client Component = client-side rendering. This is incorrect. A client component essentially tells React that "this component needs to go through hydration for it to be working correctly", but it doesn't prevent the component from being processed/rendered on the server. In fact, the client component is how things work when we are talking about traditional SSR, e.g. Next.js Page Router.
2 Replies
Asian paper wasp
The short version is that: there is no impact on SEO.
The biggest misconception here is Client Component = client-side rendering. This is incorrect. A client component essentially tells React that "this component needs to go through hydration for it to be working correctly", but it doesn't prevent the component from being processed/rendered on the server. In fact, the client component is how things work when we are talking about traditional SSR, e.g. Next.js Page Router.
The biggest misconception here is Client Component = client-side rendering. This is incorrect. A client component essentially tells React that "this component needs to go through hydration for it to be working correctly", but it doesn't prevent the component from being processed/rendered on the server. In fact, the client component is how things work when we are talking about traditional SSR, e.g. Next.js Page Router.
Answer
Barbary LionOP
That's for clarifying. I have seen opposite answers online. ðŸ‘