What triggers the production build
When the feature branch is merged into main, Vercel detects the push automatically and starts a fresh production build. No manual deploy step, no FTP, no server SSH session.
$ git checkout main
$ git merge feature/new-services-page
$ git push origin main
# Vercel detects push → runs build → deploys to edge
# ✓ Production updated worldwide
What Vercel does
Vercel runs next build on its infrastructure, producing optimised static pages and serverless function bundles. The output is distributed to data centres on a global edge network — so visitors are served from a location physically close to them.
HTTPS by default
Every deploy gets a valid SSL certificate automatically. No configuration required.
Atomic deploys
The new version goes live all at once — no partially-updated state visible to visitors.
Instant rollback
Any previous production deploy can be reinstated in one click from the Vercel dashboard.
Traceable to a commit
Every production deploy maps to an exact Git commit. What went live and when is always knowable.
The live site is the build output
Visitors receive pre-rendered, optimised pages from the edge. There is no WordPress admin layer or database assembling HTML on every page request. The site that went through preview and testing is exactly the site that is live — not a separate environment that might behave differently.
What the public sees is always traceable to a specific version of the code. That predictability is one of the main structural advantages over a traditional CMS workflow.