Chat for Websites Being Rebuilt: Keep Your Chat, Flows and Page Rules Working Through a Redesign or Platform Move (Free Rule Checker)

Chat for websites usually survives a redesign in the worst possible way: the bubble still appears, so everyone assumes it works, while the page rules behind it quietly stop matching anything. The pricing-page offer never fires, the chat pops up on checkout again, and the custom “Talk to us” button does nothing. This guide shows what to write down before a rebuild, where the code goes on the new platform, how to test on launch day, and a free tool that checks your old page rules against the new site’s addresses.

1 hourto list what your chat does today
7places a rebuild can break chat
15 minof launch-day checks
2 weeksof watching the inbox after

⚡ In short

  • A rebuild changes page addresses. Any chat rule that depends on an address can silently stop working.
  • Before the rebuild, write down every place your chat touches the site: the code, page rules, flows, links in replies and custom buttons.
  • Paste your rules and the new site’s page list into the checker below. Fix every rule that matches no page.
  • On launch day, run a 15-minute test on a phone and a laptop. Then watch the inbox for two weeks.
Chat for websites in LiveChatBot: the chat widget on an online store answering a delivery question
How it looks in LiveChatBot: the chat widget on an online store answering a delivery question.

The quiet failure

Why chat for websites breaks during a rebuild

When a website is redesigned or moved to a new platform, almost everything gets checked: the logo, the menu, the product photos, the payment page. The chat widget rarely makes the list, because it looks like a separate thing. It’s a small bubble in the corner, and as long as the bubble shows up, people tick it off.

The bubble is only the visible part. Behind it, a working chat setup usually depends on the site in several hidden ways:

  • Page rules. Flows that greet visitors on the pricing page, a hide-on list that keeps chat off checkout, a different welcome on product pages. Each one matches part of a page address. Change the addresses and the rules match nothing.
  • Links inside answers. Saved replies and AI answers often link to the returns page, the size chart or the booking page. After a rebuild those links can point to pages that no longer exist.
  • Custom buttons. A “Chat with us” button in the header or on the contact page that opens the chat through a small piece of code. Designers often rebuild the header and drop it.
  • Where the code sits. On the old site the chat code was in a theme file or a plugin. A new theme or platform doesn’t carry it over by itself.

None of these failures shows an error. Visitors simply stop getting the help you set up, and you only notice weeks later when enquiries feel slower. The rest of this guide is a plan to catch each one before or on launch day.

Plan

Four stages, from old site to new

BeforeWrite it down

List the code location, every page rule, every link in replies and every custom chat button on the old site.

DuringMap and rebuild

Get the new site’s page list. Run the rule checker. Add the chat code to the new theme or platform early, on the test version.

Launch dayTest in 15 minutes

Open the live site on a phone and a laptop. Check the bubble, each page rule, each custom button and one full chat.

AfterWatch for two weeks

Read the inbox and visitor pages daily. Fix links in replies and refresh what the AI Agent knows.

Before the rebuild

Write down everything your chat does today

Spend one hour on the old site before anyone touches it. You’re making an inventory, so that nothing depends on memory later. Open your chat dashboard and the old site side by side and note these seven things in a plain document:

  1. Where the chat code is installed. A WordPress or WooCommerce plugin, a Joomla extension, a snippet pasted into a theme file, a Shopify theme, a Wix or Squarespace custom-code box, or a React or Vue component. Write the exact place.
  2. Widget settings. Colour, position, team name, avatar, welcome text, attention grabber and widget cards. These live in your chat account, not the site, so they’ll survive, but note them in case the new design needs a different colour or corner.
  3. Page rules in Flows. Every flow with a page condition, and the page text it matches.
  4. Where the chat shows. Your hide-on pages, plus device and country settings.
  5. Links inside saved replies and widget cards. Any reply or card that points to a page on your site.
  6. What the AI Agent was taught. Any knowledge you wrote that mentions page names or links.
  7. Custom chat buttons and code. Buttons or links that open the chat, ask a question or pass a logged-in name using the JavaScript API.

In LiveChatBot the first six are on screens you can read in a few minutes: the widget settings, the Flows list, “where it shows”, saved replies and the AI Agent’s knowledge. The seventh is on the site itself, so ask whoever built it, or search the old theme for “LiveChatBot”.

This inventory also helps if you hand the rebuild to an agency. Give them the list and ask them to confirm each item on the new site.

During the rebuild

Put the chat code on the new platform early

The most common mistake with chat for websites under rebuild is adding the code on launch day, in a rush, after everything else. Add it as soon as the new site has a working page, so it gets tested along with everything else.

Where it goes depends on the new platform:

  • WordPress or WooCommerce. Install the WordPress plugin on the new site and connect it. If the old site used a pasted snippet, remove that so the chat doesn’t load twice.
  • Shopify. There’s no Shopify app; paste the code into your theme so it loads on every page. See the Shopify guide.
  • Wix or Squarespace. Paste the code into the site-wide custom code area. See Wix and Squarespace.
  • Plain HTML or a custom build. Paste the code just before the closing body tag on every page, usually in a shared footer file. Our HTML guide shows where.
  • React or Vue. Use the plugin for your framework so the chat survives page changes without a full reload.

If the new version is being built on a separate test address, think about where test chats will land. On the free plan you get two websites per account. If one slot is spare, you can add the test site as its own website, so test chats don’t mix into your real inbox. Testers count as visitors, so keep testing to a small group.

When you switch the new site live, make sure the chat code is on the live version, not only on the test one, and that the old snippet isn’t still sitting in a shared header somewhere.

Free tool

Check your old page rules against the new site

Paste each rule you noted, then the page addresses from the new site. The checker shows which rules will stop matching, which now match far too much, and the closest new page for each broken rule.

1. Your chat’s page rules today, one per line as name | page address or part of it. Include flows with a page condition, hide-on pages and any page-specific welcome.

2. Page addresses on the new site, one per line. Copy them from the new sitemap, menu or page list. Full links or paths both work.

Runs only in your browser; nothing is sent or saved. Matching is a simple “address contains this text” check, the way most page rules work.

Reading the results

How to fix each kind of broken rule

The checker sorts your rules into three groups. Here’s what to do with each.

Matches no new page

This is the quiet failure. The rule still exists in your dashboard but will never fire. In the example, “/pricing” became “/pages/wholesale-prices”, “/product/” became “/products/”, and “/contact-us” became “/pages/contact”. Each looks like a small change, and each would silently switch off a flow.

The fix is to edit the rule so it matches a part of the new address. Use the shortest piece that is unique to that page or that group of pages. “/products/” is a better rule than one product’s full address, because it covers every product page, including ones you add next month.

If the checker finds no similar page, the page may simply be gone. Decide whether the rule still has a job. If the old site had a “/offers” page and the new one doesn’t, delete the flow rather than leave a rule that will never run.

Matches most of the site

A rule meant for one page that now matches most addresses will greet visitors everywhere. This happens when a new platform puts a common word in every address, such as “/pages/” or “/shop/”. Make the rule more specific. Rules that are meant to match everything, like “/”, are skipped by this warning.

Still matching

Good, but glance at the pages listed. A rule might still match, but now match a different page than you intended.

Below the groups, the checker lists new pages that no specific rule touches. Most will be fine. Look for new pages that deserve their own greeting, like a new booking page, or that should hide the chat, like a new payment step. Our guide to showing chat on specific pages covers the settings.

Examples

Old rule, new site, better rule

Product page greeting
🚩 Instead ofKeep “/product/”, which matches nothing after a move to Shopify, where product addresses start with “/products/”.
✅ Do thisChange it to “/products/” so every product page, old and new, gets the greeting.
Hide chat on checkout
🚩 Instead ofAssume checkout is hidden because the rule still exists.
✅ Do thisCheck that the new checkout address still contains “/checkout”, then test it in a private browser window.
Pricing page offer
🚩 Instead ofLeave “/pricing” in place after the page was renamed “/pages/wholesale-prices”.
✅ Do thisUse “wholesale-prices”, the part that’s unique to the new page.
Blog stays quiet
🚩 Instead ofKeep “/blog/” when the new platform uses “/blogs/news/”.
✅ Do thisUse “/blogs/”, which covers every post on the new site.

Launch day

A 15-minute test of chat for websites going live

On the day the new site goes live, run this test yourself. Don’t rely on the developer’s word, because they’ll test on their own browser, often logged in, with a fast connection.

Use two devices: your phone on mobile data and a laptop in a private browser window, so you see what a first-time visitor sees.

  1. The bubble. Open the home page. Does the chat appear in the right corner, in your colours, without covering the new cookie banner or a sticky “Buy” button?
  2. One full chat. Send a message from the phone. Check it reaches the inbox and the Android app, and that your reply comes back to the phone.
  3. Each page rule. Visit the pricing, product and contact pages. Wait for each flow. Visit checkout and confirm the chat is hidden.
  4. Custom buttons. Click every “Chat with us” button or link. Each should open the chat.
  5. Out-of-hours. If your opening hours are set, check the away form appears outside them.
  6. Speed. Load a product page on the phone. If the page feels slower than before, check whether the chat code is loading twice.

Anything that fails goes straight back to whoever built the site, with the page address and a screenshot. A missing chat button or a duplicate snippet is a five-minute fix on launch day and a month of lost enquiries if nobody notices. Our separate post on chat and site speed covers what a widget does and doesn’t do to page loading.

Checklist

Rebuild-proof chat

Rebuild progress

After launch

The first two weeks: fix what visitors trip over

A new site changes what visitors ask. They can’t find the size chart because it moved; the new menu hides the delivery page; a broken link in an old email sends them to an error page. Chat is where those problems show up first, so for two weeks, read every chat with that in mind.

Read the pages visitors were on. Visitor tracking shows the page a visitor was viewing when they started a chat. If several people ask “where is the return policy?” from the same page, the problem is the page, not the chat.

Fix links inside replies. Go through every saved reply and widget card that has a link and open each one. Replace old addresses with new ones. Our guide to saved replies shows where to edit them.

Refresh the AI Agent’s knowledge. If the AI Agent learned answers that mention page names, links, or menu paths like “go to Shop, then Offers”, update them to match the new site. An AI answer that confidently sends a visitor to a page that’s gone is worse than no answer. See training your AI chatbot.

Recheck flows with real traffic. After a week, look at whether each page flow is starting chats the way it did on the old site. A flow that used to bring a few chats a week and now brings none is worth a second look at its rule.

Tell your team. Anyone answering chats needs to know the new page names and menu, or they’ll send customers to places that no longer exist. A one-page note with old name, new name and new address is enough.

Getting started

Start your inventory today

If a redesign is planned, open your chat dashboard now and list your rules, links and buttons. When the new page list arrives, paste both into the checker above and fix every rule that matches nothing before launch. If you haven’t added chat yet, the new site is the best time to do it, because it gets tested along with everything else. Our setup guide covers the first install.

LiveChatBot’s free plan includes the widget, Flows with page conditions, “where it shows” settings, saved replies, the inbox, the Android app, visitor tracking and an AI Agent with a small free monthly allowance, for two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.

Frequently asked questions

Will my chat history and settings survive if I rebuild my site?

Yes. Your chats, saved replies, flows and widget settings live in your chat account, not on the website. What a rebuild can break is the code on the site and any rule or link that depends on page addresses.

Do I need a new chat account when I move to a new platform?

No. Keep the same account and website, and add the same chat code or plugin to the new platform. Remove the old snippet so the chat doesn’t load twice.

Why does chat for websites stop greeting visitors after a redesign?

Usually because page rules match part of the old page addresses. When the addresses change, the rules match nothing. Paste your rules and the new page list into the checker above to find them.

Can I test the chat on the new site before it goes live?

Yes. Add the chat code to the test version early. If you have a spare website slot, add the test site separately so test chats stay out of your real inbox, and keep testing to a small group.

Does the rule checker send my site addresses anywhere?

No. It runs entirely in your browser, and nothing is sent or saved.

Keep reading

Related guides

📘

Chat Box for Website Briefs: What to Send Your Web Developer So It’s Added Right the First Time (Free Brief Builder)

Read the guide →

🧭

Chat Bot Services You Can Sell: How Web Designers and Agencies Package, Price and Deliver Bot Setup for Clients (Free Package Pricer)

Read the guide →

🛠️

Chat Widget Settings, One by One: What Every Option Does and the Value to Pick

Read the guide →

Keep your chat working through the rebuild

Page rules, saved replies and the AI Agent all stay in your account while the site changes around them. Start free on livechatbot.in.