By Matthew Edgar · Last Updated: October 07, 2021
How Content is Loaded
One of the most fundamental (and common) methods of rendering is Server-Side Rendering. As the name suggests, the rendering happens on the web server. This means when a visitor requests a page from your website, your web server will pull together the necessary HTML code and send that code to the browser. The browser doesn’t have to do anything more to the HTML code. Instead, the browser simply has to convert the HTML into a visible web page. Note that you will often hear server-side rendered code referred to as the “raw” code.
What Can Google Support
With dynamic rendering, you render the content differently for bots than you do for human visitors. Human visitors will continue to see content loaded via client-side rendering. However, bots won’t see the client-side rendering and instead will see “pre-rendered” content. Basically, you are rendering your website’s content in advance so that bots don’t have to do the rendering work on their end. By doing this, you have more control over how everything is rendered and over what bots are able to see, ensuring that Google’s bots won’t load part of your website incorrectly.
When using dynamic rendering, it is important that the content seen by bots is equivalent to the content seen by humans. There will likely be a few differences, but you want to make sure the page’s seen by bots and humans serve the same purpose and intention. If you use dynamic rendering as a way of sneaking in highly optimized content that only bots can see, Google will likely catch on and your site could receive a manual action.