Server-side rendering JSS applications

Current version: 22.x

Server-Side Rendering (SSR) is essential to enabling integration with the Experience Editor. The Experience Editor relies on finding the rendered markup of new components added to the pages when they pre-render them.

It is therefore required to use SSR on Content Management (CM) servers to enable inline editing of data by content authors in the Experience Editor. On Content Delivery (CD) servers, the primary reason for using SSR is to guarantee SEO compliance.

We recommend rendering JSS applications server-side if you have content that you want to be indexed by search engines.

Using SSR is not recommended for web apps that render user-specific information, such as user portals, or dynamic interfaces that should not be indexed, such as e-commerce checkout, food ordering, and so on.

To help you server-side render JSS applications, Sitecore provides rendering engines. Each JSS application you connect and deploy to Sitecore can be configured to use a different rendering engine.

You have several options for server-side rendering JSS applications based on the JSS sample apps for React, Angular, and Vue.js:

JSS applications based on the Next.js sample use Next.js-based techniques for server-side rendering.

Do you have some feedback for us?

If you have suggestions for improving this article,