What to add
Start with pages that answer real visitor questions: services, products, delivery, returns, FAQs, policies, pricing explanations, and contact information.
What to review
After import, check whether each source is fetched, indexed, blocked, stale, or URL-only. URL-only rows are not enough for grounded answers.
How to improve weak answers
If the assistant answers vaguely, add a clearer source page, manual Q&A, or file with the exact answer. If a page cannot be fetched, use the blocked crawler guide or upload the content manually.
Safety rule
Do not rely on pages that are private, outdated, commercially sensitive, or not suitable for customer-visible answers.
What to check before launch
Use Add Website Knowledge as part of a controlled setup path, not as a standalone promise. Confirm the relevant website pages, product-feed fields, policies, assistant instructions, handoff destination, and safe test questions before showing the widget to visitors. For ecommerce or technical catalogues, check that product attributes, variants, delivery limits, compatibility notes, and returns wording are approved for customer-visible answers.
Evidence to keep
Keep a small evidence trail for each launch: which sources were imported, which sources were approved, which answers were tested, which weak answers created missing-knowledge actions, and which questions should still be handed to a person. This makes the assistant easier to improve after launch and avoids unsupported product or policy claims.
Safe boundary
If the assistant cannot confirm an answer from approved knowledge, it should say what is missing and offer the safest next step: ask a clarifying question, suggest a relevant page, create a support handoff, or tell the visitor that the team should confirm before purchase or action.