Frontend System Design · Lesson 35 of 86 · 4 min
Static Site Generation (SSG) for Speed and SEO
This is your default answer for content-heavy sites. Know its trade-offs cold.
Static Site Generation (SSG) pre-renders your pages into static HTML files at build time. When a user requests a page, a server or CDN just sends the file. That’s it. No on-demand rendering, no database queries. This is the core of why it's so fast and why you need to be able to explain it.
The "Build Once, Serve Infinitely" Model
With SSG, the entire request-time workload is shifted to a one-time build step. Your CI/CD pipeline runs a command (next build, astro build, etc.), which fetches data, renders your components to HTML strings, and spits out a folder of static assets.
You deploy this folder to a CDN. Now, user requests are served from an edge location close to them, resulting in a minimal Time to First Byte (TTFB). The browser receives a complete HTML document immediately, so First Contentful Paint (FCP) and Largest Contentful Paint (LCP) are excellent. This is a direct path to good Core Web Vitals scores.
The process looks like this:
This model is simple and incredibly robust. If your build succeeds, your site is a collection of files that can be served by the simplest web server. High traffic is easily absorbed by the CDN.
Why SSG is the Easiest SEO Win
Search engine crawlers are simple clients. They want fast, linkable, fully-formed HTML. SSG delivers exactly that on every request.
Unlike client-side rendering, the crawler doesn't need to execute JavaScript to see your page content. It gets the same complete HTML file a user would, allowing for immediate and accurate indexing. Because SSG leads to top-tier performance metrics, it also directly satisfies Google's Core Web Vitals, which are a known ranking factor.
For any public-facing content—blogs, documentation, marketing pages, e-commerce product listings—SSG should be your starting point. It aligns perfectly with how search engines want to see the web.
Generating Pages from a Data Source
Most sites aren't just a few hand-written pages. You'll generate pages from a data source like a Headless CMS or a database. For this, you need to tell your framework which pages to build.
In Next.js, you do this with getStaticPaths (to list the pages) and getStaticProps (to get the data for each page).
This example generates a set of blog post pages at build time.
// pages/blog/[slug].tsx
import type { GetStaticProps, GetStaticPaths } from 'next';
// This function runs at build time to determine which routes to generate.
export const getStaticPaths: GetStaticPaths = async () => {
// In a real app, fetch slugs from a CMS or database.
const posts = [{ slug: 'intro-to-ssg' }, { slug: 'ssg-tradeoffs' }];
const paths = posts.map((post) => ({
params: { slug: post.slug },
}));
// { fallback: false } means any path not returned here will result in a 404.
return { paths, fallback: false };
};
// For each path defined above, this function runs to fetch its specific data.
export const getStaticProps: GetStaticProps = async (context) => {
const slug = context.params?.slug;
// Fetch the full post content for the given slug from your data source.
const post = await getPostFromDb(slug);
if (!post) {
return { notFound: true };
}
return {
props: { post },
};
};
// The component receives the fetched data as props.
export default function BlogPost({ post }) {
return (
<article>
<h1>{post.title}</h1>
<div>{post.content}</div>
</article>
);
}
The trap: This model implies a full site rebuild for any content change. For a site with 100,000 blog posts, getStaticPaths means your build process will fetch and render 100,000 pages. This can take a very long time, making it impossible to publish content updates quickly.
Know the Limits: Build Times and Stale Content
SSG is not a silver bullet. Knowing its limitations is more important in an interview than just listing its benefits. The primary trade-offs are build duration and content freshness.
Build Times: As mentioned, build time scales with the number of pages. A 45-minute build to fix a typo is not tenable. This is the single biggest operational headache of large-scale SSG.
Stale Content: The content on your site is only as fresh as your last deployment. If you run a news site and a story breaks, you can't wait for a long build to finish. You need a way to update content faster. A common pattern is using webhooks from your CMS to automatically trigger a new build and deployment, but this is still limited by the build duration.
No Personalized Content: The generated HTML is the same for every user. You cannot use SSG to pre-render a user's account dashboard or a personalized shopping cart. That content must be fetched client-side after the initial static page loads. This can lead to a flash of loading spinners or layout shifts, which harms the user experience.
In an interview, you'll be asked to defend your choice. The question is often "Why not SSG for everything?" Your answer should be about these trade-offs: build times for large sites, content freshness guarantees, and the inability to serve personalized content from the server.
Try it
Use a framework like Next.js or Astro to create two static blog post pages from a local JSON array. Implement the logic to define the routes (getStaticPaths) and pass the content to the component (getStaticProps). Run the build command and see the generated HTML files in the output directory.
Next: We'll look at how to get the benefits of static sites without the long build times and stale content problem by using Incremental Static Regeneration (ISR).
Lock it in — apply this lesson under interview conditions.