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.
| When | Step | Owner | Proof |
|---|---|---|---|
| 7+ days | Lower the DNS TTL to a few hours, as Google suggests for host moves | Whoever holds DNS | Record shows the new TTL |
| 7 days | Confirm access: DNS, domain, hosting, Search Console, analytics, CMS | Project lead | Each login tested |
| 5 days | Pick the day, and warn sales, support and anyone running ads | Project lead | Note sent |
| 3 days | Content freeze starts, final crawl of the old site | Content owner | New rows in the map, if any |
| 2 days | Final redirect map signed off, and loaded where you can | SEO owner | Dated copy saved |
| 1 day | Back up the old site, and test the rollback steps on paper | Developer | Backup opens, steps written |
| 1 day | Tell your host to expect more crawling if the site is large | Developer | Reply 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.
| # | Step | Proof it worked |
|---|---|---|
| 1 | Publish last content changes to the new site | Latest posts present |
| 2 | Remove noindex and staging passwords, using your list | Crawl of tier A shows no noindex |
| 3 | Put the final robots.txt in place | File reads as planned |
| 4 | Point the domain at the new host, or turn on the new routes | DNS checked from several places |
| 5 | SSL works on every host version | No certificate warnings, on www and non-www |
| 6 | Turn on redirects | Tier A old URLs land on the right page by hand |
| 7 | Crawl your whole old URL list | Every row returns the expected 301, or 404 or 410, with no chains or loops |
| 8 | Crawl the new site | All 200, self-canonical, no internal redirects |
| 9 | URL Inspection on key pages in Search Console | Google can fetch them, with the expected canonical |
| 10 | Send every form on the live domain | Messages land where they should |
| 11 | Watch tracking in real time | Page views and events arrive |
| 12 | Check on a real phone, with no cache | Pages look right |
| 13 | Submit the new sitemap in Search Console | Status reads as submitted, and is read |
| 14 | If the domain changed: run Change of Address, on the old property | Tool confirms the request |
| 15 | Update ads, email footers, social profiles and link-in-bio pages | Each one clicked |
| 16 | Tell the team it is live, and how to report a problem | Message 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.
| Problem | Do this |
|---|---|
| A few wrong redirects | Fix them. Do not roll back. |
| One form or event not working | Fix fast. Point the form at a working inbox in the meantime. |
| Old URLs return 404 in bulk | Fix 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 fix | Roll back, if DNS is the only change so far. |
Whole site blocked by noindex or robots.txt | Fix 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.


