Start with the knowledge boundary
The assistant should use content that the website has deliberately published and make its sources visible. Administrators need to know what was indexed, when it was refreshed, and what happens after a page is changed or removed. Private and authenticated areas should not quietly become answer material.
Define readiness
Installing a plugin is not the same as delivering a useful answer. A practical activation flow shows content discovery, processing and indexing states. The first meaningful success event is a source-grounded answer to a real visitor question after the index reaches ready state.
Run a ten-question evaluation
Include straightforward, ambiguous and deliberately unanswerable cases. Check whether answers cite the right pages, refuse to invent missing information, update after a content change and stop using a deleted source.
Review operational control
Review conversation retention, tenant separation, administrative access, disconnect behavior and deletion. Ask which credentials stay inside WordPress and which processing occurs in managed infrastructure. A clear boundary is easier to review and support.
Measure useful outcomes
Conversation volume is not the goal. Measure time to first useful answer, supported-answer quality, correct abstention and the support effort required to keep the assistant reliable.
Site Agent by Qentra
Install Site Agent from the official WordPress Plugin Directory: WordPress.org. Product and operating model.