Operator
Ask the platform, not the dashboards.
The answer to most real questions lives across several places at once — what answer engines are showing, what your site looks like underneath, what you decided to do, what happened next. Operator is where you ask across all of it in one place.
No card required.
- Reads across your evidence
- Grounded in your context
- Answers with its sources
You ask
“Where are we losing ground, and what did we already try?”
Draws across
- AI evidence
- Site evidence
- Intelligence Library
- Opportunities
- Cases
- Reports
Returns
An answer, with the evidence it came from
One surface over everything
The question is rarely about one screen.
Anything worth asking tends to cut across the platform. Operator is the interface that does that crossing for you, rather than leaving you to hold six views in your head at once.
Operator
-
AI evidence
Citations, share, competitive selection and readiness.
-
Site evidence
Technical, crawl, metadata and performance signals.
-
Business context
What your Intelligence Library says about the organisation.
-
Opportunities
What has been judged worth attention, and why.
-
Work
What was committed to, what shipped, what is open.
-
Reports
What has already been communicated, and when.
Set expectations correctly
This is not the chat window you are picturing.
The interface is conversational. What sits behind it is not a general assistant that has been pointed at your account.
- A support bot It answers questions about your evidence, not about how to use the product.
- A prompt box on a model It works from your own observed evidence and the context you have set.
- Fix Assist Fix Assist builds an implementation package. Operator helps you understand and decide.
- Content Studio Content Studio produces content. Operator reasons across what the platform already holds.
The kind of thing it is for
Questions that would otherwise take an afternoon and three exports.
These are illustrations of the shape of question Operator is built for. They are examples of what you might ask, not a script.
- Which questions in our category are we consistently absent from?
- Who has been showing up in our place most often this quarter?
- What did we commit to after the last review, and what shipped?
- Which open Opportunities relate to the pages we just changed?
- What has the evidence looked like since that work went live?
- What would I need to know before this client call?
Answers are composed from evidence CiteWorth holds, and carry that evidence with them so you can check the reasoning rather than take it on trust.
Where it stops
It reasons across your platform. It does not go and act on your systems.
Operator does not have standing write access to your CMS, your repository or your client's infrastructure, and we are not going to imply that it does. It helps you understand the position and decide what should happen. Committing to work is still a decision a person makes, and implementation still happens in your systems under your review.
In practice
- It reads and reasons across evidence, context and work
- It shows the evidence behind what it tells you
- It does not change your live site on your behalf
- It does not commit work without you deciding to
What Operator connects to
Operator is only as good as what sits underneath it, which is most of the platform.
Stop assembling the answer yourself.
Build up some evidence, then ask across it in one place.
Want to see how this works on your account? Talk to us