What is static site generation (SSG)?
Static site generation (SSG) is the process of building every page of a website into finished HTML files ahead of time, during a build step, rather than when each visitor requests them.
Curious how your site handles SSG?
Send me the address. I’ll look under the hood and tell you plainly what I find, free.
In plain English
A static site generator takes your content and templates and outputs a folder of ready-to-serve HTML pages. Tools include Astro, Eleventy, Hugo and frameworks built on React. The build runs whenever content changes.
Because the work happens once, at build time, each visit is just a file download. That’s different from server-side rendering, which builds the page fresh for every request.
Why it matters for a small business
Most business websites show the same content to every visitor, so building pages ahead of time is a good fit. You get fast, consistent pages that crawlers read easily, without paying for a server to rebuild them constantly.
An example
A Calgary tour operator has a page for each of its thirty trips. With SSG, all thirty are built into HTML whenever a price or itinerary changes. Visitors and search engines then get the finished page instantly, rather than waiting on a database for each one.
Common mistakes
Where I see SSG go wrong most often.
Using SSG for content that changes every minute, like live inventory, without a plan for updates.
Letting build times grow huge on very large sites without incremental builds.
Forgetting to trigger a rebuild after editing content, so changes don’t appear.
SSG, answered
They’re closely related. Both produce HTML ahead of time. Prerendering is often used for a JavaScript app that is rendered to HTML at build time.
Yes, when paired with a CMS that triggers a rebuild on publish, editors don’t need to touch the build at all.
Keep reading
- nick@tavro.ca
- 587-439-9994
- Calgary, Alberta