Google’s John Mueller answered a question on Reddit. “Does anyone know of any studies in which case he’s considering switching from dynamic rendering to server-side rendering?” I hope that.”
John quickly replied: He added, “They’re just different ways of making content indexable (similar to client-side rendering).”
Here’s the full block of what he said:
There are no SEO ranking bonuses to implement in any way. They are different ways to make content indexable (similar to client-side rendering). The difference between dynamic rendering and server-side rendering from my his POV is more about setting up and maintaining the actual infrastructure (which can affect speed as well, depending on how you set it up). There’s no rush to switch from dynamic rendering. It will never be unsupported or raised by Google. Changes over time are now, if you have a JS based site, there are better options available (better CSR or SSR), so doing things dynamically based on the user agent is not a viable option. It’s often not the most efficient approach.
If you’re currently doing dynamic rendering, of course it doesn’t hurt to look at your options and write down the pros and cons. For extended engineering teams, it doesn’t seem convincing most of the time. But if you’re planning on rebuilding your site, let us know that you don’t need to spend too much time dynamically rendering your content. At the same time, know what to watch out for :-). This is where his JS knowledge as an SEO really comes in handy. You don’t have to do any coding, but JS is part of all modern websites and it’s up to you to decide if there’s something wrong with your method. Implemented.
That’s right, if you implemented all this today, don’t use dynamic rendering in your next redesign. If you have the resources to change it, it makes sense to do so. Otherwise, add it to the queue and run it when you can.
Forum discussion on Reddit.