Static vs dynamic website
A static vs dynamic website comparison comes down to when the site’s web pages get built. A static website serves HTML pages generated once, at publish time, then delivered as-is to every visitor. A dynamic website builds each page on request, by querying a database or services, which lets it tailor the response to the visitor.
Definition and how it works
An enterprise website can also be mixed. Public pages are pre-generated or cached, while authenticated areas and site search results stay dynamic. The article Static vs dynamic sites: SSG, SSR and what to choose compares both models.
Related terms: Site search · GraphQL API · Content as a service · Headless CMS
Resources that cover this term
The differences in detail
A cached dynamic page behaves, for the visitor, like a static page until it expires.
| Criterion | Static website | Dynamic website |
|---|---|---|
| Personalization | Limited to what the browser does | By visitor, permissions or context |
| Updating content | Requires a new build, partial or full | Visible on publish, cache aside |
Static vs dynamic website in practice
The decision is made page by page rather than by picking a camp. Documentation or corporate pages change little, which suits static generation or long caching. A customer area or a web portal that adapts content to the profile must stay dynamic.
Frequently asked questions
Does going static improve search rankings?
Not automatically. Search engines receive HTML in both cases, provided the page does not rely entirely on JavaScript to display its content. A dynamic site can reach short load times too with well-tuned caching. Implementation determines search quality, not the way pages are generated.
Can a static website be managed with a CMS?
Yes. The CMS serves as the editing tool, then a generator builds the static pages on each publish by reading content through an API, for example from a headless CMS. For editors, what changes is the delay between publishing and going live, as well as preview.