Web Hosting Implementation Guide
Launch or migrate without the downtime. An eight step sequence built on two rules, plus the pitfalls that break sites and email at cutover.
Launch without the downtime
Getting a site onto a new host is routine when you work in the right order, and a source of broken pages and lost email when you do not. The two rules that prevent most pain: never change your domain's DNS until the new site is built and tested, and keep the old host live until the move is verified. Everything below follows from those two rules.
This is the sequence we recommend for a typical WordPress or small business site, whether you are launching new or migrating from another host. Adjust the detail to your stack, but keep the order.
Eight steps to launch or migrate
Choose the host and tier that fit your traffic and stack, and a term you are confident you will use given the renewal. Buy the plan but do not point your domain at it yet.
Create your account, enable the free SSL certificate and confirm the data center region closest to your visitors. Note the temporary URL or IP the host gives you for testing before DNS changes.
Install your CMS or use the host's free migration to copy the existing site. Many hosts migrate the first site free; confirm before you start. Import into a staging or temporary URL, not the live domain.
Click through every key page, form and checkout on the temporary URL. Check images, links, plugins and email forms. Fix issues here, while the live site is still served by the old host.
Only once testing passes, update the domain's DNS records to the new host. Lower the time to live ahead of time so the change propagates quickly. Keep email records intact if your mail lives elsewhere.
After DNS propagates, confirm the padlock loads on the live domain and that contact forms and any hosted email still send and receive. Propagation can take up to a day, so check more than once.
Enable daily automated backups with a restore you have tested, then switch on caching and a content delivery network for speed. Do this before you announce the site, not after the first traffic spike.
Watch uptime and error logs for a few days. Once the new site is stable and email is confirmed, cancel the old host within its refund window if applicable. Keep one final backup of the old site.
Four mistakes that cause downtime
A small WordPress or business site usually moves in a few hours of work plus up to a day for DNS to propagate. Many hosts offer free migration for the first site, which removes most of the manual steps. Plan the cutover for a low traffic window.
It should not if you build and test on a temporary URL first and only change DNS once the new site passes. Keeping the old host live until propagation finishes gives you a fallback and avoids visible downtime.
Not if you preserve your mail records. Email often runs on a separate service or set of DNS records; note them before the move and keep them unchanged so messages keep flowing through the cutover.
One email when the rankings move. The shortlist, the tradeoffs, the price changes. No filler.