HTML guide

How to Add a Chatbot to a Website Using HTML

To add a chatbot to a website using HTML, copy the bot-specific script from PrimeWebKit's Widget tab, place it once before the closing body tag in the shared HTML template, deploy the page, and test the public URL.

Last updated: 2026-10-25

Before you start

This guide uses PrimeWebKit's standard website widget: one external script that loads the chatbot configured in your account. It does not install a native HTMLplugin or automatically connect your site's private data. The platform-specific steps below explain where the snippet belongs and what to verify before making a live change.

  • A published PrimeWebKit bot and its complete script from the Widget tab.
  • Access to the HTML file or shared template used to generate the pages you want to update.
  • A way to deploy the changed files to the same public site origin visitors use.
  • The public hostname allowed in the bot's domain settings if domain restrictions are enabled.

Installation steps

  1. 1. Find the shared HTML document template

    Editor or file path: Your site's source or hosting editor → shared page layout/template that contains </body>

    Use the repository or hosting tool that owns your site's HTML. The exact filename depends on how the site is built, so locate the shared document template rather than adding the snippet to one generated page at random. If every page is maintained separately, add it only to the pages where the widget should be available.

  2. 2. Paste the script before the closing body tag

    Editor or file path: Shared HTML template → immediately before </body>

    Add the full script copied from the bot's Widget tab just before the closing body tag. Keep the data-bot-id value as supplied. Place the script once in the template, not in both the shared layout and an individual page. The async attribute allows the external widget script to load without blocking parsing of the page.

  3. 3. Deploy and test the public page

    Editor or file path: Your site's normal build and deploy process → open the deployed URL

    Build or upload the changed site using its established deployment process. Open a deployed page in a private browser window, confirm the chat launcher appears, and send a test question that the bot's knowledge sources can answer. Test another page that shares the template to confirm placement is global.

Widget snippet

Copy the snippet from the selected bot's Widget tab whenever possible. The example below shows the format for your reference; replace the example identifier only with the bot ID from your own copied snippet.

<script     src="https://api.primewebkit.com/widget.js" data-bot-id="YOUR_BOT_ID" async></script>

Use the exact snippet copied from the Widget tab. YOUR_BOT_ID is explanatory placeholder text, not a working identifier.

Platform-specific notes

If the site uses a static-site generator, CMS, or framework, edit its source template rather than a generated output file that will be overwritten on the next build. Preserve existing script ordering and consent controls.

If the widget is not intended on every page, use the relevant page template instead of the global layout. Either way, ensure the script is included once per rendered document and only on domains where it is allowed to run.

Before publishing, review any site-wide consent banner, security policy, and domain restrictions already in place. Add the widget only to the pages and hostnames where it is intended to run, and avoid copying account secrets or private customer data into the page source.

Verify the chatbot is working

Test a published page, not just an editor preview. Confirm the launcher is visible, opens when activated, and accepts a question. Ask something answered by the bot's current knowledge sources, then check that an unrelated or unsupported question is handled within the limits of the bot's instructions.

Repeat the check on another page that shares the layout and on each hostname visitors use, such as a staging host and the production domain. If the bot is restricted to allowed domains, include the exact hostname for each environment before testing. Inspect the browser console and Network panel if the script or API request fails; record the specific error rather than changing unrelated settings.

Common problems

The widget does not appear

Confirm that the page was published with the script, the bot ID is correct, and the exact site hostname is allowed in the bot's domain settings. Check the browser console and Network panel for blocked or failed requests, then clear the site's page cache and test the public page again.

A cache or optimization tool serves an old page

Purge the relevant page, hosting, or CDN cache after publishing. Temporarily compare the public page in a private browser window and inspect its page source for the script before changing other settings. Avoid disabling all optimization or security features as a first step.

A content-security policy blocks the script

A CSP can prevent the browser from loading an external script or connecting to the widget service. Read the exact blocked origin in the browser console, then have the site administrator update only the applicable script-src or connect-src policy after verifying the required host. Do not use a wildcard policy as a workaround.

A builder or plugin changes the injected code

Some page builders, script managers, and cache plugins defer, rewrite, or sanitize custom code. Check the published HTML and console, confirm the tool supports external scripts in the chosen location, and remove duplicate copies before trying another injection point.

Frequently asked questions

Where do I get the HTML chatbot script?

Open the bot you want to publish in PrimeWebKit, go to its Widget tab, and copy the complete snippet shown there. Use that bot-specific script and ID rather than a placeholder or a snippet from another bot.

Can the chatbot appear on every HTML page?

Yes, when the script is added once to a shared site-wide layout or footer that is included on those pages. If you place it in a page-specific block or template, it may only appear on that page. Test more than one public page after publishing.

Do I need a HTML plugin?

No plugin is needed for a hand-built HTML page. Add the script to the source template that produces the pages where the chatbot should appear.

What should I check if the widget is missing?

Check that the latest page was published, the script and bot ID are present, and the tested hostname is allowed in the bot settings. Then inspect the browser console and Network panel for blocked or failed script requests and clear relevant caches.

Can a content-security policy block the chatbot?

Yes. A restrictive CSP may block the widget script or its network requests. Use the exact blocked origin reported by the browser and ask the site administrator to update the relevant policy narrowly; do not add wildcard permissions.

How do I avoid loading the widget twice?

Place the script in one shared insertion point only. Do not add a second copy in a page block, another theme file, or a script plugin if it is already in the global layout. Check the rendered page source when troubleshooting duplicate launchers.