WotWP Blog

How to move a website without downtime: launch week, step by step

A brass door key on a metal ring with a kraft paper tag reading SPARE, on a blue background

The short answer

You move a website without downtime by building the new site next to the old one, approving it on a private preview, and changing where your domain points only at the very end, with the old site still running and the steps to switch back written down. Visitors never meet an empty page, because the old site keeps answering until the new one has passed its checks, and it stays ready for days afterward in case you need it.

This guide is launch week from the owner's side. It assumes the new site is already built and checked page by page. If you are earlier than that, start with our website migration SEO checklist, which covers the full list of checks before, during and after a move.

You need four things before you start: the login for wherever your domain's settings live (your registrar, your host or a DNS provider such as Cloudflare), an hour of your time for the preview, one named person who will do the switch and, if needed, the switch back, and access to Google Search Console.

  • A week before: approve the preview. See the new site and its check report, then say yes in writing.
  • Write the rollback down. What would make you switch back, who decides, who does it, and the exact settings to restore.
  • A day or more before: lower your DNS TTL. So the switch, and any switch back, reaches visitors quickly.
  • Switch day: change where the domain points, and nothing else. Then re-run the checks on your real domain.
  • The first 72 hours: watch forms, missing pages and Google. Fix what shows up the same day.
  • Retire the old site only when nobody is using it. Back it up, save what lives only there, then cancel.

1. A week before: approve the preview, not a promise

The new site should exist at a private preview address while your live site stays untouched. Before launch week starts, open that preview, read the check report that compares it with your live site, and give your approval in writing. If anything on the preview is wrong, the switch waits. Nothing about the domain changes until you say yes.

What to look at on the preview, in this order:

Look at

What has to be true

The pages that bring in leads

They read the same as today, on a phone and a computer

The check report

Every old address answers on the preview, or has a one-to-one redirect, and the search details match

Every form

A test message from the preview arrived in the right inbox, not in spam

Anything that should stay hidden

Drafts and private pages do not open when you are logged out

The preview itself

It is hidden from Google, so the copy never competes with your real site

Then pause edits on the old site from the day you approve until the day you switch. A blog post or price change made in WordPress after the new site was built will not be on it. If something has to change that week, write it down so it can be added to the new site before the switch.

2. Write the rollback down before anything moves

A rollback is the plan for switching back to the old site if the new one misbehaves after launch. Write it before the switch, in a shared document, so nobody has to make it up under pressure. It names what would trigger it, who decides, who does it, the exact settings to put back, and how long the old site stays ready.

Write down

Example

What would make you switch back

Forms not delivering, a block of pages missing, the site down on phones

Who decides

You, or the person you trust to decide while you are with a customer

Who does it

One named person, with the domain login, reachable for the first 72 hours

The exact settings to restore

A screenshot or export of every DNS record as it is today, taken before anyone edits anything

How long it takes

About as long as your DNS TTL, which is why step 3 lowers it

How long the old site stays ready

Until traffic to it has stopped and you no longer need a way back (step 6)

The screenshot of your current DNS records is the single most useful thing in the document. With it, switching back means typing the old values back in. Without it, someone has to remember them.

EmDash's own migration guide puts it the same way: keep the backup and the WordPress site "until the new site has run successfully in production and rollback is no longer required" (EmDash docs). A move with no written way back is a bet.

3. Lower your DNS TTL a day or more ahead

DNS is the setting that tells the internet where your website lives. Each DNS record carries a TTL, or time to live: how long internet providers may remember the old answer before asking again. Lowering it ahead of the move means the switch, and any switch back, reaches visitors in minutes or hours instead of a day.

Google's guide to moving a site without changing its addresses explains that "DNS settings are usually cached by ISPs based on the specified Time to Live (TTL) setting", and suggests lowering the TTL to "a few hours" well ahead of the move, at least a week in advance where you can (Google Search Central).

  • Which records. The ones for your website: your bare domain (yourbusiness.com) and the www version. Leave every other record alone.
  • How low. A few minutes to an hour. Most DNS providers offer options in that range.
  • When. At least a day before the switch, and longer if your current TTL is long. A lowered TTL only takes effect once the old, longer one has run out.
  • Afterward. Once the new site has settled, the TTL can go back up.

If you cannot find the TTL setting, ask whoever manages your domain. It is a normal request, and their answer tells you who will have the login on switch day.

4. Switch day: change where the domain points, and nothing else

On switch day, one person changes your domain's website records to point at the new site, at a quiet hour, with the rollback document open. Change only those records. Do not move the domain to a new registrar, redesign the site or change your email the same day, so that if something looks wrong you know exactly which change caused it.

Pick a time when traffic is low and both you and the person doing the switch are free for the next few hours. Avoid the day before a holiday, a big campaign or a trip.

The order that keeps visitors on a working site:

  1. Check the preview passed its last check. Same report as step 1, re-run if anything changed since.
  2. Copy your email records exactly. Your domain's settings also say where your email is delivered. If the move touches those settings, the email records (MX, plus the TXT records that prove mail comes from you) must stay exactly as they are, or your website looks fine while your inbox goes quiet.
  3. Point the website records at the new site. Usually your bare domain first, then www.
  4. Re-run the checks on your real domain. The pages that bring in leads, every form, a few old addresses that should redirect, and the padlock in the browser.
  5. Open the site to Google. The preview's "hidden from Google" setting must be gone on the live site, and the sitemap submitted in Search Console.
  6. Send one ordinary email from a personal account to your business address, and check it arrives.

If any of these fails and cannot be fixed within the hour, follow the rollback. Putting the old records back is not a defeat. It is the plan working.

Search Console has one trap worth knowing on switch day. If your site was verified with an uploaded HTML file, that file may not exist on the new site, and you can lose access just when you need the reports. Switch the verification to a DNS record before the move.

5. The first 72 hours: what to check, and when

For the first three days, check the things that would cost you leads first: forms, missing pages and whether Google can reach the new site. The problems to look for are small ones, such as a missed redirect or a form sending to an old address, and each is quick to fix when someone looks the same day.

When

Check

The first hour

Every form on the real domain, on a phone and a computer. One email to your business address

End of day 1

The list of "page not found" addresses. Each real page on it gets a redirect to its closest match

Day 2

Search Console's URL Inspection on your home page and a page that brings in leads, so you know Google reaches the new site

Day 3

Form messages arriving as usual, the spam folder, and whether traffic to the old server is tapering off

Google suggests exactly that last check: "Keep an eye on the server logs on both new and old servers", expecting traffic on the old one to fall as the new one rises (Google Search Central). If your old host shows a visitor count, that is enough.

Missing pages are the one to act on fastest. Our guide to what a redirect is explains why an address that stops answering takes its search history with it. Forms come second: our contact form test is the routine to repeat on launch day and in the week after. Rankings can move for a few weeks while Google recrawls, so judge the move against a baseline after 90 days, not after three.

6. Retire the old site only when nobody is using it

Keep the old site and its hosting until traffic to it has stopped, the new site has run without trouble, and you no longer need a way back. Google's guidance is to shut the old hosting down once "the traffic to the old provider reaches zero" and you are confident all visitors, Googlebot included, are on the new site (Google Search Central).

Before you cancel, work through this list. Each item is something that lives only on the old hosting and disappears with it:

  • A final full backup. The database and the uploads folder, stored somewhere other than the old host. Our website hosting checklist covers what a real backup includes.
  • Old form messages. Entries stored in the WordPress dashboard do not move with the site. Export the ones you need.
  • Your email. If your mailboxes are hosted with the same company as the old website, move them before you cancel, or they close with the account.
  • Your domain. If the domain is registered with the old host, keep that part of the account, or transfer the domain on its own, weeks later, keeping every DNS record the same.
  • The redirects. They live on the new site, not the old one, and should stay for "generally at least 1 year" (Google Search Central).

Then cancel, put the TTL back up, and note the date in your rollback document. The document has done its job.

Who should not plan a move at all

A careful launch week only helps a site that should move. If your site is a store, has members or courses, or is built around one plugin feature such as a booking or directory system, moving means rebuilding that feature, and staying on WordPress is usually the right answer for now. The same is true if the site works, costs you little and nobody touches it.

If you are unsure which side you are on, our guide to whether you should move off WordPress walks through the questions, including the reasons to stay.

How we run launch week on EmDash

We move WordPress sites to EmDash, the open-source CMS from Cloudflare that its makers call "the spiritual successor to WordPress", built on Astro. Bring your WordPress site into the AI era on EmDash and Astro.

EmDash's own guide says to review what was imported "before changing DNS or retiring WordPress" (EmDash docs), and launch week on every move we take on follows that order:

  • Preview first. The new site is built on a private preview while your live site stays untouched, and nothing changes until you approve it.
  • Every page checked. Each URL, redirect, form and search detail on the preview is compared with your live site before the switch.
  • Plenty of notice. We tell you ahead of time what changes in your domain settings and when, and confirm each change has taken effect.
  • Only the website records change. Nothing else in your domain settings is touched.
  • Rollback named. The way back is written down before launch, and we ask you to keep your WordPress hosting until you no longer need it.
  • Checked after launch. We host the site and email you a monthly certificate listing the checks we ran and what changed.

A free, read-only check of your public pages shows whether your site is a good fit and gives you the exact price before you ask, with every option listed under pricing.

Want to see where your site stands first? Check your site for free.

Frequently asked questions

Can I move my website without any downtime?

Yes, if the new site is built and checked before the switch and your domain is pointed at it only at the end. The old site keeps answering until the change reaches each visitor, so nobody sees an empty page. Lowering your DNS TTL a day or more ahead keeps that changeover short.

Will my website go down during a domain transfer?

Moving a website does not need a domain transfer. You only change where the domain points. If you also want the domain at a new registrar, do it separately, weeks before or after the move, and keep every DNS record the same, so the website and email carry on without a gap.

How long does a DNS change take to reach everyone?

Roughly as long as the TTL on the records you change. With a TTL of an hour, most visitors reach the new site within an hour or two. With a TTL of a day, some may see the old site for a day. That is why the TTL is lowered well before switch day.

What is a website rollback plan?

A short written document saying what would make you switch back to the old site, who decides, who does it, and the exact DNS settings to restore, usually as a screenshot taken before anything changed. With it, switching back takes minutes of work instead of guesswork.

Will my email stop working when I change my DNS?

Not if your email records stay exactly as they are. The same domain settings that point to your website also say where your email is delivered. Change only the website records, copy the email records unchanged, and send yourself a test email right after the switch.

When can I cancel my old hosting?

When traffic to the old server has stopped, the new site has run without problems, and you no longer need a way back. Before cancelling, take a final full backup, export old form messages, and make sure your email and domain are not tied to that hosting account.