November 7, 2026

Live Chat Website Redesign Checklist: Keep the Widget Working

Live chat website redesign checklist: a before, during and after list beside a chat widget on a redesigned website

A live chat website redesign checklist is worth printing before the first mock-up is approved. Redesigns change templates, URLs, scripts, consent banners and page text, and every one of those can quietly break a chat widget that worked fine for years. The typical story is familiar: the new site goes live on Monday, the chat bubble is gone on half the pages by Tuesday, and on Thursday someone notices that nobody has answered a visitor for three days. This guide gives you a checklist for the weeks before, during and after a relaunch, so the widget keeps working and your assistant keeps answering from fresh pages.

Talkmio is an AI live chat for websites. Its assistant, Mio, reads your website, FAQ and uploaded documents and answers only from that content, and hands the conversation to your team when it cannot answer. That design makes a relaunch a double risk. The widget must be installed on the new templates, and Mio must read the new pages instead of the old ones. Both are easy to handle if you plan for them. The checklist below follows the usual stages of a site relaunch with redirects.

What Can Break When You Redesign

Before you start the checklist, know the failure modes. They are few, and almost all of them are about the snippet, the content or the paths.

Change in the redesign What can go wrong with the chat
New theme or templates The snippet lived in the old footer and is missing from the new one
New URLs Mio keeps old pages in its knowledge, and links in answers point to dead addresses
New domain or subdomain The new address is not added as a website in Talkmio
New consent banner or tag manager The script waits for consent or is blocked entirely
New security headers A content security policy blocks the widget script
New copy and prices The chat gives answers from old text until the pages are re-read
New checkout or app pages The bubble covers a button or appears where it should not

With these in mind, the live chat website redesign checklist is a matter of checking each row at the right moment.

Before the Redesign: Prepare

  1. Find your site key and your snippet. In Talkmio, open Websites and note the site key and the install snippet for the site you are redesigning. Save them with your project documents. If you use the WordPress plugin, note where the site key is entered, in Settings, Talkmio.
  2. List where the widget is installed. Is it in the theme footer, a plugin, a tag manager container or a custom template? You need to know before you replace it.
  3. Export what matters. From the Inbox, you can see conversation history and contacts. If you want to keep records, export or note what you need before any change. You can export or delete your data at any time by writing to [email protected].
  4. Collect the top questions. Read the last month of conversations and list the questions customers ask most. These become your test script after launch.
  5. Review the knowledge base. Open Mio AI, then Knowledge base, and list the sources: your website, single pages, question and answer pairs, free text and files. Decide which will still be valid after the redesign.
  6. Tell the project team. Add the chat widget to the launch requirements, so designers and developers treat it as a feature and not an afterthought.

During the Build: Staging and Testing

A staging site is the right place to find problems, with one caution: do not point Talkmio at it by accident. Test chats from a staging address land in the same Inbox as real ones, and staff may answer a test as if it were a customer.

  1. Decide how staging behaves. Either do not install the widget on staging, or install it and make sure the team knows that conversations from that address are tests. Our guide on adding live chat to WordPress shows how to keep the snippet in one place.
  2. Install the snippet in the new template. Put it just before the closing body tag of the layout that all public pages use, and nowhere else.
  3. Check consent and scripts. If the new consent banner or tag manager changes when scripts load, test that the widget appears at the right moment. Read our guide to chat widget cookies and consent before you configure it.
  4. Check placement. Open key pages on a phone and a laptop. The bubble must not cover the menu button, the cookie banner or the add-to-basket button. Our guide to live chat widget placement lists the checks.
  5. Check speed. A redesign often adds heavy images and scripts. Measure your key pages with the chat on and off and look at the difference before you decide to change anything.
  6. Check security headers. If the new site sends a content security policy, allow the widget script host from your snippet.

URLs and Redirects: Where Mio Reads

Mio reads every public page on the same domain and respects robots.txt. After a redesign, that means it will read the new site, provided the new address is public and not blocked. The risk lies in the old content. A knowledge base built from old pages can keep answers about products you no longer sell, or links to pages that no longer exist.

  • Keep redirects in place. Old addresses should redirect to the right new pages. Google explains how in its guide to a site move with URL changes. Redirects help visitors who follow old links in e-mails and answers.
  • Use the re-read option. Sources can be re-read on demand. After launch, re-read your website source so that Mio learns the new pages. Do it again after final text edits.
  • Remove obsolete single pages. If you added single pages or files that describe the old site, delete them from the knowledge base or replace them with new versions.
  • Check the question and answer pairs. Pairs written for the old site may mention old prices, names or processes. Review each one.
  • Add a new domain if it changed. If the site moves to a new domain, add the new website under Websites and install the snippet with its site key. Check that the old domain redirects and no longer shows a widget.

Our guide to AI chatbot knowledge base updates explains a routine for keeping sources current, which is useful long after the relaunch.

Launch Day: The Live Chat Website Redesign Checklist in Order

  1. Confirm that the snippet is present on the home page, a product page, a blog page, the contact page and the checkout. View the page source and look for the script tag.
  2. Open the site in a private browser window and check that the chat bubble appears and that the welcome text is correct.
  3. Ask Mio three real questions and check that the answers come from the new pages. Use Try Mio in the dashboard, which shows the answer, which knowledge pieces were used and how long it took.
  4. Test the hand-off. Write that you want to speak to a person, and confirm that the conversation arrives in the Inbox with the needs-human badge and that you get a browser notification. If you use the mobile app for iOS or Android, check the push notification.
  5. Reply from the Inbox and confirm that the visitor sees the answer.
  6. Check that your team members have the right status, Online, Away or Offline, and that business hours under Websites match reality.
  7. Re-read the website source, so that Mio reflects the final text.

Who Does What and When

A checklist without owners is a wish. Give each item to a named person, and put the dates into the project plan. A simple split works for most teams.

  • The developer or agency installs the snippet in the new templates, handles redirects, security headers and the tag manager, and confirms that the widget loads on every public page type.
  • The content owner reviews the knowledge base, edits question and answer pairs, uploads new files and presses re-read on launch day.
  • The support lead prepares the test questions, checks answers in Try Mio, tests the hand-off and watches the Inbox during the first days.
  • The project manager adds the chat to the launch checklist and makes sure that no one switches off the widget as a quick fix during a problem.

Plan the dates backwards from launch. Two weeks before, review the knowledge base and prepare the test script. One week before, test the snippet on staging. The day before, confirm redirects. On launch day, run the seven steps above in order. In the two weeks after, review hand-offs every morning. If a relaunch is planned for a busy season, add a few days of buffer, because a broken chat at the wrong time is expensive.

Small Details That Are Easy to Miss

A few details cause most of the surprises. The welcome text may mention a sale or a product that no longer exists, so reread it under Websites. The offline text may promise a reply time that your team no longer meets. The pre-chat form may ask for a field that the new design hides. Business hours may still reflect last year’s schedule. The widget language may be fixed to one language on a site that now serves several. Each of these is a setting that applies within five minutes of a change, so none of them should wait for a new release. Add them to your live chat website redesign checklist as a final pass, and tick them off with the support lead, who knows what customers see.

After the Launch: The First Two Weeks

Treat the first two weeks as an extended test. Read the conversations that Mio handed over, because they show where the new content leaves gaps. Check the Inbox filter Mio replied for answers that mention old names, old prices or broken links. Compare the numbers in the reports, conversations per day, the share Mio answered alone, hand-offs and first-reply time, with the weeks before the redesign. A sudden drop in conversations per day often means that the widget is missing from some pages. A sudden rise in hand-offs often means that Mio can no longer find what it used to.

Use Try Mio again with the question list you prepared. Ask the awkward ones too: “Where is my order?” should reach a person, and “How much is the premium plan?” should repeat the new price. If the redesign included a new 404 page, add a path to the chat on it, so lost visitors can ask for help. Our checklist for testing an AI chatbot before launch is a good companion.

Frequently Asked Questions

Do I need a new site key after a redesign?

Not if the website stays on the same domain. Keep the existing website in Talkmio and install the same snippet in the new templates. If the site moves to a new domain, add the new address under Websites, install its snippet and make sure the old domain no longer shows a widget.

How do I make Mio read the new pages?

Mio reads every public page on the same domain and respects robots.txt, and sources can be re-read on demand. After launch, use the re-read option on your website source, and again after final text edits. Then ask real questions in Try Mio to confirm the answers.

Will test chats from my staging site appear in the Inbox?

If the widget is installed on staging, test conversations land in the same Inbox as real ones. Either leave the widget off staging or tell your team to expect tests from that address. Do not point Mio at a staging site as a knowledge source.

What if my new consent banner blocks the chat?

Scripts that wait for consent will also hold the chat bubble until the visitor chooses. Decide how the widget should be classified in your consent tool, test the banner in a private window and check that the bubble appears after the right choice.

Can I keep my old conversations after a redesign?

A redesign does not delete conversations stored in your Talkmio account, because they belong to the account and not to the website templates. You can also export or delete your data at any time by writing to [email protected]. Check the Inbox before launch and note anything you want to keep.

How long should I monitor the chat after launch?

Watch it closely for the first two weeks. Read hand-offs, check answers that mention old names or prices, and compare reports with the weeks before the redesign. A drop in conversations per day often points to pages that lost the snippet.

The Bottom Line

A live chat website redesign checklist comes down to three jobs: keep the snippet in the new templates, make sure Mio reads the new pages and test the hand-off before the first customer does. Do the preparation before the build, test on staging without confusing your team, and re-read the website on launch day. Start free with Talkmio and keep your visitors’ questions answered while your website changes shape.


Try Talkmio on your site

Free plan, no card required.

Start free