Static website

Static describes how pages are delivered, not how they look. A static site can have animations, video, interactive maps and forms that send through an outside service. What it does not do is build pages on the server per visit; every page already exists as a file. The opposite is a dynamic website, which assembles pages from code and a database when they are requested.

Static sites are rarely written by hand page by page any more. Most are produced by a static site generator or a framework that takes templates and content and outputs the finished files in a build step, so editing stays manageable even with hundreds of pages.

How it works

A developer keeps templates, content files and images in a project folder, usually under version control with Git. A build tool combines them into complete HTML pages, optimises images and bundles stylesheets and scripts. The output is a folder of ordinary files that can be uploaded to almost any host, from basic shared hosting to a CDN.

When a visitor requests a page, the server simply finds the file and sends it. There is no application to run and no database query, so responses are fast, the server needs little power, and there are fewer components for attackers to target. Pages can be cached aggressively because they only change when the site is rebuilt.

Anything that must be personal or change on its own is handled outside the static files: a form posts to a small server script or a form service, a booking widget loads from a third party, search runs from an index generated at build time. Content updates mean editing a file or a connected CMS and rebuilding, which takes seconds to minutes.

Example

A roofing company's site has ten service pages, a gallery of finished jobs and a quote request form. Built as a static site, it loads quickly on phones at building sites with weak signal, runs on inexpensive hosting and has no plugins to update. The quote form posts to a small script that emails the office and stores a copy of each enquiry.

The limit appears when the owner wants to add a project photo himself. With no admin panel, he either sends the photos to the developer or uses a simple CMS connected to the build, which commits the change and triggers a rebuild. The company chose the first: it adds projects a few times a month, and a message to the developer is cheaper than maintaining an editing system.

Why it matters for your business

Static sites are fast, inexpensive to host and much harder to hack, which suits small businesses whose content changes occasionally. The trade-off is editing: without a CMS, every change goes through whoever manages the build, and features like logins, shops or member areas need outside services or a different architecture. If several staff publish daily, a static site needs a connected CMS or it becomes a bottleneck. If content changes a few times a month, the lower running cost and risk are hard to beat.

Common mistakes

• Choosing static and then needing staff to publish daily with no editing tool planned.
• Assuming a static site needs no maintenance, when its form scripts, build tools and third-party widgets still need updating.
• Embedding so many third-party scripts that the speed advantage disappears.
• Losing the source project and keeping only the built files, which makes future edits painful.

Questions people ask

Is a static website good for SEO?

Yes, it can be very good. Static pages are fast, fully rendered HTML that search engines read easily. As with any site, rankings depend on content, titles, internal links and structured data, so a static site needs the same SEO work, but it removes most speed and crawlability problems.

Can a static website have a contact form?

Yes. The form itself is plain HTML; the submission goes to a small server script, a serverless function or a third-party form service that emails you and stores the message. Spam protection and data handling need the same care as on any other site.

How do I update a static website?

You edit the content, either in files or in a CMS connected to the build, and the site is rebuilt and uploaded, usually automatically. Without a connected CMS, updates go through a developer. For a site that changes occasionally, that can still be cheaper than maintaining an editing system.