Skip to content
ceeme

How it works

How ceeme works

ceeme measures whether AI assistants mention, cite or recommend your company when a customer asks a real question — and records what is missing when they do not. This page describes that route, from measurement to proof.

Measure your own company → Rather talk it through first

In short

ceeme
A measurement system that establishes whether AI assistants mention, cite or recommend a company, and what is missing when they do not.
mentioned
Your name appears in the answer.
cited
A source of yours is cited by the engine.
chosen
You are recommended, not merely listed. This is the only one that produces revenue.
query fan-out
The sub-questions an engine splits one question into before it answers.

What exactly does ceeme measure?

ceeme asks AI engines real customer questions and measures three things separately: are you mentioned, is your source cited, are you chosen. Adding those three into one number hides which of the three is broken, so we do not.

What ceeme measuresWhat ceeme does not measure
Answers from AI engines to real customer questionsSearch engine rankings — an AI answer is not a list of ten links
Which sources underpin that answer, and whether they were fetched liveWhat a model "remembers" without searching — that does not count
The sub-questions an engine splits your question into (query fan-out)Volume estimates per prompt — those do not reliably exist
Whether you are mentioned, cited or chosen, counted separatelyOne composite score — it hides which lever is broken

Why a prompt and not a keyword?

Because nobody says a keyword to an assistant. People type a situation: "who do you recommend in my area". The engine splits that question into sub-questions itself and answers them separately. Measure on a keyword and you measure a question nobody asks.

One trap we walked into ourselves: put the company name in the prompt and you plant the brand in the model's head, then ask whether the brand is there. That is not a measurement, that is a leading question. So the name only comes in after the answer.

The prompt a real customer question The engine answers with sources The weighting we measure and publish

How does ceeme know why AI chooses?

By looking at what underpins the answer. Decision Drivers are the factors that recur for those who do get chosen: source quality, freshness, whether you are recognisable as an entity, citations, local context and human signals. Not a black box — factors you can act on.

Who does the work?

Thirteen agents, each with one task. They hand off to each other, and between writing and publishing sits a gate only you open.

Radarspots what changed
Scoutfetches the sources
Pathfinderpicks the route
Curatororders the evidence
Appraiserweighs the value
Scribewrites the fix
Judgeapproves or rejects
Tunertunes
Launcherexecutes
Failsaferolls back
Heraldreports the result
Posterpublishes
Sentrykeeps watching

REWORK If Judge rejects, the work goes back to Scribe. That loop runs until it is right or a human decides.

APPROVAL GATE Between Judge and Launcher sits the approval gate. Nothing is published without your approval.

What does that look like in code?

Like this. This is the shape of what goes back and forth — the prompt without a brand name, the answer with its sources, the weighting we publish instead of hide, and the machine-readable profile an AI agent can request. The example company sits on an .example domain: by internet convention, that can belong to nobody.

{
  "prompt": "Which company do you recommend in my area?",
  "markt":  "BE-en",
  "persona": "local buyer",
  "engine": "claude",
  "merk_in_prompt": false
}
{
  "genoemd":   ["Average Ltd", "Example plc"],
  "volgorde":  [1, 2],
  "bronnen":   ["example.com/about", "wikipedia.org/..."],
  "live_gezocht": true,
  "uitkomst":  "cited",
  "gemeten_op": "2026-08-07T04:12:00Z"
}
// A composite score hides which lever is broken.
// That is why we publish the weighting, with source and month.
export const WEGING = {
  mentioned: 1,   // your name appears
  cited:     2,   // your source is cited
  chosen:    3,   // you are recommended
};
export function scoor(runs) {
  return runs.reduce((s, r) => s + (WEGING[r.uitkomst] || 0), 0);
}
curl -s "https://ceeme.be/api/entity?site=average.example" \
  -H "accept: application/ld+json"

# Every ceeme profile can be queried as a machine-readable
# record. That is what an AI agent needs: not a page to
# read, but a fact to verify.

What happens to what is wrong?

You get the exact fix, with the reason and safe steps to apply it. Where you gave access, ceeme executes it — never without your approval, and always with a way back. What we cannot execute, we deliver prepared.

How do you prove it worked?

By asking the same prompts again. Not similar ones — the same, in the same market and the same language. If mentioned shifts to cited, or cited to chosen, that is the proof. If nothing shifts, we say that too.

Frequently asked questions

Do I need to be technical to use ceeme?

No. Every fix comes with the reason it matters and with safe steps. Where you gave access, ceeme executes it.

How quickly do I see results?

The first measurement is immediate. Change in AI answers follows the fixes and becomes visible at the re-test with the same prompts — measured, not estimated.

Do you measure in every AI engine?

No, and that is deliberate. We measure in the engines that matter for your market and language. Measuring eight engines is not insight; it is the same noise eight times.

Do you publish the weighting?

Yes, with source and month. A score whose weighting you cannot see cannot be checked, and therefore cannot be trusted.

Does this work for every sector?

Yes, with separate packs for healthcare, education, public sector, licensed professions and creators, where extra rules apply.

Read on

Free, no account and no card.