Skip to main content Scroll Top

Build Week 7: Launch Day and the Steps Around It

Launch is the moment the new website replaces the old one, or appears for the first time. In the seventh stage of our Build Week series, the focus is on doing that safely. A good launch is usually uneventful to the outside world. Customers simply find a better website one day. Behind the scenes, though, a careful sequence of steps makes that smooth handoff possible.

Choosing the timing

Launch timing matters more than many people realize. Most teams avoid launching right before a weekend or holiday, when fewer people are available to fix problems. They also avoid the business’s busiest days. A weekday morning in a quiet week is a common choice. If the business has a big promotion or season coming, launching well before it, rather than just before, gives room for adjustments.

The pre-launch checklist

In the day or two before launch, the team usually confirms a list of essentials:

Advertisement
  • A full backup of the old website exists and is stored safely.
  • All must-fix items from testing are resolved.
  • DNS records are documented, and their TTL values have been lowered so changes spread quickly.
  • Email-related records are identified so they are not disturbed.
  • Store payments are ready to switch from test mode to live mode.
  • Everyone knows who is doing what on launch day.

Going live

The actual switch depends on the setup. Often, it involves pointing the domain to the new hosting by updating DNS records, or moving the finished site from staging onto the production server. Then the team works through a short sequence:

  • Confirm the SSL certificate is active and every page loads over HTTPS.
  • Remove any settings that blocked search engines during development.
  • Switch payment and email integrations from testing to live.
  • Apply the redirect map from old page addresses to new ones.
  • Submit an updated sitemap to search tools, if they are in use.

Because DNS changes take time to spread, some visitors may briefly see the old site while others see the new one. That is normal and usually settles within hours.

The first hours after launch

Immediately after launch, the team repeats key tests on the live site. Forms are submitted again, a real order may be placed and refunded, and the most important pages are checked on phones. Monitoring tools are confirmed to be watching the new site. Email is checked to make sure it is still arriving normally.

The business can help by being available for quick questions and by noticing anything that seems off. A message from a customer about a strange page or a missed confirmation is valuable early warning.

Telling people

Once the site is stable, it is time to let people know. Update links in email signatures, online listings and social profiles if any addresses changed. A short announcement to customers can invite them to look around. Then comes the part many projects forget: the first month after launch, which is the focus of Build Week 8.

Advertisement

A Launch-Day Run Sheet

A simple run sheet, shared with everyone involved, turns launch day from a series of conversations into a sequence of tasks. It does not need to be elaborate. A list with times, owners and a checkbox for each step works well. A typical outline might be:

  1. Morning check-in. Confirm everyone is available and the old site’s backup is complete.
  2. Final content freeze. No more edits to the staging site once the move begins.
  3. The switch. The web team updates DNS or moves the site to production.
  4. Immediate checks. HTTPS, homepage, main menu and contact page on a phone and a computer.
  5. Feature checks. Every form, booking flow and checkout, in live mode.
  6. Redirect checks. A sample of old addresses, especially ones printed on materials or linked from elsewhere.
  7. Email checks. Send and receive messages on the business’s own addresses to confirm email was not disturbed.
  8. End-of-day review. List anything found, decide what needs fixing now and what can wait.

Having a Rollback Plan

Most launches go smoothly, but a prepared team decides in advance what it will do if something serious goes wrong. A rollback plan answers a few questions ahead of time:

  • What kind of problem would be serious enough to switch back to the old site?
  • How would the switch back be done, and how long might it take for visitors to see it?
  • Who makes the decision?
  • How will customers be told if there is an interruption?

Lowered TTL values and a recent backup of the old site make rolling back much quicker if it is ever needed. Having the plan written down usually means it is never used, because everyone launches with more confidence.

Common Launch-Day Problems and What Usually Causes Them

  • Email stops arriving. Often caused by DNS changes that replaced or removed mail records. This is why email records are identified before launch.
  • Security warnings in the browser. Usually means the SSL certificate is not yet active for every version of the domain, such as with and without www.
  • Some images or links point to the staging site. Addresses that were not updated during the move. A search for the staging address across the site usually finds them.
  • Forms submit but nothing arrives. Notification settings may still point to test addresses, or messages may be landing in spam on the new server.
  • Search engines still blocked. A development setting that discourages indexing was left switched on. It is easy to miss and important to check.
  • Payments still in test mode. Orders seem to work but no money is collected. One real order, refunded afterward, confirms the switch.

What the Business Should Have Ready

  • A person available most of the day to answer questions and approve decisions.
  • Logins for the domain registrar and email administration in case the web team needs help confirming a setting.
  • A short message ready for customers in case of a temporary problem.
  • A list of places where the website is linked, such as listings, social profiles and email signatures, ready to update once things are stable.

Questions Owners Ask

Will the website be down during launch?

Usually not in a way most visitors notice. Some may see the old site for a while as DNS changes spread, but the site generally remains available throughout.

Should we announce the launch the same day?

Many businesses wait a day or two, until the site has been checked on the live domain and any small issues are fixed. There is no advantage in sending people to a site that is still settling.

Latest stories

View all
Our clients