Creator Assistant Knowledge

No. The ca_knowledge post type is registered as strictly private:

• publicly_queryable: false — direct URL requests return a 404.
• exclude_from_search: true — entries never appear in WordPress search results.
• has_archive: false — no archive page exists.
• rewrite: false — no pretty permalink is generated.

No. Creator Assistant Knowledge only creates new entries in its own private post type. Your existing posts, pages, custom post types, and all their content are completely untouched.

Because nothing would be done with it. This plugin acts on gaps: what it can do with "this did not help" is open a draft entry for an admin to answer. A button that records nothing would be a control that lies about what it does, so there is only one, and it reports a problem.

No. The plugin creates a draft entry of the private ca_knowledge post type. Drafts are never publicly visible. The entry is pre-filled with the search query and the AI response so an admin can review it, improve it, and publish it to the knowledge base — at which point it becomes available to the AI but remains invisible to visitors (see above).

No. Before creating a draft the plugin embeds the query and compares it with the searches already assigned to existing entries, published or draft. Above a similarity threshold the query is recorded on the entry that already covers it and no new draft is created, so a gap asked in ten different wordings produces one entry with ten recorded searches instead of ten drafts. The searches assigned to an entry are listed in a panel in the editor sidebar, and the entry list shows how many wordings and how many requests each entry has collected.

Creator Assistant, then Knowledge. The similarity threshold is the only setting there, and the page explains what the numbers mean. The whole range is usable. At 1 nothing is ever merged and every new wording gets its own entry. At 0 everything is merged: after the first entry, no new one is created and every unanswered search is filed under it. In between, raise it and you get a second draft for a question you already have, which you can see and merge by hand; lower it and a distinct question ends up filed under an entry that does not answer it, and nobody notices. The two mistakes do not cost the same, so when in doubt, raise it.

Because there is nothing for the results loop to render. Knowledge entries are private, so they are never put into the search results, and on a classic theme the panel is injected on loop_start, which WordPress does not fire when the loop is empty. Block themes are unaffected: the panel is injected around the query block, which renders either way. If your site runs a classic theme and you want the panel on those searches too, place it explicitly with the [creator_assistant_search_ai_overview] shortcode or the AI Overview block in your search template, instead of relying on automatic insertion.

Two things:

1. ca_knowledge posts — entries you create in the Knowledge admin section, plus any drafts created automatically from visitor feedback. All are private and never visible on the frontend.
2. A post meta entry (_creator_assistant_knowledge_reason) on feedback-generated drafts, recording whether the draft was created because of a negative rating (negative_feedback) or an unanswered query (no_answer).
3. Post meta entries (_creator_assistant_knowledge_queries), one per search assigned to an entry, so the admin can see which wordings that entry has to cover.
4. A post meta entry (_creator_assistant_knowledge_hits) counting how many times an entry was asked for.
5. One option (creator_assistant_knowledge_intent_threshold), the similarity threshold from the settings page.

Deactivating the plugin hides the Knowledge admin section and stops feedback processing; your knowledge entries are preserved in the database. Deleting the plugin removes all knowledge entries and their post meta from your WordPress database, and drops the two Qdrant collections it owns (creator_assistant_<id>_knowledge_chunk and creator_assistant_<id>_knowledge_intent, where <id> is the random identifier Creator Assistant Hub gives each site so several sites can share one Qdrant cluster). Your regular posts, pages, all public content and the shared vector collections are completely unaffected.

Creator Assistant - Hub's Reset button, and switching to a different embedding model, both invalidate every stored query vector: the whole point of the similarity comparison is that queries embedded with different models are not comparable. When either happens, this plugin drops its query-matching collection (creator_assistant_knowledge_intent) and rebuilds it in the background, in small batches, from the searches already assigned to your entries. Nothing you have written is lost: the entries, their assigned searches and their request counts all stay as they were, only the vectors used to recognise a reworded question are recomputed.