Lisp on Workers Without Losing SEO
Why server-rendered HTML matters more than the source language, and how ClojureScript still fits cleanly on Cloudflare.
Search engines do not care whether the source code started as TypeScript or ClojureScript. They care whether the first response already contains the real content.
SSR is a delivery decision
On Cloudflare Workers the runtime is still JavaScript or WebAssembly. Choosing ClojureScript means choosing a source language that compiles to JavaScript, not changing the delivery requirement.
Static HTML is often enough
If the site is mostly essays, notes, and project writeups, prerendered HTML covers the SEO-critical path better than request-time rendering. It also simplifies caching and makes failure modes easier to reason about.
Hydrate only what moves
Archive filters and table-of-contents tracking benefit from client code. Article bodies do not. Keeping the body static narrows the hydration surface and reduces the chance of rendering drift.
The worker should stay thin
Use the Worker for redirects, canonical normalization, and static asset delivery. Put the expressive work into the build pipeline instead of turning every request into a rendering event.