Chatbot for Static Website Builds: Where the Embed Script Goes in Jekyll, Hugo, Eleventy or Plain Files, and Why a Deploy Is Needed (Free Decision Tree)

Chatbot for static website projects is a good match, because a static site has no server code to maintain and a chat widget is just one script. The catch is that a static site is rebuilt and cached, so an edit only shows after a build and a cache clear. This guide shows where the script goes for each setup, and the checks that confirm it is live.

1embed script, nothing to host
2websites on the free plan
100free visitors per site each month
0per-seat charges

⚡ In short

  • A static site has no backend, and the chat needs none: the script loads from livechatbot.in in the visitor’s browser.
  • Put the script in your shared layout if you use a generator, or in each HTML file if you do not.
  • Nothing changes live until you rebuild, upload and clear any CDN cache.
  • Check the decision tree below to find your own edit point.
Chatbot for static website in LiveChatBot: the chat reports dashboard with chats, visitors and top sources
How it looks in LiveChatBot: the chat reports dashboard with chats, visitors and top sources.

Fit

Why a chatbot for static website hosting works well

Static sites are fast and cheap because every page is already built. There is no PHP or database to run, which is also why some owners assume they cannot have live chat. They can. Chat is a browser feature, not a server one.

LiveChatBot loads from a script tag. The widget draws itself on your page, your team answers from the LiveChatBot inbox or the Android app, and visitors see replies in real time. Your static host never touches a message.

That has a nice side effect: you cannot break the chat by breaking your build, and the chat adds no work to your hosting. The things to get right are more mundane. You need one place to add the script, a rebuild, and a cache check. Everything else, such as colours, welcome text and opening hours, lives in the dashboard.

Where it goes

Three places to put the script on a chatbot for static website setups

Which edit point you use depends on how the site is made.

A static site generator

Tools such as Jekyll, Hugo and Eleventy build pages from templates. Add the script to the base layout or a footer partial, so every page that uses the layout gets it. In Jekyll that is typically a file in `_includes` or `_layouts`; in Hugo, a partial in `layouts/partials` called from the base template; in Eleventy, your base layout. Folder names vary by theme, so look for the file that prints the closing body tag.

Hand-written HTML files

Paste the script before the closing body tag in every page. For a handful of pages that is fine. For fifty, use find and replace across the folder and check the count.

A page builder export

If your tool exports a zip of HTML, add the script to the export’s custom code area if it has one, or edit the files after export. Re-adding it after every export is easy to forget.

Try it

Which edit point fits your site?

Follow the branch that matches how your pages are made.

How are your pages made?
↓
Generator with templates
↓
Edit the base layout or footer partial once
↓
Rebuild, deploy, test one page per template
A few hand-written files
↓
Paste the script before the closing body tag in each
↓
Upload, clear cache, test every file
Many HTML files
↓
Find and replace across the folder
↓
Count the matches against the file count
Exported from a builder
↓
Use the builder’s custom code box if it has one
↓
Re-check after every export

Deploy

Why your edit does not show up straight away

On a dynamic site, a saved edit is live at once. On a static site it is not. Three layers sit between your change and a visitor.

  1. The build. A generator must rebuild the pages. Editing a template without rebuilding changes nothing.
  2. The upload. Built files must reach your host. A deploy that fails halfway can leave some pages old and some new.
  3. The cache. A CDN or the browser may keep serving the old copy of each page. Clear the CDN cache after the deploy, then test in a private window.

If you see the script in your template but not in the live page source, work down that list. Nine times out of ten, the build or the cache is the reason, not the chat.

Testing

A five-minute test before you call it done

Open a private window and visit three pages: the home page, one deep page and a page that uses a different template, such as a blog post. On each, view the page source and search for livechatbot.in. If the script is on two of three, you found a template your edit missed.

Then send a test message from the widget. It should appear in your inbox, and if you installed the app, as a phone alert. Next, set opening hours and test the after-hours form, because a static site often runs unattended at night.

Finally, check the mobile view. A floating bubble should not cover a cookie banner or a sticky call-to-action button. The dashboard lets you change the widget position and hide it on chosen pages or devices.

Content

Giving a chatbot for static website pages good answers

A static site often has a small, stable set of pages, which makes it easy to teach a bot. Write down the ten or twenty questions people actually ask: prices, hours, delivery, how to book, refunds. Put the answers into the AI Agent as knowledge, and create matching saved replies so the free keyword bot can answer if the AI allowance runs out.

When your content changes, the chat does not update itself. A price change on your page needs a matching change in the knowledge you gave the bot. Add that step to whatever checklist you already use for publishing.

Keep the first version small

Do not try to cover every page on day one. Start with your three busiest pages, read the first fortnight of chats, and add replies for whatever people actually ask. Real questions beat guessed ones every time.

Proactive messages

For a first version, three proactive messages are enough. Use Flows to greet visitors on your pricing page, ask a question on a long article and offer help after several visits.

Limits

What it does not do

Say the gaps plainly so you can plan.

  • There is no generator plugin or theme. You edit a template or file.
  • The chat does not read your repository or rebuild anything. It cannot learn your pages by itself; you add the knowledge.
  • No WhatsApp inbox; a WhatsApp button card sends visitors to your number. The team app is Android only.
  • “Powered by LiveChatBot” stays on all plans.

If you want leads to land elsewhere, Zapier, webhooks for tickets and a REST API are available. See the integrations page. For a smaller walkthrough of plain pages, the guide to a free chatbot for an HTML website covers costs.

Frequently asked questions

Can I add a chatbot for static website hosting without a server?

Yes. The widget loads from livechatbot.in in the visitor’s browser, so your static host only serves the page.

Why do I not see the chat after editing my template?

A static site must be rebuilt, uploaded and cleared from any CDN cache before the change is live.

Is there a plugin for Jekyll, Hugo or Eleventy?

No. You add the embed script to a layout or partial yourself.

Does the bot learn from my pages automatically?

No. You give the AI Agent the knowledge it should use, and update it when your content changes.

What does it cost?

The free plan covers two websites and 100 free visitors per website each month, with no per-seat charges.

Keep reading

Related guides

📘

Chatbot for PHP Website Projects: Add One Footer Include, Cover Every Template and Pass the Logged-In User Safely (Free Template Audit Checklist)

Read the guide →

🧭

Chatbot for Laravel Website Owners: Add the Embed Script to Blade the Safe Way, With Config Caching, Logged-In Names and Test Routes (Free Copy-Ready Snippets)

Read the guide →

🛠️

Chatbot for Education Website: Which Questions to Automate, Which to Hand to Staff, and Which to Leave to Official Pages (Free Setup Quiz)

Read the guide →

Add chat to your static site

One script, no backend and a free plan for two websites. Start free on livechatbot.in.