How to Make an AI Chatbot Use Your Website Content
Give Niwa accurate website content, rebuild the knowledge index and add business rules. Test retrieval and answers against your published information.
To make an AI chatbot use your website content, connect the chatbot to that information and check what it retrieves. In Niwa, run Run Full Index + Embeddings in WordPress, add your business facts and instructions in Frontend Agent Rules, then test answers against your actual pages. An active AI account alone does not give the assistant your policies or service details.
Start with the questions customers need answered. For a furniture store, those might concern dimensions, care and delivery. For a studio, they could be session duration, location and cancellation conditions. Prepare the source information for those questions before expanding the assistant's role.
Give each fact an identifiable source
Choose the page or record that should answer each question. A delivery page should state where you deliver, the relevant conditions and what a customer should do if their destination is unclear. A service page should explain what is included and how to enquire or book.
Write complete information rather than isolated fragments. "Delivery available" leaves the assistant guessing about destinations and conditions. A clear published policy provides something you and the assistant can verify.
Remove conflicting versions. If your homepage promises a different service duration from the booking description, decide which is correct and update both. An index can make information searchable; it cannot decide which of two contradictory business promises you intended.
Use information that customers are allowed to receive. Private contracts, credentials and staff notes should not become public business guidance. Review the Niwa safety information when deciding what relevant context can be sent to your connected AI provider.
Build Niwa's searchable site knowledge
Confirm that Niwa is installed, its licence is active and the intended model connection is configured. Then open Niwa AI → Main Settings and select Run Full Index + Embeddings.
Follow the Indexed, Embedded and Pending counters and inspect any service errors. Indexed records represent searchable content; embeddings provide a representation used to retrieve relevant material. Use the counters to confirm indexing has finished, then test the relevant customer answers.
The Niwa setup handbook documents the full rebuild and retrieval test controls. If work remains pending, investigate the reported error and service availability before repeatedly starting another full rebuild.
This process connects the assistant to a knowledge source. It does not train a new model from scratch. The assistant still needs to retrieve the right material, understand the question and use the facts accurately.
Add business guidance in Frontend Agent Rules
Open Frontend Agent Rules and complete the fields relevant to your business: company information, products or services, FAQ, policies, tone and human handoff. Save this page separately from Main Settings.
Use the profile to state facts and explain how the assistant should handle them. For example:
Use our published delivery and returns information. If you cannot confirm whether a condition applies to this customer, explain what is missing and direct them to our contact page. Do not invent a delivery date or exception.
Instructions should express the meaning of the boundary. You do not need a list of English phrases a customer must use to trigger a correct answer. People may describe the same need in another language or with different wording.
Keep the profile consistent with the website. A copied policy in the FAQ becomes another place to maintain. For frequently changing details, keep the current information in its appropriate source record and make sure the assistant uses that source.
Inspect retrieval before judging the final answer
Use Test Query and Run Demo in Main Settings to inspect retrieval with a question from your prepared list. A demo can use the configured model service, so its normal account allowance applies.
Ask a specific question first, such as whether delivery covers the region stated in your policy. Check whether the relevant material is found. Then ask a natural paraphrase of the same question. This helps separate a source-coverage problem from a wording or answer problem.
If the material is not found, confirm that the source is current and the rebuild completed. If the right information is available but the answer changes its meaning, review the rules and reproduce the conversation with the public chat.
Retrieval checks and visitor checks serve different purposes. A record appearing in a retrieval test is useful evidence; the visitor still needs a clear, correct answer and a working next step.
Test a conversation against the source page
Open the website in a private browser window. Ask a question with a known answer, then a follow-up that depends on the first answer. Compare the reply with the page or service record rather than whether it sounds plausible.
Also ask about something the source does not say. If your website does not promise same-day delivery, the assistant should not manufacture that promise. Give it a useful route to the team when confirmation is needed.
For products, descriptive content explains material or care; prices, stock and variations should be checked against the relevant catalog records. Niwa capabilities describes its product and customer-help workflows. Treat changing catalog information separately from a long-lived policy document.
Maintain the source after launch
When a policy or service changes, update its authoritative page and any duplicate business-rule text, refresh the relevant knowledge and repeat the affected questions. Test in a fresh conversation so an earlier answer does not conceal the update.
A chatbot that uses website content needs an ongoing information owner. Assign someone to review new customer questions and turn missing answers into accurate source material.
If you need help connecting your existing WordPress content to Niwa, send your website URL and the questions you want it to answer. Include the page that should support each answer. That makes the setup concrete and the result easier to check.
