FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 5 of 6

Launch day order

The order matters, and launch day is no time to work it out. A run sheet from a week before to the last check, with an owner and a proof for every step, plus a rollback rule.

6 min readUpdated 2026-11-07
All chaptersChapter 5 of 6
  1. 01Is moving worth it?
  2. 02Crawl and inventory every URL
  3. 03Build the redirect map
  4. 04Rebuild content, SEO, forms and tracking
  5. 05Launch day order
  6. 06The first 30 days

The short answer

Launch on a quiet weekday morning with everyone reachable, and follow a written sheet in order: final content, then new site live with blocks removed, then redirects, then checks against your whole old URL list, then the new sitemap in Search Console. Do not start at 5pm on a Friday. Then keep the old site available until you are sure you do not need it.

The exact steps depend on your host and on whether your domain changes, so adapt the sheet below before the day. It follows Google's site move guide and guide to moves without URL changes, with what we add from our own projects.

The week before

Most launch-day trouble is decided here.

WhenStepOwnerProof
7+ daysLower the DNS TTL to a few hours, as Google suggests for host movesWhoever holds DNSRecord shows the new TTL
7 daysConfirm access: DNS, domain, hosting, Search Console, analytics, CMSProject leadEach login tested
5 daysPick the day, and warn sales, support and anyone running adsProject leadNote sent
3 daysContent freeze starts, final crawl of the old siteContent ownerNew rows in the map, if any
2 daysFinal redirect map signed off, and loaded where you canSEO ownerDated copy saved
1 dayBack up the old site, and test the rollback steps on paperDeveloperBackup opens, steps written
1 dayTell your host to expect more crawling if the site is largeDeveloperReply from host

Google notes that crawling usually gets heavier after a move with new URLs, so check your server can handle it. On a host move with no URL change, it says to expect a temporary dip, then a steady rise over the following days.

Pick the time

A good slot has three things: low traffic, your whole team around, and working hours left in the day to fix things. For most B2B sites, a Tuesday or Wednesday morning in your main market works well. Avoid the day before a holiday, the day of a campaign, and any time your developer is about to get on a plane.

Name one person who makes the call on launch day. Others report to that person. A rollback decision by group chat takes too long.

The run sheet

Print this, or paste it into a shared doc. Do the steps in order, and tick each one off with the time beside it. Adapt the wording to your host.

#StepProof it worked
1Publish last content changes to the new siteLatest posts present
2Remove noindex and staging passwords, using your listCrawl of tier A shows no noindex
3Put the final robots.txt in placeFile reads as planned
4Point the domain at the new host, or turn on the new routesDNS checked from several places
5SSL works on every host versionNo certificate warnings, on www and non-www
6Turn on redirectsTier A old URLs land on the right page by hand
7Crawl your whole old URL listEvery row returns the expected 301, or 404 or 410, with no chains or loops
8Crawl the new siteAll 200, self-canonical, no internal redirects
9URL Inspection on key pages in Search ConsoleGoogle can fetch them, with the expected canonical
10Send every form on the live domainMessages land where they should
11Watch tracking in real timePage views and events arrive
12Check on a real phone, with no cachePages look right
13Submit the new sitemap in Search ConsoleStatus reads as submitted, and is read
14If the domain changed: run Change of Address, on the old propertyTool confirms the request
15Update ads, email footers, social profiles and link-in-bio pagesEach one clicked
16Tell the team it is live, and how to report a problemMessage sent

A note on step 14. The Change of Address help page says it is for moving from one domain or subdomain to another. It is not for a change of platform on the same domain, moving from http to https, or a change between www and non-www. It asks you to have redirects in place first, to own both properties in Search Console, and to verify every subdomain version of the old domain. The notice lasts 180 days.

Rollback: decide before you need it

Agree the rule before the day, when everyone is calm. Most problems can be fixed forward. Rollback is for the serious few.

ProblemDo this
A few wrong redirectsFix them. Do not roll back.
One form or event not workingFix fast. Point the form at a working inbox in the meantime.
Old URLs return 404 in bulkFix within the hour if you can. If you cannot, roll back.
The site is down or broken on main pages, and there is no quick fixRoll back, if DNS is the only change so far.
Whole site blocked by noindex or robots.txtFix now. This is one setting, and a roll back would be slower.

Decision rule Set a time limit in advance, such as one hour. If your main pages or redirects are still broken when it runs out, go back to the old site, fix it, and try another day. There is no shame in a second try.

Rolling back gets harder with time, because new data lands in the new site. Note any form messages or content created after the switch, so you do not lose them.

Keep the old site alive for now

Do not cancel the old host on launch day. Google's guide to moves without URL changes says to keep the old hosting running until its traffic falls to zero, and until users and Googlebot are getting the right content from the new setup. That is also your rollback route, your record of the old pages, and where you look when someone asks what a page used to say.

If you are changing domains, keep the old one too. The Change of Address help page recommends paying for the old domain for at least a year. Letting it lapse could hand your old URLs to someone else.

The first hours after launch

Stay close for the rest of the day. Do not schedule other work, and hold off on any new changes to the site.

  • Re-run the old URL crawl a few hours later, in case cache or rules changed.
  • Open the Pages and Sitemaps reports in Search Console, knowing that it can take days to show much.
  • Check for real form messages, and that they reach the right person.
  • Check error logs if your host has them, and look for a spike in 404s.
  • Ask support and sales to tell you about anything odd.
  • Save the live redirect list with the date.

Done when The old URL list is clean, forms are landing, tracking is arriving, and the sitemap is submitted. Then go home. Chapter 6 picks up from here.

Takeaways

What to remember from chapter 5.

  • Lower DNS TTL at least a week ahead, if the host is changing.
  • Launch on a quiet weekday morning, with one person making the calls.
  • Follow the sheet in order, with proof beside each step.
  • Run your whole old URL list against the live site.
  • Set a rollback rule and a time limit before the day. Keep the old host until its traffic reaches zero.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.