Adding an AI chatbot to your website — one line, no developer
July 27, 2026 · 4 min read · by the hiy team
If you're searching "AI chatbot for my website," you've probably seen the same demo fifty times: a bubble opens, a bot says How can I help you today?, and nobody mentions what happens when it doesn't know the answer. Here's the practical checklist — what actually matters, what doesn't, and how the embed itself should behave.
What actually matters
It answers from your content, checkably. The whole point of a chatbot on your site is that it knows your stuff — your services, your policies, your writing. That means grounding with citations, not a general-purpose model with your name on it. Ask any vendor: can a visitor see the source behind an answer?
It fails honestly. Every chatbot eventually gets a question outside its material. The difference between an asset and a liability is that moment: a good one admits it, and either captures the visitor's email so you can reply, or tells them how to reach you. Nobody should dead-end.
It captures the lead with its context. "We got an email address" is table stakes. What you want is the email plus the question that prompted it — that's the difference between a list and a pipeline.
It doesn't tax your page. The embed should load nothing until a visitor actually opens it. Your Core Web Vitals shouldn't pay for a chatbot nobody clicked.
What doesn't matter as much as it looks
Avatar animations, 40-language auto-translation on day one, "GPT-5 inside" badges. If the bot invents your refund policy, it invents it beautifully in every language.
The one-line reality check
A modern embed is genuinely one line. hiy's, for example:
<script src="https://hiy.ai/embed.js" data-twin="you" data-mode="bubble" async></script>
Inline in the page or a floating bubble — either way it lazy-loads, answers with citations from your content, admits gaps, and hands you the follow-ups with context. (Embed docs here.)
Chatbot, or twin?
One more distinction worth making. If your site is a company's, you want a support-style bot: neutral voice, answers from docs, escalates to your inbox. If your site is yours — you're a coach, consultant, or creator — what you want is closer to an AI twin: it answers as you, in your voice, from your work. Same one-line embed, very different relationship with your visitors. hiy does both; try the twin kind live to feel the difference.