Add an AI Chatbot Trained on Your Website

Decide the Chatbot's Job

Before creating the chatbot, decide what job it should actually do. For a simple business website, the chatbot may answer questions about:

- Services - Pricing - Opening hours - Locations - Booking - Delivery - Contact information - Policies - Frequently asked questions

NOTE

Do not try to make the first version handle every possible business workflow.

Audit the Website

Use your AI coding assistant to identify what information is already available.

AI Chatbot Knowledge Audit

Reviews the website's real content — what the business does, services, pricing, hours, locations, booking/contact options, delivery, refund/cancellation policies, FAQs, About and Contact pages — flags conflicting, placeholder, or outdated information and anything that should NOT become public chatbot knowledge, never exposes secrets or private data, changes nothing, and reports the best knowledge sources, missing information, and the chatbot's recommended job in one short paragraph.

Review this website specifically for creating an AI customer-support chatbot that will answer questions using the website's real content. Do not change anything. Identify: - what the business or website does - main products or services - pricing information - opening hours - locations or service areas - booking/contact options - delivery or shipping information - refund/cancellation policies if present - FAQs - About information - important service/product pages - Contact page - any existing help/support content Also identify: - conflicting information between pages - placeholder information - outdated information - important customer questions the website does not currently answer - information that should NOT be used as public chatbot knowledge Do not expose: - private environment variables - API keys - internal admin information - private customer data - backend-only information Finish with: Best Knowledge Sources List the pages/content the chatbot should learn from. Missing Information List important customer questions that need a confirmed answer before the chatbot should answer them. Recommended Chatbot Job Describe in one short paragraph what this chatbot should and should not do.

Keep the Scope Clear

A good first chatbot could have one simple goal:

Answer common questions and help visitors find the right page or contact option.

That is enough.

IMPORTANT

Do not start with autonomous refunds, account changes, order modifications, payment actions, or access to private user data. Those require a more advanced and trusted integration.

Create Your Chatbase Agent

Create a Chatbase account and select New AI agent, then add your website as a knowledge source. Chatbase currently supports website content as well as files, text, Q&A, and other sources, so you can start with the site itself and add missing information later.

Chatbase

Create an account, or sign in if you already have one.

https://www.chatbase.co

Add Your Website

Enter your real website URL and let Chatbase discover or import the relevant pages. Review what it finds.

Example

https://yourbusiness.com

IMPORTANT

Do not intentionally include admin pages, private dashboards, unpublished internal documents, or pages containing information the chatbot should not reveal.

Add Missing Answers

If important information is not available on the public website, add confirmed Q&A manually. Chatbase supports adding manual Q&A alongside website and document sources.

Example question

Do you offer free estimates?

Example answer

Yes. You can request a free estimate from our Contact page.

IMPORTANT

Do not let AI invent the answer.

Give the Agent Clear Instructions

Configure the chatbot so it behaves like a useful website assistant rather than a general-purpose AI. Use instructions similar to:

Agent instructions

Answer questions using the provided business knowledge. Be concise and helpful. Do not invent prices, policies, services, availability, guarantees, locations, or business information. If the answer is not available in the knowledge base, say that you are not sure and direct the visitor to the appropriate contact option. Do not claim to have completed bookings, payments, refunds, account changes, or other actions unless those actions are actually connected and confirmed.

Test It Inside Chatbase

Before adding it to the website, ask questions such as:

What services do you offer?

How much does [service] cost?

Where are you located?

How can I book?

What are your opening hours?

Do you offer [service the business does NOT offer]?

Can you give me a discount?

What is your refund policy?

NOTE

Pay special attention to questions where the correct response should be "I don't have enough information to answer that." A chatbot that admits uncertainty is better than one that confidently invents business information.

Customize the Widget

Once the answers are reliable, customize the visitor experience. Configure useful basics such as:

Chatbot name

Welcome message

Logo/avatar if appropriate

Brand colors

Suggested questions

Fallback behavior

Example welcome message

Hi! 👋 How can I help you today?

Example suggested questions

What services do you offer? How can I book? Where are you located?

Keep it simple.

Get the Website Embed

In Chatbase, deploy the agent as a Website widget and copy the official embed code. Chatbase's current deployment flow provides a website widget/embed script that can be inserted into an existing site. Then give the code to your AI coding assistant.

Deploy Website widget

Add the Chatbot to the Website

Add the Chatbase Chatbot

Wires the official Chatbase widget into the existing website — inspects the framework, layout, and any existing chat/floating widgets first, initializes the chatbot only once, keeps it working on desktop and mobile without covering CTAs, navigation, or cookie controls, and preserves any existing consent mechanism. Never rebuilds the chatbot with a custom AI API, adds private AI API keys to frontend code, creates an unneeded backend, or loads the widget more than once. Runs the production build, lists every file changed, and answers AI chatbot integration: READY or NOT READY.

Add this Chatbase AI chatbot to the existing website. Official Chatbase embed code: [PASTE THE OFFICIAL CHATBASE EMBED CODE] First inspect: - the framework/project structure - global layout/root component - existing third-party scripts - existing chat widgets - WhatsApp/floating buttons - cookie/consent UI - other fixed mobile elements Requirements: - use the official Chatbase integration - initialize the chatbot only once - make it available on the intended website pages - preserve the existing design - keep the implementation isolated and easy to remove/update - make sure the widget works on desktop and mobile - make sure it does not cover important CTAs, navigation, cookie controls, or other floating elements - preserve any existing consent mechanism where relevant Do not: - rebuild the chatbot with a custom AI API - add OpenAI, Anthropic, Gemini, or other private API keys to frontend code - create an unnecessary backend - load the Chatbase widget multiple times - remove existing contact options unnecessarily - redesign unrelated parts of the website After implementation: - run the production build - check for browser/runtime errors - list exactly which files changed Finish with: AI chatbot integration: READY / NOT READY

IMPORTANT

Never add OpenAI, Anthropic, Gemini, or other private AI API keys to frontend code — the official Chatbase embed does not need one.

Test Real Questions

Do not publish it after asking only one easy question. Test whether the chatbot knows when it doesn't know something. Open the website in a private/incognito browser and ask questions from several categories.

Questions It Should Know

What services do you provide?

How do I contact you?

Where are you located?

How do I book?

What are your opening hours?

Questions It Should Not Invent

Ask something deliberately missing:

Do you offer a 40% discount?

Do you provide lifetime guarantees?

IMPORTANT

If that information does not exist, the chatbot should not invent it.

Test Navigation Help

Ask: "Where can I book an appointment?" The chatbot should point visitors toward the appropriate real page or action when the knowledge supports it.

Run the Final Production-Readiness Audit

Chatbot Production Audit

Verifies the chatbot loads correctly, initializes only once, works on desktop and mobile without covering navigation or CTAs, and the production build succeeds — reviews the real website content to build a test set (services, pricing, contact, location, hours, booking, policies, common questions) plus several questions with no answer in the knowledge base, flags conflicting/outdated/ambiguous content, and never invents missing answers. Finishes with Chatbot website status: READY or NOT READY.

Run a final production-readiness audit for the Chatbase AI chatbot integration. Verify: Website integration - the chatbot loads correctly - it initializes only once - it works on desktop - it works on mobile - it does not cover important navigation or CTAs - no duplicate chatbot integration exists - the production build succeeds Knowledge quality Review the public website content that the chatbot is expected to use and create a test set covering: - services/products - pricing if available - contact information - location/service area - opening hours - booking - policies - common customer questions Also include several questions whose answers are NOT present in the website knowledge. I will use these questions to test the chatbot manually. Flag any conflicting, outdated, or ambiguous website content that could cause incorrect chatbot answers. Do not invent missing answers. Finish with: Chatbot website status: READY / NOT READY If NOT READY, list only the issues that should be fixed before real visitors use it.

Keep the Knowledge Updated

The chatbot's answers are only as good as its sources. When you change important website information such as prices, services, opening hours, policies, locations, or FAQs, update or re-sync the chatbot's knowledge as necessary.

NOTE

Chatbase specifically notes that website-trained agents need their source content kept current, especially when pricing, products, or policies change.