I never understand the logic behind NextJS. The whole point of React and Angular was to put all the client logic on the client side, a clean seperation of concerns, away from the ugliness of JSP, PHP, ASP, etc. Now we are going back to the server again? This just hurts my brain.
Client-side rendering works in SEO. When Google indexes your site, they're using JavaScript just like any other browser.
Worry less about SEO and worry more about making the pages perfect for real users. Server rendered pages are responding faster because they're not blocked by waiting for JS to download, parse, execute. That's why they feel faster. When they feel faster, it's better SEO.
No, please don't believe everything that Google says on its face value, it is a lesson learnt the hard way. The SEO foes down the trash with client side. The entire nextjs SSR / SSG / ISR evolved because Google was dumb and unable to execute javascripts in the first place.
Comment
Client side rendering = bad SEO or not working SEO at all. SSG or SSR fixes that.
Parent comment
I never understand the logic behind NextJS. The whole point of React and Angular was to put all the client logic on the client side, a clean seperation of concerns, away from the ugliness of JSP, PHP, ASP, etc. Now we are going back to the server again? This just hurts my brain.
Replies
Client-side rendering works in SEO. When Google indexes your site, they're using JavaScript just like any other browser.
Worry less about SEO and worry more about making the pages perfect for real users.
Server rendered pages are responding faster because they're not blocked by waiting for JS to download, parse, execute. That's why they feel faster. When they feel faster, it's better SEO.
No, please don't believe everything that Google says on its face value, it is a lesson learnt the hard way. The SEO foes down the trash with client side. The entire nextjs SSR / SSG / ISR evolved because Google was dumb and unable to execute javascripts in the first place.