{"id":6518,"date":"2026-11-20T17:20:00","date_gmt":"2026-11-20T17:20:00","guid":{"rendered":"https:\/\/www.cmsgalaxy.com\/blog\/?p=6518"},"modified":"2026-11-20T17:20:00","modified_gmt":"2026-11-20T17:20:00","slug":"website-launch-checklist-plan-backward-go-live","status":"publish","type":"post","link":"https:\/\/www.cmsgalaxy.com\/blog\/website-launch-checklist-plan-backward-go-live\/","title":{"rendered":"Website Launch Checklist: Plan Backward From Go-Live Day"},"content":{"rendered":"<p>Let&#8217;s be honest: most website launches don&#8217;t slip because of a big technical failure. They slip because somebody realised, three days out, that the copy for the services page was never written. If you have a go-live date and a pile of loose ends, this <strong>website launch checklist<\/strong> is built to be run backward. Begin on launch day, note what has to be finished one day earlier, then keep stepping back until you reach today. Bring a site map and something warm to drink, and we&#8217;ll begin.<\/p>\n<h2>Step one: set the go-live date and the hour<\/h2>\n<p>Pick a real day and time. Avoid Fridays if nobody will be around to fix things over the weekend, and avoid the morning of a big marketing email. Write the date at the top of your checklist. Everything below is counted from it.<\/p>\n<h2>Launch day checklist (T minus zero)<\/h2>\n<ul>\n<li>Switch DNS or publish the new theme at the agreed hour.<\/li>\n<li>Open the live site on a phone and a laptop and click through the main journey.<\/li>\n<li>Submit a contact form and confirm the message arrives.<\/li>\n<li>Check that the old pages redirect to their new addresses.<\/li>\n<li>Confirm analytics is recording a visit.<\/li>\n<\/ul>\n<p>That list is short on purpose. Anything you are still deciding on launch day is a sign that an earlier link in the chain was skipped.<\/p>\n<h2>The day before (T minus one)<\/h2>\n<p>This is the day for a final content freeze. Nobody edits copy, swaps images or tweaks the menu. Take a complete backup of the old site and the new one, and write down where each lives. Then check these items.<\/p>\n<ul>\n<li>All plugins and the core system are updated and the update is not scheduled to run tomorrow.<\/li>\n<li>The favicon, page titles and meta descriptions are filled in on every key page.<\/li>\n<li>The privacy and cookie notices are in place where your audience needs them.<\/li>\n<li>Someone other than the builder has the login details and knows the rollback steps.<\/li>\n<\/ul>\n<h2>One week before (T minus seven)<\/h2>\n<p>A week out is when you want the site working end to end on a staging copy. Test forms, search, checkout if you have one, and the login flow. This is also the moment to run a speed test and fix anything glaringly slow, such as oversized images. Page templates should look right at phone width, since that is how most visitors will see them.<\/p>\n<p>Content is the part that ruins plans, so audit it now. Open your page list and mark each one as final, draft or missing. Anything marked missing has to be assigned to a named person with a date. For ideas on which pages deserve the most care, try the piece on <a href=\"https:\/\/www.cmsgalaxy.com\/blog\/shaping-customer-perception-through-effective-homepage-design\/\">how homepage design shapes first impressions<\/a>, and the one on <a href=\"https:\/\/www.cmsgalaxy.com\/blog\/the-importance-of-the-about-us-page-in-building-online-trust\/\">why an About page matters for building trust online<\/a>.<\/p>\n<h2>Two to three weeks before<\/h2>\n<ul>\n<li>Finish the design and get sign-off from whoever has the final say.<\/li>\n<li>Write or collect all page copy and images, with credits and permissions noted.<\/li>\n<li>Draw up the redirect list: every old address and where it should now point.<\/li>\n<li>Decide who approves what, and by when, so feedback does not arrive on launch eve.<\/li>\n<\/ul>\n<h2>Four to six weeks before<\/h2>\n<p>This stretch covers decisions that take time to execute. Settle the site map and the navigation. Choose hosting and book any domain changes, because registrars and DNS providers can be slow. If your project needs a developer outside your team, this is the time to book them, since good people have calendars too.<\/p>\n<p>Many small businesses also use this window to line up the technical help they will lean on after launch. As one example of tidy site structure, <a href=\"https:\/\/cotocus.cn\/\">the site of a software and cloud engineering business<\/a> splits its pages into a services area, a products area, a training area and a blog, which can inspire how you name and order your own menu.<\/p>\n<h2>Find the first day you must start<\/h2>\n<p>Now read the checklist from the bottom up and add real durations. If design sign-off needs two weeks, copywriting needs two weeks, and the build needs three, and they cannot overlap much, the chain tells you how far back to begin. Write the latest start date in big letters. If it has already passed, choose between three options: move the launch, shrink the site, or add people.<\/p>\n<h2>A quick worked example<\/h2>\n<p>Say a local cafe wants its new site live on the first of the month. Counting back, the menu page and photos must be final by the twentieth, so the owner needs to hand over the text by the fifteenth. The builder needs about ten working days, which puts the start of the build in the first week of the previous month. The site map and hosting decisions sit before that. Laid out this way, the cafe owner sees that &#8220;we&#8217;ll start when things calm down&#8221; will not work, and that the real first task is choosing a hosting plan this week.<\/p>\n<p>Notice how much of that chain has nothing to do with code. In most small projects, the longest links are people: someone deciding, someone writing, someone approving. Put their dates on the chain first and the technical steps will fit around them.<\/p>\n<h3>Common ways this goes sideways<\/h3>\n<ul>\n<li><strong>Copy arrives last.<\/strong> Ask for it first; designing around placeholder text hides length problems.<\/li>\n<li><strong>Approvals go missing.<\/strong> Put approval dates on the chain, with names beside them.<\/li>\n<li><strong>Everything is tested once.<\/strong> Test again after the last content change, since small edits break things.<\/li>\n<li><strong>No rollback.<\/strong> A backup nobody has tried restoring is just a wish.<\/li>\n<\/ul>\n<h2>A word on testing windows<\/h2>\n<p>Teams often put testing in one block and call it done. A better habit is to schedule two passes with different goals. The first pass, about a week out, hunts for broken features and missing pages while there is still time to rebuild something. The second pass, on the day before, is a smoke test only: does the main journey still work after the final edits? Asking a friend who has never seen the site to buy, book or subscribe often turns up confusion that the builder can no longer see. Give that person a single task and watch where they hesitate.<\/p>\n<h2>Turn it into a shared document<\/h2>\n<p>Put the checklist in a shared sheet with four columns: item, owner, due date and status. Sort by due date every Monday morning. A five-minute scan will tell you whether the project is on its backward timeline or drifting off it. If it is drifting, make the call early, while moving a launch is still a polite email rather than an emergency.<\/p>\n<p>When launch day finally arrives and the list is mostly ticked, you will notice something pleasant. The day feels dull. Dull is the goal. The excitement belongs to the visitors who find a site that simply works.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A conversational website launch checklist counted backward from go-live: what to finish the day before, the week before, and the weeks that come earlier.<\/p>\n","protected":false},"author":14,"featured_media":6519,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1455],"tags":[],"class_list":["post-6518","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-development"],"_links":{"self":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6518","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/comments?post=6518"}],"version-history":[{"count":1,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6518\/revisions"}],"predecessor-version":[{"id":6523,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6518\/revisions\/6523"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media\/6519"}],"wp:attachment":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media?parent=6518"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/categories?post=6518"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/tags?post=6518"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}