How to add AI chat to a website without a developer

If you’ve ever pasted a video onto a page, you’ve already done this. An embed snippet is a short block of HTML — usually a single <script> tag — that tells the browser to load something from somewhere else and put it on the page. You don’t need to understand what’s inside it any more than you need to understand a video player.

For a chat assistant, that snippet typically renders a launcher button in a corner of the page and opens a panel when someone clicks it. Nothing about your site changes. You aren’t installing anything, there’s no plugin to keep updated, and removing it later is deleting the same lines you pasted.

This is why “without a developer” is a realistic ask, and also why the hard part of this project has nothing to do with the embed. The hard part is what the assistant knows.

The snippet needs to run on every page you want the assistant to appear on, which means putting it somewhere shared rather than pasting it page by page. Where that is depends on how your site was built:

• A site builder with a “custom code” or “head/footer code” setting. Most of them have one, usually under site settings. Paste it there once and it applies everywhere. This is the right option when it exists.
• A site builder with only an embed block. Drop the block onto a page and paste the snippet in. You’ll have to repeat it on each page you want it on, so start with the two or three that matter.
• A hand-written HTML site. Paste it just before the closing </body> tag of your template.
• A site you can’t edit at all. Skip the widget. Use a shareable link to the assistant on its own page and put that in your menu, your bio or your email signature — it works just as well and needs nothing from your site.

One caution: if your builder’s plan blocks custom HTML, no amount of instructions will make an embed work. Check that before you sign up for anything.

The mistake almost everyone makes is uploading everything they have and hoping. A better first pass takes an hour and produces a far more useful assistant.

Write down the ten questions you are actually asked most often — from your inbox, your chat log, your phone. Then find the documents that answer them, and start with those alone. Shipping-and-returns, what’s included, how to cancel, whether it works with X, opening hours, what happens after someone books. That’s usually three or four files, not thirty.

Once the common ten are answered well, add more. Working the other way round — uploading the archive and then discovering the answers are contradictory — is how people end up concluding the technology doesn’t work. There’s more on this in what to put in an AI knowledge base.

• Ask it your ten questions. Not paraphrased into the document’s own words — ask them the way a customer would, typos included.
• Ask it something you haven’t documented. The correct answer is a clear “I don’t have that”. If it invents a policy instead, do not put it on your site.
• Check a citation. Follow it to the page and confirm the answer really is there.
• Look at it on a phone. Specifically whether the launcher covers a cookie banner, a sticky cart, or your own call-to-action button.
• Check it matches your site. Name, logo and colours should be yours; a widget that visibly belongs to another brand undercuts the page it sits on.

With Ultranivo — ours, stated plainly — the snippet is copy-paste, the branding is a dashboard setting, and answers are cited to the exact page or video timestamp. The snippet also only loads on domains you allowlist, so someone copying it from your page source can’t run your assistant on their site. The builder page walks through the setup end to end.

A chat widget is not automatically an improvement, and it’s worth saying so on a page that would rather sell you one.

If your site has three pages and one of them is a price list, a visitor can already find everything in less time than opening a chat panel. If your most common question is genuinely urgent — a delivery gone missing, a booking today — people want a human and an assistant sitting between them and one is an obstacle. And if the answers aren’t written down anywhere, the widget has nothing to work with; write the page first.

Where it earns its place: sites with real depth — help centres, product manuals, policy libraries, course material, back catalogues — where the answer exists and nobody can find it. That’s the problem it genuinely solves.