Skip to main content

By the time a new website is ready to launch, most of the hard work is done. The design is approved and the site has been tested. Yet launch day is when owners tend to get most nervous, and with some reason. Going live depends less on the website itself than on the domain settings around it, which are often controlled by someone outside the project.

We learned how much that matters on a large e-commerce launch several years ago. We had planned it meticulously. It was booked for 10:00am on the Tuesday after the Labour Day long weekend, and all the development and final testing had wrapped up the week before.

Early on that Tuesday morning, before business hours, we noticed the client’s existing website wasn’t working at all. Visitors were seeing an error page saying no database connection could be established. The launch hadn’t started yet, or so we thought.

Once we were in the office, the cause became clear. The client’s DNS settings had already been switched to the new server’s address, but the new site hadn’t been loaded onto that server yet. The person who controlled those settings had made the change at 2:00am on the Saturday, three days early.

We had them switch the settings back so visitors could reach the old site, held off for a day while we regrouped, and launched without any further hiccups.

The lesson stuck with us. On the Friday afternoon, we had emailed the whole team detailed launch instructions, including the new server’s address. The IT team saw their task on the list but ignored the timing instructions.

These days our pre-launch email explains what will need to happen, but the new IP address only goes out at the moment of launch. With nothing to change it to, nobody can accidentally change it early.

What actually changes when a site goes live

Your domain name doesn’t change, and neither does who owns it. What changes is where the domain points. Behind every domain is a set of DNS records, which work like an address book telling the internet which server holds your website and which one handles your email. Launching a new site mostly means updating that address book, or swapping what sits at the address it already points to.

There are two common ways we handle that:

  • Staying on the same server. We install the new site in a separate folder on the existing server, which allows us to do some initial testing before launch. At launch, a small configuration change tells the server to show the new site instead of the old one. The cutover is instant, visitors see no downtime, and switching back takes moments if something serious turns up.
  • Moving to a new server. We install and test the new site on the new server first, using a setting on our own computers that lets us view it there before anyone else can. Where possible, we also shorten how long the internet remembers the old DNS records, down to about 5 minutes. The switch then spreads quickly, and a rollback would spread just as fast.

Same Server

  • New site built in a separate folder
  • One setting switches it live
  • No downtime, instant rollback

New Server

  • New site installed and tested first
  • DNS memory shortened to about 5 minutes
  • Quick switch, quick rollback
Either way, the new site is ready and tested before anyone points the domain at it.

If any downtime is expected, we tell the client well in advance, so they can warn staff or customers.

In our experience, launches onto our own server go the smoothest. We know that environment inside out, and the interactive demo version of the site the client has been reviewing is hosted on the same infrastructure, so any server-related issues have surfaced during testing. The launches that have dragged on or caused trouble have one thing in common: severely underpowered third-party hosting.

IT administrator and marketing manager reviewing domain settings on a laptop before a website launch

The email risk nobody mentions

The same DNS records that point to your website also route your company’s email. Change them carelessly and the website can come up perfectly while email quietly stops arriving.

We learned this almost 15 years ago, when we moved a client onto our hosting. We used an online tool to scan their existing DNS records and recreated them on the new host. The tool missed some records, and email to outside addresses stopped working. The problem surfaced within 24 hours, but unfortunately the client found it before we did.

Since then, we don’t rely on scanning tools. Before launch, we get access to the original source of the records and export the full set. That export makes the move to the new host straightforward, and it doubles as a backup if anything ever needs to be recreated by hand.

If your form notifications start going missing after a launch, the cause is often in the same records. We covered that in our article on whether your contact form is losing leads.

What we need from you before launch

Some clients give us access to their domain registrar, the company the domain was bought through. That’s the smoothest route, because we can handle every change ourselves.

It’s also where surprises come up. Often nobody at the company knows who has the login. The employee who set it up has moved on, or the company can’t remember where the domain was bought in the first place. It always gets sorted out eventually, so we raise it at the project kickoff rather than the week of launch.

Our article on who owns your website explains why that login belongs to the company and not one person.

Larger organizations usually have an internal or outside IT team that makes DNS changes for them. In that case we need two things:

  1. Their contact details, so the right person hears about the launch directly.
  2. How quickly they can act, because lead times vary between organizations, and we need to know theirs to schedule the launch.

Before Launch Day

Who controls the domain and its DNS
A registrar login, or an IT contact
How quickly the IT team can act
A full export of the current DNS records
One agreed launch date and time
Raise these at the project kickoff, so nothing is missing when launch week arrives.

Why we launch on Friday mornings

Clients are often surprised when we suggest a Friday morning for their website launch. The common wisdom says to avoid Fridays, because people leave early and nobody is around if something breaks. We see it differently, for a few reasons:

  • It’s a quieter day for us. Fewer leads, phone calls, and support requests come in on Fridays, so the team can focus on the launch.
  • It’s usually quieter for our clients’ sites too. Most B2B websites see lighter traffic on Fridays, so any issue reaches fewer real visitors.
  • The morning gives us the whole day. There’s time to work through our launch checklist and fix anything that turns up.
  • The weekend is a safety net. If something is still unresolved at the end of the day, we can work through the weekend, when B2B sites see the least traffic of all. We plan to be available that weekend, just in case.

Part of that checklist protects your search rankings. Google’s guidance for moving a site with URL changes recommends permanent redirects from every old address straight to its new one, kept in place for at least a year. It also suggests submitting the new sitemap in Search Console. Our article on redesigning without losing your Google rankings covers that side in more depth.

Web team going through a website launch checklist over morning coffee

The first 30 days

Every site we launch comes with a 30-day post-launch warranty. It covers functionality issues that show up in that first month. If a problem comes from our theme or custom code, we fix it as soon as possible, especially if it affects visitors.

Third-party WordPress plugins are the exception. When a plugin causes the problem, we work with its developers on the client’s behalf. Most of the time that resolves it, but once in a while the answer is that the plugin can’t or won’t be fixed. This is rare, though, because issues like this usually surface during development and get dealt with then.

Because we don’t control that code, we can’t warranty it. We can often propose a workaround, and occasionally the fix is a different plugin, which can mean some additional, billable work. Either way, we talk it through with the client first.

Covered for 30 Days

  • Functionality issues after launch
  • Problems in our theme or custom code
  • Fixed as soon as possible

Outside the Warranty

  • Third-party plugin code
  • Replacing a plugin that can’t be fixed
Even outside the warranty, we work with the plugin’s developers and talk through the options with you first.

In practice, most launches have no issues we don’t catch ourselves on launch day. When a client does spot something, it’s usually within the first week. The most common example is a minor layout problem caused by new content added after launch, such as a longer heading or an extra paragraph that the original template didn’t anticipate.

Search rankings can also move around for a while. Google notes that on a medium-sized site, it can take a few weeks or more for new pages to replace old ones in results. A short wobble is normal, and good redirects help it settle.

Web support specialist taking notes during a client call in the weeks after a website launch

Plan the switch, not just the site

Most launch problems have nothing to do with the website itself. They come from the domain settings and the people who control them, which is why the planning matters more than the day. Sort out who holds the keys early, and hand over each change only when it’s time to make it.

If you’re planning a new site and want the launch handled as carefully as the build, book a discovery call. It’s a useful conversation about your site and your team, with no pitch, and no pressure.


Ian Chapman
Founder of Leaf Design
As the founder of Leaf Design, Ian has spent the last two decades building websites for B2B companies throughout North America including manufacturers, distributors, and service firms.

Curious how this applies to your website?

If any of this hit close to home, we’re always happy to talk it through. Reach out and we’ll pick up the conversation from here.

Or call us at 1-855-253-5323

See What’s Possible

Ready to grow?

Book your 30-minute discovery call where we will:

  • Learn about your business
  • Analyze your website
  • Identify areas of opportunity
Sign up in 60 seconds!

No pitch decks. No pressure.
Just a useful conversation.