Google’s search advocate, John Mueller, said sites are in no rush to move away from dynamic rendering, although a help document says it’s not a long-term solution.
Mueller posted a comment on a Reddit thread asking for advice on dynamic rendering vs server-side rendering.
The issue arises because of a recent update to Google’s help documentation that says “Dynamic rendering is a workaround, not a long-term solution.”
Additionally, the documentation recommends using server-side rendering, static rendering, or hydration instead.
It’s understandable how someone implementing dynamic rendering reads and concludes that they need to switch.
However, Mueller clarified that the difference between dynamic rendering and other solutions lies in infrastructure setup and maintenance considerations.
This is not to say that dynamic rendering will cause problems for Google or will soon be unsupported.
Here’s Mueller’s comparison of dynamic rendering versus server-side rendering.
Mueller: Dynamic rendering won’t cause problems for Google
In a Reddit thread, SEO professionals seek information on the benefits of switching from dynamic rendering.
One Google Help Documentation Conversion is recommended, but it will be a major undertaking for the web development team.
As far as SEO is concerned, is it worth the time and effort?
Here’s what Mueller said:
“There is no SEO ranking bonus to implement it one way or another – they are just different ways of making content indexable (and client-side rendering as well). From my POV, the difference between dynamic rendering and server-side rendering It’s more about the actual infrastructure setup and maintenance (it also affects speed, depending on how you set it up).
Don’t rush to give up dynamic rendering, it won’t be unsupported or cause problems for Google. What has changed over time is that if you have a JS based site, there are better options (good CSR or SSR) available, so doing things dynamically based on the user agent is usually not the most efficient way. “
If you’re implementing dynamic rendering now, Mueller says, he recommends using a different solution the next time you rebuild your site.
He continued:
“If you’re doing dynamic rendering right now, of course you can look at the options and write down the pros and cons for you. I don’t think most people can convince a stretched engineering team. But if you plan to rebuild your site, let them know they don’t It takes too much time to dynamically render content. Also, know what to watch out for :-).
That’s what it’s really about knowing some JS as SEO – you don’t have to write code, but JS is part of all modern websites, and you can judge for yourself if there’s a problem with it being implemented. If you’re doing dynamic rendering right now, it’s certainly possible to look at the options and write down the pros and cons for you. I don’t think most people can convince a stretched engineering team. However, if you plan to rebuild your site, let them know that they don’t need to spend as much time rendering content dynamically. “
If you have similar concerns as a Reddit user, hope this helps put your mind at ease.
resource: Reddit
Featured image: Leremy/Shutterstock