Start with a controlled knowledge boundary
Navigation and search work when visitors already know the language used by a site. A grounded assistant helps when someone describes a problem in their own words or needs an answer spread across several pages. It should use approved public content, show where an answer came from and abstain when the site does not contain enough evidence.
Measure readiness, not installation
A WordPress administrator should see how many pages were discovered, processed and indexed, which pages failed and whether the assistant is ready. Installed is not the same as working. The meaningful activation event is the first useful, source-grounded answer after the knowledge base reaches a ready state.
Keep the service boundary clear
A reviewable plugin can own WordPress administration, the local widget and a signed connection. Managed indexing, retrieval, tenant isolation and protected credentials belong in controlled infrastructure. This keeps the distributed client understandable while allowing the service to operate and improve safely.
Use a ten-question evaluation
Choose ten questions that matter to real visitors. Verify that answers use approved sources, handle missing evidence, survive a content update and disappear correctly when a source is removed. Then measure time to first value, unresolved questions and support effort—not conversation volume alone.
Install Site Agent
Site Agent by Qentra uses a bounded same-origin crawl, visible indexing states, source-grounded answers, configurable retention and an explicit deletion path. Install Site Agent from the official WordPress Plugin Directory or review the product and operating model.