Publish and verify a static website

Build once, inspect the artifact

A preview should represent the exact source and dependency lockfile that passed checks. Record the commit and deployment identifier. Avoid changing production configuration during an untracked manual build.

Preview safely

Preview URLs must use noindex controls or access protection. They should not emit the preview host as a production canonical. Exercise deep links, error states, copy or form behavior, mobile layout, and content review in the preview.

Promote only after gates pass

Run type, lint, unit, content, link, build, browser, accessibility, and security checks. If the platform supports promotion, promote the validated artifact instead of rebuilding different source for production.

Verify the real domain

Check HTTPS, alternate-host redirects, status codes, canonical tags, robots, sitemap, structured data, primary journeys, telemetry receipt, and availability checks. Do not replace this step with a deployment-success message.

Preserve rollback

Identify the prior healthy artifact and document the rollback operation before promotion. Practice against a preview or noncritical release so the procedure is not theoretical.