Public site
Website pages and sitemaps
Best for brochure sites, service pages, pricing pages, policy pages, and support pages that are already public and crawlable.- Website URLs
- Sitemaps
- Specific pages
- Public FAQs
Capability proof
Website-trained chatbots are useful, but the source details matter.
The buying question is not just whether a chatbot can read your website. It is whether it can use the right pages, files, help articles, product data, and refresh path for the job.
Short answer
FastBots, Chatbase, Tidio, and ChatBot.com all document ways to use website or knowledge-source content. The better choice depends on what "from my website" really means for your buyer job.
FastBots and Chatbase are the cleanest first checks for public website answers and document-style sources. Tidio is stronger when the website answer needs to sit inside support workflow, Zendesk knowledge, or ecommerce product context. ChatBot.com is worth checking when the buyer wants AI Knowledge inside the broader Text support workspace.
Source layers
Website answers are really four different jobs.
A chatbot can be excellent at public website Q&A and still be the wrong tool for synced products, account-specific support, or stale private docs.Docs
Files, snippets, and Q&A
Best when the answer should come from approved documents or short canonical answers rather than every page on the site.- DOC/DOCX
- CSV
- Text snippets
- Manual Q&A
Support
Help centers and handoff
Best when the buyer wants AI to answer routine support questions but still route unknown or risky cases to a person.- Zendesk
- KnowledgeBase
- Suggestions
- Source review
Store data
Product catalogs need special proof
Public product pages are not the same thing as a synced catalog, stock-aware answer, order lookup, return workflow, or account action.- Shopify products
- WooCommerce products
- Product feeds
- Order-status limits
Tool fit
Which source path is strongest?
These are official-source capability notes, not hands-on answer-quality scores.FastBots
Strong for public site answersWebsite and document chatbot
Best when
Small sites that want a trained chatbot over website pages, sitemaps, uploaded documents, Google Sheets, or YouTube URLs.Check
If you need strict website-only answers, confirm how the bot uses uploaded content, ChatGPT knowledge, and live web data in your configuration.Chatbase
Strong for source controlControlled source workspace
Best when
Teams that want websites, sitemaps, files, snippets, Q&A, Notion, and source cleanup in one AI-agent workspace.Check
Auto Retrain is documented for Standard and Pro plans; Hobby users should expect to retrain manually after source changes.Tidio
Strong for support contextSupport knowledge plus commerce
Best when
Teams that want Lyro to use website data, manual Q&A, CSV/PDF imports, Zendesk articles, solved-chat suggestions, and store products.Check
Tidio documents priority-page, single-page, URL, file, Zendesk, and product-sync paths, but some higher limits and auto-sync options sit behind Plus/Premium-style packages.ChatBot.com
Strong for help-center sourcesAI Knowledge inside Text
Best when
Support teams that want AI Assist to use websites, articles, KnowledgeBase, Zendesk, and the wider ChatBot/Text workflow.Check
ChatBot.com documents a bot-structure-first priority, then AI Knowledge. That is useful, but it means you should test what answers come from flow logic versus source content.Capability table
Compare source type before comparing answer quality.
A full-site crawl, a sitemap, a PDF, a manual Q&A, a help-center import, and a product sync are not interchangeable. Start with the source type your business actually trusts.
| Tool | Website path | Other sources | Refresh check | Best fit |
|---|---|---|---|---|
| FastBots | Entire websites and sitemaps are documented. | PDF, DOC, DOCX, CSV, XLS, Google Sheets, and YouTube URLs are documented on the official site. | Buyer should confirm retrain/refresh cadence for the chosen setup. | Straightforward public website Q&A. |
| Chatbase | Full site, sitemap, and individual URL crawling are documented. | PDF, TXT, DOC/DOCX, text snippets, Q&A, and Notion are documented. | Auto Retrain is documented for Standard and Pro; Hobby retrains manually. | Source-managed AI agent with cleanup controls. |
| Tidio | Lyro can scan priority pages, single pages, and URL sources. | Manual Q&A, CSV, PDF, Zendesk Help Center, solved-chat suggestions, and product sync are documented. | Manual re-sync is documented; weekly auto website re-sync is documented for custom Plus/Premium packages. | Support workflow plus public-site and product knowledge. |
| ChatBot.com | AI Knowledge documents website scanning as a source type. | Articles, KnowledgeBase, Zendesk, and training content are documented; source count is documented up to 5,000. | Refresh content controls are documented for article sources; buyer should test source update behavior. | Support bot inside the broader Text workspace. |
Evaluation flow
Test the source boundary before you trust the bot.
The simplest useful proof is asking one question from each source type, plus one question that should not be answered at all.List the sources
Separate public pages, PDFs, help-center articles, product data, private policies, and manual answers before choosing a chatbot.
Check ingestion style
Ask whether the tool crawls a full site, sitemap, priority pages, individual URLs, files, manual Q&A, help centers, or product feeds.
Check update behavior
A chatbot that can answer from your site still needs a retrain, re-sync, or auto-refresh path when your content changes.
Ask source-bound questions
Use questions whose answers exist in one page, multiple pages, a file, and nowhere at all. Unknowns should trigger a safe fallback.
Risk boundary
What should answer automatically?
Website-source bots are best when the content is approved, current, and safe to quote. Unknown, private, or account-specific questions should fail gracefully.Good first answers
Public FAQ and policy answers
Hours, service areas, shipping policy, return windows, booking prep, and standard product or service descriptions.
Source-linked support answers
Answers where the visitor can see or request the source page, help article, or approved knowledge item.
Lead-detail collection
Collecting the user's question, page context, product interest, or quote details before a human reviews the request.
Keep human review
Anything not in the sources
If the source content does not answer the question, the bot should say so or hand off rather than improvise.
Account, order, billing, or safety claims
Public website content is not proof of authenticated account actions, live inventory, refunds, diagnostics, or emergency advice.
Changed pages and stale docs
A source-aware chatbot still needs re-sync, review, and fallback testing after pages or policies change.
Buyer checks
Five questions to ask before signup.
This is where a buyer avoids a disappointing trial. Most tools can say "train on your website"; fewer buyers ask how source quality, refresh, and fallback actually work.
Can it crawl the source you need?
Check full website, sitemap, priority pages, single URLs, files, Q&A, help center, product feed, and private content separately.
Can you remove bad sources?
Source cleanup matters when the crawler finds old pages, duplicated policies, obsolete PDFs, draft copy, or thin product pages.
How does it refresh?
Look for manual retrain, re-sync, auto-refresh, source timestamps, and plan gates before assuming changed pages update automatically.
What happens when the answer is missing?
A good source-bound bot should cite, hand off, ask a clarifying question, or say it does not know instead of inventing a policy.
Source basis
Official pages checked on May 26, 2026
This guide is desk-reviewed. It confirms documented source-ingestion paths, but it does not claim hands-on crawl quality, answer accuracy, source ranking, or production support performance.
Next checks
After source fit, check cost and handoff.
A website-source chatbot still needs enough usage allowance, a safe unknown-answer fallback, and a support handoff path when the content cannot answer the buyer's question. If the source path is clear, use the plan picker to choose the first tier to inspect.