Hacker News Reader

Comment by Lukkaroinen | Hacker News Reader

I wonder where this is actually needed, since most React frameworks support metadata with server-side rendering.

thank your for the comment while it's true that not all web applications leverage the React library, it's important to note that Next.js inherently supports React. However, the choice of technology stack depends on the specific use case and requirements of your project.

It's not about React specifically, but about whether pre-rendering will make any difference from an SEO perspective.

Not only do most frameworks do SSR, but Google is able to crawl dynamic content just fine. Here's an article from 2015 on the topic: https://searchengineland.com/tested-googlebot-crawls-javascr...

Google renders all sites in Chrome according to their documentation. So why would you render it? AFAIK they even penalize serving different content to their crawlers.

sure , but you want aslo your web app available for other bots, and you are not serving other content it same content just you avoid the js layer so it will be quickly serverd, so far for my projects it worked very well ,google serach console showed a better ranking , it s not a new technique and other services like prerender.io do the same things but not free.

Companies still struggle with seo. I've worked at two tech companies so far, and both utilized third-party services for ssr, the reason is that bot allow a few second to render your html if it s not availbale during that time frame, you can use nextjs it s a good alternative. In any case, it remains useful for my own projects and it s free, maybe can useful for other dev

Absolutely. We have a NextJS website and we faced some SEO problems due to Google bot not being able to get to some pages. To be fair, we used too much sliders.

Reply on news.ycombinator.com