Launch Checklist

Use this checklist before putting ChattyBox in front of customers. It catches the common setup gaps that make a chatbot look installed but not ready.

Content Readiness

• Public, crawlable content is selected for the chatbot to answer from.
• Private pages, admin pages, checkout flows, account pages, drafts, and staging content are excluded.
• You chose the right crawl input: sitemap for broad coverage, manual URLs for a curated launch set, or homepage only for a small site.
• Important product, pricing, policy, support, FAQ, onboarding, and troubleshooting pages are included.
• Multilingual sites include the language versions you expect the widget to answer from.

Scraping Validation

• The scrape completed successfully in the dashboard.
• The indexed page count matches what you expected for your plan and launch scope.
• Recently edited or migrated pages have been re-scraped.
• Any blocked pages were checked for authentication, robots rules, redirects, or JavaScript-only content.

Answer Quality

• You asked real test questions from sales, support, onboarding, and documentation use cases.
• Answers only use your indexed content and refuse questions your content cannot support.
• Source citations appear on useful answers.
• Citation links open the expected public source pages.
• Weak answers have been fixed by improving source content or adding missing pages, then re-scraping.

Widget Installation

• The widget is installed on the intended public pages.
• The script loads only once per page.
• The script includes data-api-key.
• The script includes data-api-url.
• Any data-locale value matches the page language.
• The widget opens and sends a test question in an incognito window.
• Mobile viewport testing confirms the launcher and chat panel are usable.

API Key and Origin Checks

• The production public key exists in Public Keys and is the one selected in Embed.
• Deleted, rotated, or test-only public keys are not used on production pages.
• If your public key has allowed origins, the production origin is included exactly, such as https://example.com.
• Staging and production use the intended keys and origin restrictions.
• No private server API keys, admin tokens, or secrets are present in frontend code, GTM, CMS custom HTML, or page source.

Browser and Deployment Checks

• Browser console has no ChattyBox errors.
• Content Security Policy allows the widget script and API URL if your site uses CSP.
• Ad blockers or consent tools are not blocking the widget on the pages where it is expected.
• The final deployed site, not only local development, has been tested.

After Launch

• Review analytics after the first traffic window.
• Check unanswered questions and content gaps.
• Add missing documentation, FAQs, or examples based on real visitor questions.
• Re-scrape updated pages after content changes.
• Rotate or restrict public widget keys if your launch domain changes.

If any item fails, use Troubleshooting before launch.