Skip to the content
searchboar.

Crawling and indexing

Static site generation: Meaning, examples and limitations

Static site generation, or SSG, creates HTML documents before visitors request them. The finished files can be delivered directly, so reading a page does not inherently require running the application or querying a database for every visit.

At a glance

  • SSG moves document creation to a build or regeneration step.
  • A static page can still include optional JavaScript.
  • Content changes need a new artifact or an explicit regeneration path.
On this page
An editorial press produces finished pages before visitors arrive.
Static site generation, or SSG, creates HTML documents before visitors request them.

What is generated ahead of time?

A build combines content and templates into HTML files. The delivery system serves those files to readers. Unlike ordinary request-time SSR, it does not need to reconstruct an unchanged document for every request. The rendering reference describes the distinction.

SSG does not necessarily mean “no JavaScript.” A generator can still attach a large application bundle. A simple reference page can instead use ordinary links and only the small enhancements it actually needs.

Example: a bilingual glossary

Imagine 300 concepts with an English and Hungarian definition each. A build can create 600 article documents, localized indexes and category pages. Each article can contain its complete explanation, metadata, image and CTA before any visitor arrives.

The same illustration can be reused across translations with localized alt text. Updating a definition requires rebuilding the affected output or using the site's defined regeneration mechanism. The live site does not automatically read an edited Markdown file on a developer's laptop.

Why can this reduce request costs?

Serving public files can avoid per-visit database queries, application rendering and provider calls. A CDN can distribute them efficiently. But storage, transfer, build systems and dynamic features still have their own limits and pricing. Static architecture is not a universal zero-bill guarantee.

Keep private account routes and paid product operations separate. A static glossary should not accidentally expose source files, secrets or account data as downloadable assets.

What are the practical limitations?

Freshness depends on publishing and cache refresh. A stale deployment can serve old content perfectly quickly. Large libraries also need build-time validation of links, images, canonical URLs and language alternatives. Test the actual deployed document and error behavior; a successful local build alone does not establish public routing or indexing.

Sources

  1. Google: Static site generation