server-side-rendering

Render React pages on the server with Next.js data fetching.

235|25|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/PatternsDev/skills --skill server-side-rendering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: server-side-rendering
Source: https://github.com/PatternsDev/skills/tree/main/react/server-side-rendering
Command: npx skills add https://github.com/PatternsDev/skills --skill server-side-rendering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SSR renders HTML on the server to improve initial load times, SEO, and per-request content delivery for React apps.

Core Features & Use Cases

  • Server-rendered HTML provides faster First Contentful Paint and better crawlability for content-heavy pages.
  • Hydration and isomorphic rendering enable seamless client interactivity after the initial render.
  • Use with frameworks like Next.js to fetch data server-side via getServerSideProps or similar data-fetching APIs.

Quick Start

Create a Next.js page that fetches data with getServerSideProps and renders the UI on the server.

Frequently Asked Questions about server-side-rendering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does server-side rendering improve React SEO and initial load performance?

Server-side rendering generates HTML on the server to improve SEO and initial load performance. This provides faster First Contentful Paint for content-heavy pages and ensures better crawlability by search engines before client hydration occurs.

How do I fetch per-request data for server-side rendering in Next.js?

To fetch per-request data for server-side rendering in Next.js, use getServerSideProps within your page component. This fetches data on the server and generates HTML for each request, making it ideal for data-driven pages.

Does server-side rendering require a specific framework like Next.js?

Server-side rendering requires a server-capable framework such as Next.js. It also leverages React 18 streaming APIs via renderToPipeableStream when supported to generate server-rendered HTML for data-driven React applications.

What is hydration and why is it needed for server-rendered React?

Hydration is the process of attaching event listeners to server-rendered HTML to enable seamless client interactivity. Isomorphic rendering ensures the server and client render identically, preventing mismatches during hydration after the initial render.

When should I use server-side rendering versus client-side rendering for React?

Use server-side rendering for content-heavy apps and data-driven pages where per-request data fetching and SEO are critical. If your application does not require per-request data or search engine crawlability, client-side rendering may be more appropriate.

Can I use React 18 streaming APIs for server-side rendering?

Yes, server-side rendering can utilize React 18 streaming APIs via renderToPipeableStream when supported. This streams server-rendered HTML to the client, improving initial load times for content-heavy React applications.