For the purposes of this article, the key takeaway here is that in 2019, you can’t rely on search engines to accurately crawl and render web applications that rely on JavaScript. If your content is rendered client-side, Google crawling will be resource-intensive and your site will perform poorly in search. No matter what you’ve heard to the contrary, if organic search is a valuable channel for your site, you need to prepare for server-side rendering.
But server-side rendering is an often misunderstood concept...
This is a common SEO audit suggestion that I often hear presented as if it is a self-contained, easy-to-do solution. At best, it is an oversimplification of a huge technical undertaking, and at worst, it is a misunderstanding of what is possiblenecessarybeneficial for the website in question. Server-side rendering is the result of many possible setups and can be armenia mobile database achieved in many different ways; however, ultimately, what we care about is having a server return static HTML .
So, what are our options? Let’s break down the concept of server-side rendered content a bit and explore our options. Here’s the high-level approach outlined by Google in the aforementioned IO conference:
Dynamic rendering - Here, regular browsers get a "standard" web application that requires client-side rendering, while bots like Googlebot and social media services serve static snapshots. This involves adding extra steps in the server infrastructure, namely fetching the web application, rendering the content, and then serving it to the bot based on its user agent ie.