NEONB
Abstract cover: dark field with fine geometry and studio light

Engineering

Static export, SEO, and why less runtime is often more

Why we prefer shipping studio sites as static HTML — and what that means for performance, hosting, and search.

Published

Most studio sites do not need a server on every request. They need clear content, fast delivery, and URLs that work for people and crawlers alike.

What static export means here

With Next.js output: "export", HTML is produced at build time. Cloudflare Pages (or any static host) serves files — no Node runtime on the request path.

next.config.mjs
/** @type {import('next').NextConfig} */
const nextConfig = {
  output: "export",
  images: { unoptimized: true },
}
 
export default nextConfig

That fits:

  • Studio and agency sites
  • Blog and case-study content
  • Sites with a small, known set of routes and i18n

SEO is not automatic — but static HTML helps

Static HTML helps because the content is in the document immediately. What still matters:

  1. Unique titles and descriptions per page
  2. Canonicals and hreflang for DE/EN
  3. Sensible internal linking
  4. Content that answers a real question

Without those, the stack alone will not save you.

What we deliberately skip

For the first blog slice: no CMS layer, no client-only articles, no tracking noise. Content lives as files in the repo — versioned, reviewable, rendered at build time.

Good defaults beat late optimization. Structure first, complexity second.

Next

Case studies come next — same content pattern, richer layout room. The blog stays the lighter channel for topics and thinking.

If you are shaping a digital presence and want to keep the stack lean: write us.

All posts