Last reviewed November 2026.
Short answer
A website redesign launch checklist is a short list of checks you run on the day the new site replaces the old one. Back up both sites, switch, remove the search block, test redirects, forms and tracking, submit the sitemap, and have a rollback plan ready. Run the checks in order and give each one an owner.
Launch day should be boring. The work is done, and you are now confirming that it still works on the real address. This guide gives you a run sheet for that day, with a clock, an owner for each step, and a plan for when something breaks.
This guide is part of our website redesign guide.
In this guide
- What launch day means
- Before you start: the go or no-go list
- A launch day run sheet
- The 12 launch day checks
- Who owns each check
- How to test the things that break most
- A made-up example: a form that fails for a week
- Fix, wait or roll back?
- The first 48 hours after launch
- Central PA notes
- Common mistakes
- Frequently asked questions
- Next steps
What launch day means
Launch day is the moment your new site goes live at your real web address. Visitors who type your domain, click a Google result or tap a saved link now see the new site.
A few terms help here:
- Staging site. A private copy where the new site was built and tested. It is usually set to stay out of search results.
- DNS. The system that tells browsers which server holds your site. Changing it is how many launches switch from old to new.
- TTL. Short for time to live. Cloudflare’s DNS documentation defines it as a field on DNS records that controls how long each record is cached. A longer TTL means changes take longer to reach people.
- Redirect. An instruction that sends a visitor from an old address to a new one. A permanent redirect tells Google the move is for good.
- Rollback. Putting the old site back because the new one has a serious problem.
This post covers the day itself. If you are still planning, start with our website redesign checklist. If you are changing hosts or platforms, read the website migration guide. For traffic and rankings after launch, see what to monitor after a website redesign.
Before you start: the go or no-go list
Do not start the clock until you can answer yes to each row. A delayed launch costs little. A rushed one can cost weeks of calls.
| Question | Yes means | If no |
|---|---|---|
| Is the new site finished and approved in writing? | No surprise changes mid-launch | Move the date |
| Is the redirect list complete? | Old pages will land on the right new pages | Finish it first |
| Do you have backups of both sites, stored off the server? | You can go back | Take them before you begin |
| Can someone log in to your domain and DNS settings today? | The switch will not stall | Find the login first |
| Has content been read for old phone numbers, addresses and typos? | No embarrassing errors | Proofread again |
| Is your developer reachable for several hours? | Problems get fixed fast | Pick another time |
| Do you know who will answer the phone and check forms? | Leads are caught | Assign a person |
Not sure the new site is ready? Run our free Website Teardown on the staging or live address. It shows what a visitor sees and where it falls short.
A launch day run sheet
Use this as a template. Times are examples. Shift them to fit your day. The redirects and the search-block removal go live with the switch, so old addresses never land on an error page. The times after the switch are for testing.
| Time | What happens | Owner |
|---|---|---|
| 8:00 am | Confirm everyone is online. Take both backups. | Developer |
| 9:00 am | Switch the live site to the new one, with redirects on and the search block off. | Developer |
| 9:15 am | Confirm the search block is gone. Check HTTPS. Test a sample of redirects. | Developer, then you verify |
| 10:30 am | Test forms, phone links and tracking on real phones. | You |
| 11:30 am | Click through the whole site on phone and desktop. | You and one other person |
| 12:30 pm | Go or rollback decision. | You |
| 1:00 pm | Submit the sitemap. Update outside listings. | You or SEO |
| 4:00 pm | Second look at calls, forms and errors. | You |
Notice the rollback decision sits at midday. That leaves the afternoon to restore the old site if you have to. Decide that rule before you start, not in the heat of the moment.
The 12 launch day checks
1. Back up the old site
Take a full backup of files and database. Store it somewhere other than the web server. Also save the old sitemap and a list of old page addresses. You will need them to check redirects.
2. Back up the new site
Back up the finished staging site too. If launch trouble hits, you want a known good version to restore.
3. Switch the live site to the new one
How this works depends on your setup. It might mean moving files, pointing your domain to a new host, or changing which version is live. Have the person doing it write down each step and the time. Do not improvise.
If the switch involves DNS, ask your developer to lower the TTL a day or two ahead. A shorter TTL means the change reaches people sooner, and a rollback does too.
4. Remove the block that hides the site from search
Staging sites are usually set to stay out of search. If that setting travels to the live site, the new site is told to stay hidden. Check three places:
- The WordPress setting “Discourage search engines from indexing this site.” WordPress Reading settings says it adds a noindex, nofollow tag to your pages, and that it is up to search engines to honor the request.
- The robots.txt file at yoursite.com/robots.txt. Look for a line that says “Disallow: /”.
- Any noindex tag in your page code or SEO plugin. Google’s noindex guide explains that a noindex tag goes in the page head.
Google’s site move guide puts it plainly: “Don’t forget to remove any noindex or robots.txt blocks that were only needed for the migration.” This check takes about a minute, and skipping it can hide your whole site.
5. Turn on the redirects
Redirects should be live at the moment of the switch, not after it. Otherwise every changed address shows an error page until they are on.
Each old address that changed should now go to its new page in one step. Google’s redirect guide says to use permanent redirects when you are sure the redirect will not be reverted. Test your top pages, a few blog posts and a few pages you removed. Check that:
- Each goes to the closest matching page, not always the home page.
- There is no chain of redirects, and no loop.
- The final page loads with no error.
Google’s site move guide says to keep redirects as long as possible, generally at least one year.
6. Confirm HTTPS
Open the home page and several inner pages. Look for the padlock and for warnings. Check that the “http” and “www” versions all end up at your one preferred address.
7. Check canonical tags and page titles
A canonical tag names the main address for a page. On the live site, it must point to the live address, not to staging or the old site. Check a handful of key pages. Titles and descriptions should also match your plan, especially on pages that already bring in visitors.
8. Test every form and phone link
Do this on the live address, from a real phone. Settings that worked on staging sometimes fail after the switch, especially email delivery.
9. Confirm tracking
Open the Google Analytics Realtime report. It displays user activity during the last 30 minutes. Visit your site and make sure you appear. Then submit a test form and tap a phone number, and confirm both are recorded. If you run ads, confirm ad tags and call tracking still fire.
10. Submit the new sitemap
In Google Search Console, submit the new sitemap. Google says to do this in its site move guide. Know the limit, though. Google’s sitemap guide says submitting a sitemap is merely a hint. It helps, but it is not a command.
11. Click through the whole site
Spend twenty minutes as a visitor on a phone, then on a desktop. Use the menu, the footer, the service pages and the form pages. Look for broken images, missing pages, odd layouts and old text. Write each problem down with its address.
12. Update your outside listings
Check your Google Business Profile, social profiles and main directories. If your web address changed, update the link. Confirm your name, address and phone number match the new site.
Do this today: open your staging site and your current robots.txt. Write down the exact setting or line that hides staging from search. On launch day, that is the first thing you will look for.
Who owns each check
A check with no owner does not get done. Print this table or copy it into a shared document.

| Check | Who runs it | Who verifies |
|---|---|---|
| 1 and 2. Backups | Developer | You |
| 3. Switch | Developer | You |
| 4. Search block | Developer | You, with the steps below |
| 5. Redirects | Developer | You |
| 6. HTTPS | Developer | You |
| 7. Canonicals and titles | Developer or SEO | SEO or you |
| 8. Forms and phones | You | You |
| 9. Tracking | Developer | You |
| 10. Sitemap | You or SEO | You |
| 11. Click-through | You and a second person | You |
| 12. Outside listings | You | You |
If you do not have a developer on call, that is a sign to book help for launch day. You can also start with the free Website Teardown.
How to test the things that break most
You do not need special tools for these. You need fifteen minutes and a phone.
Test steps for the search block
- Open yoursite.com/robots.txt in a browser. Look for “Disallow: /”. If you see it, tell your developer right away.
- Right-click a live page and choose “View page source.” Search for “noindex”. You should find nothing.
- In Google Search Console, paste a page address into the URL Inspection tool and choose “Test live URL.” Google says this fetches and examines the page in real time. Check whether indexing is allowed. One caveat: Google says that if robots.txt blocks a page, the “Indexing allowed?” field always reads “Yes,” because Google cannot see a noindex tag on a page it may not crawl. So always do step 1 first, and treat this step as a second look, not an all-clear.
Test steps for forms
- Fill in each form with your own name and a real email address.
- Confirm you see a thank-you message.
- Confirm the message arrives in the right inbox. Check spam too.
- Reply to it, to confirm replies go to you.
- Repeat on a phone using mobile data, not Wi-Fi.
Test steps for redirects
- Open your saved list of old addresses.
- Paste ten of them into your browser, starting with your most visited pages.
- Note where each lands. It should be the closest matching new page.
- Try two addresses for pages you deleted. They should go to a useful page or show a helpful “not found” page.
Want more on redirects and rankings? See how to redesign a website without losing SEO.
A made-up example: a form that fails for a week
This example is made up. The numbers are round and are not from a real client. It shows why the form test matters.
Picture a small landscaping company in Carlisle. Before the redesign, its form sent about 8 quote requests a week. One in four of those requests became a job worth $600 in gross profit.
| Step | Made-up figure | Math |
|---|---|---|
| Quote requests per week | 8 | Assumed |
| Jobs won per week | 2 | 8 × 0.25 |
| Gross profit per week | $1,200 | 2 × $600 |
| Weeks the form is broken | 1 | Nobody tested it on launch day |
| Gross profit at risk | $1,200 | $1,200 × 1 week |
Some people would call again, so the loss may be lower. But some would not, and nobody would know who they were. Compare that with the cost of the test: about five minutes on launch day.
Planning a redesign? We redesign WordPress sites for local businesses. See our website redesign service.
Fix, wait or roll back?
Problems will show up. The goal is to sort them by how much they hurt customers.
| Problem | Example | What to do |
|---|---|---|
| Customers cannot reach you | Form fails, phone link wrong, site will not load | Fix now. Roll back if not fixed within your time limit. |
| Search is blocked | Noindex tag or robots.txt block still on | Fix now. It is quick. |
| Pages lead to errors | Redirects missing or looping | Fix the top pages first. Then work down the list. |
| Look or layout problems | A misaligned image on one page | Log it. Fix this week. |
| Slow to appear in Google | New pages not yet in results | Wait. Google’s site move guide says a move can take a few weeks or more. |
Log every problem, who found it and when it was fixed. That record helps if rankings or leads shift later. If they do, read what to do if website traffic dropped after a redesign.
The first 48 hours after launch
- Check calls and forms twice a day. Compare with a normal two days before launch.
- Check the Search Console Pages report for new errors.
- Ask staff to report oddities. They see problems before you do.
- Keep the old backup. Delete nothing yet.
- Do not make big content changes. If you change many things at once, you cannot tell what caused a shift.
After that, move to a slower rhythm. Our guide on what to monitor after a redesign covers weeks one through twelve.

Central PA notes
Local businesses have a few extra checks.
- Pick a quiet day for your trade. A snow-removal company should not launch in January. A landscaper should not launch the week of a spring rush.
- Your phone is your form. If most of your leads call, test the phone link and call tracking more than anything else.
- Match your Google Business Profile. Your name, address, phone and web address should match the new site.
- Check town and service pages. If you have pages for Carlisle, Mechanicsburg, Harrisburg or other towns, make sure each one redirected correctly.
To see how your pages look to a visitor, run the free Website Teardown.
Common mistakes
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| Launching on a Friday afternoon | Problems wait through the weekend | Launch early in the week, in the morning |
| Leaving the staging block on | Search engines are told to skip the new site | Check WordPress settings, robots.txt and noindex tags |
| Testing forms only on staging | Email settings often change after the switch | Test on the live address |
| Redirecting everything to the home page | Visitors and Google lose the match | Send each page to its closest match |
| Skipping the backup | You cannot go back | Back up both sites first |
| No owner for each step | Steps get missed | Name an owner for every check |
| Changing a lot after launch | You cannot see what caused a change | Hold content changes for two weeks |
| Forgetting outside listings | Customers land on dead links | Update Google Business Profile and directories |
Frequently asked questions
What should I check on launch day for a website redesign?
Check twelve things in order: backups, the switch itself, the search block, redirects, HTTPS, canonical tags and titles, forms and phone links, tracking, the sitemap, a full click-through, and your outside listings. Test the search block and the forms early, because a failure in either one is easy to miss and hurts the site.
What is the best day and time to launch a website?
Pick a weekday morning when your developer and your staff are both reachable for several hours. Avoid Fridays, holidays and your busiest week. A launch early in the week leaves time to fix problems while people are at their desks. There is no perfect hour for every business, so choose when you can watch calls and forms.
How long does a website launch take?
The switch itself can take an hour or less. The checks and fixes usually fill the rest of the day. DNS changes can take longer to reach everyone, because each record is cached for a set time, called its TTL. Plan for a full day of watching, then a closer look for the next two weeks.
Should I take my old site down before launching the new one?
No. Keep the old site and its backup safe until the new site passes your checks. The new site takes the old one’s place in one step. If something goes wrong, you can go back. Delete nothing for at least a few weeks. Old pages that moved need permanent redirects, not deletion.
Why is my new website not showing up on Google?
One thing to rule out first is a leftover block from staging, such as a noindex tag or the WordPress setting that discourages search engines. Google also needs time to find new pages. Google says a site move can take a few weeks or more to settle. Check for the block first, then submit your sitemap.
Do I need to submit my sitemap to Google after launch?
It is a good step, but it is only a hint. Google says submitting a sitemap is merely a hint, and it may not use it. A sitemap helps Google find your new pages sooner. Submit the new one in Search Console, then remove the old one if it no longer applies.
When should I roll back a launch?
Roll back when a problem stops customers from reaching you and you cannot fix it fast. Examples are forms that fail, a phone number that does not dial, or pages that will not load. Set a time limit before launch, such as one hour. If the fix is not in by then, restore the old site and try again.
Who should be on the launch team?
You need three roles: someone who runs the technical switch, someone who tests as a customer, and someone who approves. In a small business, you may be the tester and the approver. Name each person before launch day. Write down who can change the domain settings and make sure that person is reachable.
Next steps
Here is the short version. Run the go or no-go list. Name an owner for each check. Test forms, phones and the search block on the live site. Decide your rollback rule before you begin.
Not sure where your site stands? Start with the free Website Teardown to see where your site stands.
Keep reading
- website redesign guide
- After a Website Redesign: What to Monitor: the first 90 days.
- Redesign a Website Without Losing SEO: the redirect and ranking plan.
- Website Migration: moving host, platform or domain.
- website redesign service



