Frequently asked questions
Everything worth knowing before you start — what the Presence Engine does, which AI engines it tracks, how fixes are applied and reviewed, what we need from you, and how results show up.
What the Presence Engine does
What is CLEO?
CLEO is a Presence Engine — it doesn't just measure how your brand appears across AI-generated answers, it improves it. It runs a closed loop that diagnoses gaps, applies fixes, and re-measures until your brand is reliably cited.
How is that different from an AI visibility dashboard?
Most tools stop at a score and hand you a to-do list. CLEO takes the next step and executes the repair server-side, then verifies the lift, so the number moving is the outcome rather than the report.
Which AI engines are tracked
Which engines does CLEO monitor?
CLEO tracks your presence across the major AI answer engines, including ChatGPT, Google Gemini, and Perplexity. Each engine is measured independently so you can see exactly where you are cited and where you are absent.
How often is presence re-checked?
Presence is re-sampled on a recurring basis and after every fix is deployed. That way you can distinguish a durable improvement from normal day-to-day variation in model outputs.
How server-side fixes are applied and reviewed
What does a server-side fix actually change?
CLEO opens crawler access, writes structured data, resolves canonicals, and repairs the machine-readable layer that AI engines rely on. These changes happen at the edge, without raising tickets against your product backlog.
Do the changes need my team's approval?
Yes. Every proposed change is staged and reviewed before it goes live, and you can approve, defer, or roll back any fix. Nothing ships to your live infrastructure without a clear, auditable step.
What data is needed to get started
What do you need from me to begin?
To start, CLEO needs your primary domain and the set of prompts or topics you want to be found for. That is enough to run an initial diagnosis and show where your brand stands today.
Do you require access to our codebase?
No codebase access is required to diagnose, and fixes are applied at the edge rather than inside your repository. When deeper integration helps, we scope it explicitly with your team first.
How results are measured
How will I know CLEO is working?
Results are tracked as measurable lift in citation rate and AI market share across the engines you care about. You see the before-and-after for each engine, with the change tied to the specific fixes that produced it.
How long until I see results?
Most brands see meaningful movement within weeks of the first fixes shipping, not months. The pace depends on how much of the machine-readable layer needs repair, which the initial diagnosis makes clear.
Still have a question? See where your brand stands today.
Run a scan