CLEO lotusCLEO
Book a conversation
Questions & Answers

Frequently asked questions

Everything worth knowing before you start — what the Presence Engine does, which AI engines it tracks, how fixes are generated, reviewed, and deployed, what we need from you, and how ARS and visibility lift are measured.

What the Presence Engine does

What is the CLEO Presence Engine?

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 it different from an AI visibility dashboard?

Most tools stop at a score and hand you a to-do list. CLEO executes the repair server-side and then verifies the lift, so the number that moves is the outcome rather than the report.

Who is CLEO built for?

CLEO is built for brands that want to be cited when people ask AI engines for recommendations. It suits teams who care about presence in AI answers but don't want to divert engineering resources to chase it.

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 again after every fix is deployed. That lets you distinguish a durable improvement from the normal day-to-day variation in model outputs.

How server-side fixes are generated, reviewed, and deployed

How are fixes generated?

CLEO diagnoses the machine-readable layer AI engines rely on, then generates targeted fixes — opening crawler access, writing structured data, and resolving canonicals. Each fix maps to a specific gap found during diagnosis so nothing is speculative.

Are fixes reviewed before they go live?

Yes. Every proposed change is staged and reviewed before it ships, and you can approve, defer, or roll back any fix. Nothing reaches your live infrastructure without a clear, auditable step.

How are fixes deployed?

Approved fixes are applied at the edge, without raising tickets against your product backlog. Because deployment is server-side, changes take effect quickly and can be reverted just as cleanly if needed.

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 would help, we scope it explicitly with your team first.

How ARS and visibility improvements are measured

What is the AI Readability Score (ARS)?

ARS is a composite measure of how well your site can be read and cited by AI engines, covering crawler access, JS rendering, structured data, and content quality. It gives you a single, trackable number for the machine-readable health of your presence.

How are visibility improvements measured?

Improvements are tracked as measurable lift in citation rate and AI market share across the engines you care about. You see the before-and-after per engine, with each 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.

Onboarding, security, and reporting

What does onboarding look like?

Onboarding begins with a scan of your domain and target prompts, followed by a diagnosis you review together with our team. From there you approve the first set of fixes and CLEO takes over the closed loop.

How is my data kept secure?

CLEO works with the minimum data needed to diagnose and repair your presence, and access is scoped and auditable. Sensitive integration is only introduced when explicitly agreed, so your systems stay under your control.

What reporting do I get?

You get engine-by-engine visibility on citation rate, AI market share, and ARS, alongside a log of every fix and its effect. Reporting is built to tie each metric change back to the work that caused it.

Still have a question? See where your brand stands today.

Run a scan