Go-live checklist - Sevalla docs

Before you point real traffic at a static site, go through these checks. Each one links to the page that explains it.

Check the build

The latest production deployment shows Deployed and the site’s status is Live. Open the site’s sevalla.page address and click through its main pages. See Deployments.
The Publish directory is your build’s output folder, such as dist, not the repository’s source. See Build settings.
The build log has no There is no lock file. warning: commit your lockfile so every build installs the same versions.
The Node version is a fixed major version, such as Node 22, so a new LTS release doesn’t change your build without warning. See Node versions.

Check missing pages and URLs

Missing pages return your 404 page with status 404, from a 404 rule in _redirects. A single-page application serves index.html instead. See Custom 404 pages and Serve a single-page application.
You’ve chosen whether page URLs end in /, and set pretty URLs to match. Changing it after launch changes every page’s URL.
If the site replaces an older one, _redirects sends the old URLs to the new ones with 301, and the build log shows Redirects processed successfully!.

Check headers and caching

Security headers such as Strict-Transport-Security and X-Content-Type-Options are in a _headers file. See Custom headers.
Files that keep their name across deployments have a short Cache-Control, since browsers keep files other than HTML for 30 days by default. See Cache files that keep their names.
curl -I https://<name>.sevalla.page/ shows the headers you expect.

Check environment variables

Every variable the production build needs is set, with Production availability. See Environment variables.
No secret reaches the published files: anything the build embeds, such as VITE_ or NEXT_PUBLIC_ variables, is public.

Check deployments

Auto-deploy is on for the branch you release from. See Deploy automatically on push.
In a monorepo, deploy paths skip pushes that don’t touch the site.
Your team knows that Deploy now on a feature branch replaces the live site, and uses pull request previews to review branches.

Add your domain

Your custom domain is added, verified and serving the site over HTTPS. See Add a domain and SSL certificates.
The custom domain is the site’s primary domain, so Visit site in the dashboard opens it.
The other variant (www or the apex) is added too and redirects to the primary one with a domain-level rule.

Check access and costs

Only the people who should change the site can. See Users and roles.
A usage alert warns you when the company’s spending this billing period passes an amount you set, for example if traffic takes bandwidth past the free 100 GB. See Usage and usage alerts.