Websites and Tech

Deployment

Also called release, going live, push to production

The controlled act of moving tested changes onto the live site, including caches, database updates and checks.

Quick facts: Deployment

Category
Websites and Tech
Also called
release, going live, push to production
Level
Intermediate
Affects
Uptime, conversion tracking, campaign performance, rollback speed
Where to see it
Managed hosting deploy tools, Git-based pipelines, your caching plugin
In this article4
  1. How deployment works
  2. Why deployment matters
  3. Common mistakes with deployment
  4. How to act on it

How deployment works

Deployment is the moment a change stops being a plan and becomes what your customers see. At its simplest it is somebody uploading files over FTP. Done properly it is a defined sequence: take the approved version from version control, copy it to the server, run any database updates the new version needs, clear caches so the change is actually served, and check that the site still works.

Automated pipelines do that sequence the same way every time, which is the point. Many hosts also deploy atomically: the new version is assembled alongside the old one and switched over in a single step, so no visitor ever lands on a half-updated site. The reverse switch is what makes a fast rollback possible.

Why deployment matters

Everything else you paid for — the design, the copy, the testing on staging — reaches customers through this step, and a careless release can undo it. A change that works perfectly in testing can still break live because of a cache that was not cleared, a file that never got uploaded, or a setting that differs between the two servers.

Timing matters as much as method. Releasing into your busiest hour, or while an ad campaign is running, means paying for clicks that land on a site mid-change. Releasing on a Friday evening means whoever notices the problem cannot reach anyone who can fix it.

Common mistakes with deployment

The most expensive is skipping the post-release check. The files went up, the page loads, everyone moves on — and nobody submits the contact form, so a broken enquiry route goes unnoticed until a client asks why nobody called back. Tracking is the other silent casualty: a redeployed template that lost its tag keeps looking fine while your conversion data quietly stops.

The second is having no way back. Without a verified backup and a known-good previous version, a bad release turns into live debugging with traffic arriving. The third is deploying edits made directly on the server, which the next release overwrites without warning.

How to act on it

Write down the release routine once and follow it every time: verified backup, deploy, clear caches, then a short check of the journeys that earn money. That check should include a form submission, a purchase or booking, a page viewed on a phone, and confirmation that conversions are still recording.

Deploy at a quiet time, keep the previous version ready to restore, and tell whoever runs your ad accounts that a release is happening so an unexplained dip has an obvious cause. If your site changes often enough that this feels heavy, that is exactly the case for building it into scheduled site maintenance rather than doing it from memory each time.

Do and do not

Do

  • Take a verified backup immediately before every release
  • Clear caches, then check forms, checkout and tracking
  • Deploy at a quiet hour with someone available

Do not

  • Release late on a Friday or into peak traffic
  • Assume a loading home page means the release worked
  • Make manual server edits a later release will overwrite

Questions people ask about this

When is the best time to deploy website changes?

During a quiet period for your audience, and while somebody who can fix problems is still available. Late Friday is the classic bad choice: the release looks fine, a fault appears over the weekend, and nobody is watching. Check your analytics for the genuinely low hours rather than assuming night is quiet everywhere.

What should I check immediately after a release?

The paths that make you money, not just the home page. Submit the contact form and confirm the enquiry arrives, complete a test purchase or booking, view a key page on a phone, and check that conversions are still being recorded in your analytics and ad accounts. Broken tracking is the failure people notice last.

What is a rollback?

Putting the previous working version back after a release causes problems, rather than trying to repair the new one while visitors are arriving. It needs two things prepared in advance: a verified backup including the database, and a definitive record of what the last good version was. Without those, rollback is not actually available.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.