To add an AI chatbot to your website, load your own pages into it, tell it what it must never promise, test it on real customer questions in a copy visitors cannot see, then paste one script tag into your site's footer. Most small businesses can do it in an afternoon, without code.
Key takeaways
- A website chatbot is not retrained on your site. It reads your pages into a knowledge base and answers from the passages that match each question.
- Never skip testing in a separate copy before anyone sees it. Ask your 20 most common questions there first.
- Installing is one
<script>tag. On WordPress, Wix, Squarespace, Shopify and Webflow it goes in a footer or custom-code setting. - Decide where leads go before launch: an inbox, your email or your CRM.
- Paid plans with AI replies included start at $10 a month.
Why visitors expect to ask
More visitors now expect to type a question instead of hunting for a page. In a Pew Research Center survey of 5,123 U.S. adults (February 24 to March 2, 2025), 34% said they had used ChatGPT, and 58% of adults under 30 had. 26% had used it to learn something new, up from 8% in March 2023. A visitor used to asking a chatbot will try the same on your site, and the answer should come from your pages, not a guess.
How to add an AI chatbot to your website: the short answer
- Give it your content. Your website first, then PDFs, price lists and FAQs.
- Tell it who it serves, and the promises it must never make.
- Test it before anyone sees it, with real questions, in a test copy.
- Put it on your site with one script tag.
- Decide where leads go, so a captured phone number reaches a person the same day.
What you need before you start
- Your website address, and the pages that matter most: services, prices, hours, location, booking and policies.
- Your top 20 customer questions, in your customers' words, from your inbox, phone notes, reviews and DMs. They become your test set in Step 3.
- A lead inbox: the email or CRM where a new enquiry should land, and the person who answers it.
Step 1: Give the assistant your content
In Rylvo, a new workspace starts by pasting your website. Rylvo reads the site and builds the agent from it, so the first answer you see comes from your own pages.
Paste your website
The website reader starts from the address you give it and follows links on your own domain. It respects your site's robots.txt file (the standard is RFC 9309), so pages you have asked crawlers to skip stay out. When you paste your website, Rylvo reads up to 40 pages, two links deep, and re-reads the site daily. A Web Crawl source you add yourself in the knowledge base starts at two levels and 50 pages, and there you can add more start addresses, change both limits and allow extra domains.
Two limits to plan for:
- It reaches unlinked pages only through your sitemap, and only within the page limit. The reader follows links first, then fills any remaining page budget from your sitemap (the one
robots.txtnames, or/sitemap.xml). If an important page is in neither, or the limit is reached first, add its address as a start URL. - It does not log in. Pages behind a customer login are not read. Add that content as a document instead, if it is safe to share with visitors.
Add PDFs, docs and FAQs
A menu PDF or price sheet often answers more questions than the homepage. Rylvo's knowledge base accepts 16 kinds of source, from file uploads and a web crawl to Google Drive, Notion, Confluence, SharePoint, Zendesk, Intercom and databases. Uploads can be PDF, Word, PowerPoint, Excel, CSV, plain text, Markdown, HTML, JSON, XML or YAML. Images are read with text recognition (OCR).
Free holds 1 knowledge source with uploads up to 10 MB, and Starter holds 5 sources with uploads up to 25 MB. A source can sync on a schedule, so when you change a page the answers follow.
For more, read how to train an AI chatbot on your website and documents.
Step 2: Tell it who it serves
Rylvo's onboarding asks four questions, one tap each, and you can skip any of them:
| Question | What it decides | Example answer |
|---|---|---|
| Who it's for | Your customers, a team at your company, or your own app | My own business |
| Industry | Which template and which questions it should expect | Dental or clinic |
| Its job | Answer questions, book appointments, qualify leads, and more | Answer customer questions |
| Where it talks | The channels it starts on | Website and a shareable link |
After that, open the agent's instructions and add three things in plain sentences:
- Tone. "Warm and brief. Two or three sentences unless the visitor asks for detail."
- The never list. "Never quote a price that is not on the pricing page. Never promise an appointment time; offer to take details instead. Never give medical advice."
- The I-don't-know path. "If the answer is not in your knowledge, say so, and offer to pass the question to the team with the visitor's name and email."
The last one matters most: without it, the assistant guesses. For one regulated field, the dental practices page shows a careful setup.
Step 3: Test it before anyone sees it
Every Rylvo workspace has two copies of its agents: Test, where you edit and try things, and Production, which customers talk to. Production changes only when an admin activates a release, and any earlier release can be made live again. The environments page lists what a release includes, and Test vs Production explains why the split matters.
With the environment switch on Test, chat with the agent in your dashboard and ask your 20 questions. Check that each answer is correct, comes from your content and respects your never list.
| Question | Test, before a fix | Test, after a fix | Production |
|---|---|---|---|
| "Do you take my insurance?" | Guesses "yes" | "Our insurance page lists ... Call us to confirm your plan." | Unchanged until you release |
| "Can I come in at 6pm Friday?" | Promises a slot | Gives hours, offers to take details | Unchanged until you release |
| "How much is whitening?" | Quotes an old blog price | Quotes the pricing page, or says to ask | Unchanged until you release |
Save the questions that failed as test cases, so you can rerun them after every change. Every plan includes scripted tests: Free allows 5 test cases per bot and Starter 10. The full pre-launch routine, including the adversarial questions worth asking, is in how to test an AI chatbot before launch.
Step 4: Put it on your site
When the answers hold up, Go live publishes the agent. You get a shareable Beam link and a QR code straight away. If you built the agent from your website, the build screen offers "Put it on your site as a chat bubble": one click makes the widget, shows the code, and already limits it to your site. You can also set a widget up later from the Deploy page, where the widget's Install page gives you the code and the list of websites it may be used on.
The script tag
The code is one tag with two attributes: data-bot-id names your agent, and data-widget-token is a public site token for that agent. Copy your own from the Install page; it looks like this:
<script
src="https://rylvo.com/widget.js"
data-bot-id="YOUR_BOT_ID"
data-widget-token="rwt_..."
async
></script>
Paste it just before the closing </body> tag; a site-wide footer setting covers every page.
If you set the widget up from the Deploy page, add your domain under Where it may be used (the one-click path fills it in for you). With entries there, the widget answers only on those sites (example.com also covers www.; *.example.com covers subdomains). Colour, position, launcher icon and greeting are set in the dashboard and apply at once, without a release. The "Powered by Rylvo" badge shows on Free only.
Floating launcher or embedded inline
| Mode | Looks like | Best for | Attribute |
|---|---|---|---|
| Floating (default) | A button in the corner that opens a chat panel | Every page of a marketing site | none |
| Embedded | The chat drawn inside a box on your page | A dedicated "Ask us" or support page | data-mode="embedded" and data-target |
<div id="ask-us" style="height:560px"></div>
<script
src="https://rylvo.com/widget.js"
data-bot-id="YOUR_BOT_ID"
data-widget-token="rwt_..."
data-mode="embedded"
data-target="#ask-us"
async
></script>
Optional attributes: data-theme="light" or "dark" to match your page, and data-z-index if the launcher sits under another floating element.
WordPress, Shopify, Wix, Squarespace, Webflow
Rylvo has no plugin or app for these builders. You paste the same snippet into the builder's own code setting:
| Platform | Where to paste the snippet |
|---|---|
| WordPress | Install the free WPCode plugin, then Code Snippets, Header & Footer, paste into Footer, Save |
| Wix | Settings, Custom Code, Add Custom Code, paste, choose All pages and Body – end, Apply |
| Squarespace | Pages, Website Tools, Code Injection, paste into Footer, Save |
| Shopify | Online Store, the ⋯ menu, Edit code, theme.liquid, paste just above </body>, Save |
| Webflow | Site settings, Custom code, paste into Footer code, Save, then Publish |
Check your builder's requirements first: Wix runs custom code only on a published site with a connected domain, and changing the domain deletes the snippet (Wix help); Squarespace Code Injection needs a Core, Plus or Advanced plan (Squarespace help); Shopify lets you edit the code of a paid theme only after you have purchased it (Shopify help). Paths checked November 2026.
On Shopify, the snippet lives in the current theme's theme.liquid: paste it again if you switch or replace your theme. Duplicate the theme first (⋯ menu, Duplicate) so you can revert.
If someone else runs your site, the Install page has an "Email it to whoever runs your website" link that opens a ready-written email in your mail app, with the snippet and where it goes. WordPress has its own walkthrough in how to add an AI chatbot to WordPress.
Pre-fill visitors you already know
If visitors sign in to your site, tell the assistant who they are so it does not ask for an email you already have:
<script>
window.addEventListener("load", function () {
if (!window.RylvoWidget) return;
RylvoWidget.identify({
name: "Jane Rao",
email: "jane@example.com",
fields: { plan: "gold" }
});
});
</script>
identify() can be called before the chat has loaded; the details are passed on when it does. They live in memory for that page view only (no cookie, localStorage or URL) and are not saved to your audience records. The assistant is told they are unchecked, so use them to skip questions, never to grant access. The same API can open the panel from your own "Chat with us" button (RylvoWidget.open()) or hide it on pages where chat does not belong (RylvoWidget.hide()).
Step 5: Decide where leads go
Captured leads land in a Leads inbox with search and filters. From there they can also go by email or by a webhook to Zapier, Make, n8n or your CRM.
Decide what it asks for (a name and one contact method is usually enough), when (after it has answered), and who follows up, how fast. The lead generation chatbot guide covers the questions to ask and how to route each kind of enquiry.
If you also want customers to reach the same assistant from Instagram, a flyer or a QR code, a Beam link works with no website at all: see an AI chatbot without a website. For messaging, the WhatsApp AI chatbot guide covers Meta's rules and costs.
What it costs
Prices checked on 2026-11-17, in USD. The full plan list is on the pricing page.
| Plan | Price | Agents | AI replies included each billing cycle | Knowledge sources | Badge |
|---|---|---|---|---|---|
| Free | $0 | 1 | None after the trial | 1 | Yes |
| Starter | $10/month | 1 | About 650 | 5 | No |
| Lite | $40/month | 3 | About 1,300 | 15 | No |
| Pro | $100/month | 25 | About 2,650 | 50 | No |
A few details that change the real cost:
- Starter's $10 is an early price, guaranteed for your first 12 monthly billing cycles. New customers pay $19 a month from 31 Jan 2027 or after the first 100 Starter customers, whichever comes first. Starter is billed monthly.
- Reply counts assume the default model. A stronger model uses more replies per answer, and the model picker shows how many. Unused replies do not carry over. Extra replies come in one-time packs of 1,000 for $5.
- Your own AI key is optional. Add one and the included replies pause until you remove it.
- Running out is not silent. At zero replies, the assistant tells visitors the business will get back to them, takes their details and emails you the lead.
- Every new workspace starts with a 7-day Pro trial, plus 7 more days the first time a customer talks to your assistant, and about 1,300 AI replies for a verified email. No card is needed.
How other tools charge, and what a do-it-yourself build costs, is in how much an AI chatbot costs.
After launch: the first week
Visitors will ask things you did not predict.
- Day 1: read every conversation. Each reply has a trace showing which pages it read, the model and the time and cost.
- Days 2 to 3: turn every wrong or weak answer into a fix: a missing page, a clearer instruction or a new test case. Make the fix in Test, rerun your tests, then release.
- Days 4 to 7: look for patterns, such as questions it cannot answer, and check that every lead reached a person.
On Pro, Edge Cases can check each live reply as it lands and file problems with their evidence. A person still reviews and approves every fix. Edge Cases and the other Pro tools are included in the 7-day Pro trial, so the first week of a new workspace can use them.
Trace history depends on the plan: 7 days on Free, 14 on Starter and 90 on Pro.
Common mistakes
Importing the whole blog. Old posts carry old prices and retired services, and the assistant cannot tell a 2019 post from today's pricing page. Start with pages that state current facts.
No "I don't know" path. Write the fallback into its instructions and test it with a question your content cannot answer.
Testing on the live site. Every experiment on the live widget is a real customer conversation.
Leaving "Where it may be used" empty. Without it, your snippet works on any site that copies it.
Hiding that it is an AI. Under Article 50 of the EU AI Act, AI systems that talk to people must be designed so people know they are talking to an AI, unless that is obvious. It has applied since 2 August 2026, per Article 113; the 2026 Digital Omnibus postponed other deadlines but left this disclosure duty in Article 50(1) on that date (checked November 2026). Wherever your customers are, a greeting such as "Hi, I'm the AI assistant for Bright Smile Dental" costs nothing.
Never checking page speed. The floating widget downloads its chat app only when a visitor first opens it. Still, check key pages against Google's Core Web Vitals after installing. As of November 2026 the "good" thresholds are a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads.
When another tool fits better
| If your main need is... | Consider | Why |
|---|---|---|
| Several people answering live chats together | A helpdesk with a shared inbox | Routing, assignment and response targets for human agents |
| Shopify order-status answers | A store app that reads orders natively | No API setup |
| An assistant that answers from your own content, tested before launch | Rylvo | Test copy, releases and a trace for every reply |
For side-by-side comparisons with specific tools, see compare.
The launch-ready checklist
Go through these 12 before you paste the snippet:
- Your services, prices, hours and location pages are in the knowledge base.
- Old or contradictory pages are left out.
- Key PDFs and FAQs are uploaded.
- Tone, never list and I-don't-know path are in the instructions.
- The greeting says it is an AI assistant.
- All 20 real customer questions were asked in Test.
- Every failed answer is fixed and saved as a test case.
- A question your content cannot answer gets "I don't know" and an offer to pass it on.
- The release is live, and Production answers your three hardest questions correctly.
- Your domain is listed under "Where it may be used".
- A test lead reached the right inbox or CRM.
- A named person follows up on leads, and knows how fast.
Frequently asked questions
How do I add an AI chatbot to my website for free?
Start a Rylvo workspace: it includes a 7-day Pro trial with about 1,300 AI replies for a verified email, and no card. Build the assistant, test it and paste the script tag. After the trial the workspace moves to Free, which keeps 1 agent in 2 places to deploy, such as the website widget and a Beam link, with a small badge. Free has no included AI replies, so to keep answering you either pick a paid plan, which includes replies, or add your own AI provider key.
Can I train ChatGPT on my website?
Not in the sense of retraining the model. Website chatbots, Rylvo included, read your pages into a searchable knowledge base and give the model the most relevant passages with each question. The model stays the same; what it reads changes. That is why updating a page and re-syncing updates the answers, with no retraining.
Do I need to code?
No. You paste your website address, answer four questions and paste one line of code into your site builder's footer or custom-code setting. If someone else runs your site, the dashboard gives you a ready-written email with the snippet and where it goes, to send them. Code is only needed for optional extras such as pre-filling a signed-in visitor's details.
How long does it take to set up?
The first working version takes minutes: Rylvo reads your site and builds a tested agent from it. Plan another hour or two to ask it your 20 most common customer questions, fix the gaps and decide where leads go. Pasting the snippet takes a few minutes on most site builders.
Will the chatbot slow my site down?
Very little. The script loads asynchronously, and in the default floating mode the chat app itself is not downloaded until a visitor first opens it, so an unopened widget costs your page only one small script. Check your own pages against Google's Core Web Vitals after you install it.
Does it answer in my customers' language?
Usually, yes. The assistant replies in the language the visitor writes in, as far as the AI model you choose handles that language, so it is model-dependent. The widget's own text, such as the greeting and placeholder, is whatever you type in the dashboard; it is not translated automatically.
