Rendering Modes
The rendering mode determines when and where a Web page is generated. Momen supports CSR, SSG, and SSR, which differ in page generation, data updates, and page SEO support.
Select the rendering mode under Settings → SEO → Rendering Pattern. For the complete SEO workflow, see SEO for Web Apps.
Compare rendering modes
| Dimension | CSR | SSG | SSR |
|---|---|---|---|
| Generation | Rendered in the browser when the user visits | Generated as a static page during publishing | Rendered on the server when the page is requested |
| Page data | Loads current data at visit time | Uses data available at publishing and requires republishing to update the page | Loads data for each request |
| Initial load | Loads and runs frontend resources before rendering | Returns a pre-generated static page | Waits for the server to generate and return the page |
| Page SEO | Not configurable | Configurable | Configurable |
| Availability | All plans | Basic plan or above | Single-Tenant Server |
CSR
How it works
When a user visits a page, the server returns the base HTML and frontend resources. The browser loads and runs those resources, retrieves the required data, and renders the page content.
Advantages and limitations
- Advantages: The page loads data at visit time, so backend data changes do not require republishing. It works well for highly interactive application pages.
- Limitations: Frontend resources must load and run before the initial content is rendered. Page SEO cannot be configured.
- Suitable for: Admin tools, dashboards, and authenticated application pages.
Page SEO cannot be configured in CSR mode. Global settings such as sitemap, robots.txt, and custom Header and Body remain available.
SSG
How it works
When the app is published, Momen generates static HTML from the page configuration and the data available at that time. Visitors receive the pre-generated page without waiting for the server to generate the HTML again.
Advantages and limitations
- Advantages: Delivers a pre-generated page without server-side rendering for each request. Page SEO is available.
- Limitations: The page retains the data available at publishing. Republish after its data, page configuration, or dynamic path parameters change.
- Suitable for: Company sites, product pages, blogs, and other public content that changes less frequently.
Dynamic pages
If a page path contains a parameter such as /article/:slug, configure the possible path parameter values in the SEO settings. Momen generates the corresponding URLs and static pages during publishing.
Values can come from a selected database table and field, with filters limiting which records are generated. Republish the app after adding or changing parameter values.
SSR
How it works
For each page request, the server loads current data, generates the page HTML, and returns the complete page to the browser.
Advantages and limitations
- Advantages: The page can use data available at request time, and page SEO is available.
- Limitations: Every request requires server-side rendering, so response time and capacity depend on the server. SSR requires a Single-Tenant Server.
- Suitable for: Public pages that change frequently and also need page SEO.
Choose a rendering mode
- Choose CSR when page SEO is not required and the page should always load current data.
- Choose SSG for relatively stable content that should be delivered as a pre-generated page.
- Choose SSR for frequently changing content that also requires page SEO.
Republish the app after switching rendering modes or changing SSG dynamic page settings.