Chatbot for HTML Website Rollout: Get One Snippet onto Every Page and Prove It Works on All of Them

Chatbot for HTML website projects looks easy until you remember a static site has no shared template: every page is its own file. The real job is making sure the snippet lands on all of them and stays there. This guide gives you a safe rollout, three ways to avoid missed pages, and a checklist to tick off as you go.

1script tag per page
โ‚น0free plan, 2 websites
100free visitors per site each month
0plugins needed

โšก In short

  • The chat is one script tag. The work is putting it on every page file, once, and checking each page.
  • Use a shared include, a find-and-replace or a build step so you never paste by hand twenty times.
  • Put the tag just before the closing body tag so it never blocks your content.
  • Prove it with a page list: open each URL on a phone and confirm the bubble appears.
Chatbot for html website in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them
How it looks in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them.

The problem

Why a plain site makes this harder than WordPress

A WordPress theme has one footer file, so one edit reaches every page. A hand-built site often has thirty separate files, each with its own footer. Miss one and visitors on that page see no chat, which is hard to notice because you rarely open every page.

The snippet itself is short. LiveChatBot gives you a single line that loads the widget and carries your website key. The same line on every page is exactly what you want, because the key tells the widget which website’s settings, team and visitor count to use.

What can go wrong

  • A page added later by someone who copied an old file.
  • A landing page built from a different template.
  • A copy of the site left in a staging folder that is counted as a second website.

A short rollout plan prevents all three.

Three ways

Three safe ways to add a chatbot for HTML website pages

1. A shared include

If your server supports includes (PHP include, server-side includes), put the snippet in a footer file and include it everywhere. Next time you change anything, you edit one file.

2. Find and replace across files

For a purely static folder, use your editor’s search across files. Search for the closing body tag, and replace it with the snippet followed by the closing body tag. Check the result in a copy of the folder first.

3. A build step

If you use a static site generator, add the snippet to the base layout. Every generated page gets it automatically. See our HTML snippet guide for where the line goes and the free chatbot for HTML site guide for the basics.

Whichever you pick, keep a backup copy before you start.

Try it

Your rollout checklist

Tick each step as you finish it. The bar shows how far through the rollout you are.

HTML rollout progress

Placement

Where the line goes in the page, and why

Put the script just before the closing body tag. The page content loads first, the chat appears a moment later, and nothing in your design waits for it. The script is marked async, so it does not block rendering.

Not in the head

Placing it in the head works, but it competes with your CSS and images during the first load. The body end is calmer.

Once per page

Two copies on one page means two bubbles or odd behaviour. If you use both an include and a hand-pasted copy, remove one. Our chat script troubleshooting guide covers the signs of a double install.

Mixed content

If your site runs on HTTPS, the script must also load over HTTPS. Use the snippet exactly as the dashboard gives it and do not change the address to plain HTTP.

Checking

How to prove the chatbot for HTML website pages is live everywhere

Do not trust memory. Make a plain list of every URL, then work through it.

The quick way

Open each page in a private browser window on your phone. The bubble should appear within a few seconds. Mark each URL as seen.

The thorough way

Right-click a page, choose view source and search for the widget address. If you find exactly one match, the page is covered. Do this for the handful of pages that differ from the rest, such as landing pages and the thank-you page.

Use Flows to confirm too

Set up a simple proactive message for one page with Flows, then open that page. If the message appears, both the script and your page rule work.

Maintenance

Keeping a chatbot for HTML website files in step over time

A static site changes by copying files, and that is how snippets go missing. Add one line to your own notes: every new page starts from the file that already has the chat snippet, never from an old copy.

When you redesign

Check the new layout carries the snippet before you switch over. It is easy to rebuild a footer and leave the script behind.

When you move host

Moving hosts changes nothing about the snippet, since it loads from LiveChatBot’s address. Do check that your new host does not cache old files, or strip scripts through a security rule. Repeat the page-by-page check after any move, and test on a phone as well as a laptop.

Extras

Small additions once the basics work

Because it is your own code, you can go a little further. The JavaScript API, window.LiveChatBot, offers open, close, show, hide, setVisitor, sendMessage, pageView and on. A common first use is a “Chat with us” link in your header that opens the chat.

You do not need those for a working site. Start with the plain snippet, then read our guide to live chat API snippets when you want a custom button. Use the dashboard’s “where it shows” settings first, because they are easier for the next person to find than code.

Honest gaps

What to know before you commit

  • The chat does not read your pages by itself. You give the AI Agent its knowledge, or write saved replies.
  • “Powered by LiveChatBot” stays on all plans.
  • There is no pre-chat form, no WhatsApp inbox and no iOS team app.
  • Free visitors are 100 per website each month. After that, chat pauses for new visitors until you buy a pack, with no automatic charge.

If those fit, a plain HTML site is among the easiest places to run it, since there is no plugin to update or conflict with. See pricing for packs.

Frequently asked questions

Do I need a plugin for a chatbot on a plain HTML site?

No. You paste one script tag into your pages. There is nothing to install on the server.

Can I add the chat to only some pages?

Yes. Either leave the tag off those files, or add it everywhere and use the dashboard’s where-it-shows settings to hide it on chosen pages.

Why is the chat missing on one page?

Usually that file was not updated, the old version is cached, or the tag sits outside the body. View source on that page and search for the widget address.

Does a chatbot for HTML website pages slow them down?

It loads asynchronously after your content, so it should not block the page. Test your page speed before and after.

Is it free?

The free plan covers two websites and 100 free new visitors per website each month. Visitor packs are one-time and never expire.

Keep reading

Related guides

๐Ÿ“˜

Free Chatbot for Webflow: What Stays Free, What Costs Money and What Webflow Itself Charges For

Read the guide โ†’

๐Ÿงญ

Chatbot for Custom Website Builds: Where the Script Goes in Your Templates, Which Environment Gets Which Key, and What Your Security Rules Must Allow

Read the guide โ†’

๐Ÿ› ๏ธ

Webflow Live Chat Widget: Seven Designer Mistakes to Avoid When You Add Chat to a Client Site (Free Mistake-vs-Better List)

Read the guide โ†’

Put chat on your HTML site

One snippet, a free plan for two websites and no per-seat charges. Start on livechatbot.in.