Schema sold as the answer
The pitch is usually structured data. No search vendor has ever stated that its AI reads FAQ markup, and the most-cited research on AI citations never tested schema at all. It tested writing.
Most answer engine optimization is sold on a story. We start by counting where four AI engines cite you today, run the work, and count again every month. You see movement or you see us change the plan.
The pitch is usually structured data. No search vendor has ever stated that its AI reads FAQ markup, and the most-cited research on AI citations never tested schema at all. It tested writing.
Plenty of tools watch ChatGPT and stop. Your buyers are also asking Perplexity, Gemini and Claude, and the four disagree with each other constantly about who to name.
Without a count taken before the work began, no improvement can be demonstrated afterwards. The engagement ends in adjectives, and nobody can say whether the money did anything.
We ask four engines the questions your buyers ask, repeat each one to filter out the noise, and count how often you are named and who gets named instead. That number is the contract.
ChatGPT, Perplexity, Gemini and Claude, re-run on the same prompts on the same cadence. Where an engine is too unstable to claim movement, we say so rather than reporting the wobble as progress.
Questions your buyers actually ask, answered in the first two sentences under the heading. Passages short enough to lift. Sources behind figures. Markup kept because it earns its keep in ordinary search.
A run across four engines on the questions that matter to your market, repeated for stability. It returns your share of answers, the competitors named ahead of you, and the questions where nobody is named yet.
The pages that should be cited, rewritten to be quotable: question headings, answers directly under them, short self-contained passages, and a source behind every figure.
Schema per page type, an llms.txt that resolves, clean semantic structure, and no broken internal links. It will not win a citation on its own, and its absence can cost you one.
The same panel re-run and reported beside rankings and AI-referred sessions. One document, written so it can go upward without being rewritten first.
Every figure below is one client's August run: 14 buyer questions, each asked three times of four engines, 168 answers. The client is not named here; the numbers are exactly as the panel returned them.
The same fourteen questions, asked of four engines in the same week, produced a 24-point spread. Perplexity cited this client in nearly half its answers. ChatGPT cited them in under a fifth.
That is the whole argument against a single-engine tool. A dashboard watching only ChatGPT would have reported this client as a laggard. A dashboard watching only Perplexity would have reported them as a leader. Both would have been describing the same fortnight.
It is also why the work is prioritised per engine rather than run as one undifferentiated content push.
A share figure on its own says nothing. The question a board asks is who is being named instead of us, and by how much.
In the August run this client was cited in 52 answers against AlphaSense's 50, having been behind in every previous run. That is a sentence with a number in it, which is the only kind worth putting in a report.
The same panel names every company an engine cited instead of you, so the competitive set is measured rather than assumed.
Ask an engine the same question three times and it will not always give the same answer. We measure that directly: stability is how often an engine repeated itself across its three runs.
Perplexity repeated itself every time. Gemini agreed with itself on fewer than three quarters of questions. So a Gemini figure that moves five points between months has not necessarily moved at all, and we say so in the report rather than banking it as progress.
Most tools in this category report the number and stop. The stability column is the difference between a measurement and a screenshot.
We agree the fourteen questions your buyers actually ask, run them three times across all four engines, and hand back the baseline: your share, the companies named instead of you, the questions nobody owns, and the stability of each engine. Nothing is changed on the site this month. The number has to exist first or nothing afterwards can be proven.
The baseline names the questions where you lose. Those pages get rebuilt to be quotable: the question as the heading, the answer in the first two sentences under it, passages short enough to lift whole, and a source behind every figure. In parallel the technical layer gets fixed, because an engine that cannot cleanly separate your content from your navigation has nothing to quote.
The same fourteen questions, the same three runs, the same four engines. Movement against the baseline, per engine, with the unstable ones flagged rather than counted. This is where the engagement either shows a result or shows us that the plan needs changing, and both of those are reported.
From month four the cycle repeats monthly, and the report carries the trend rather than the snapshot.
No search vendor has ever stated that its AI reads FAQ markup, and the most-cited research on AI citations never tested schema at all. We keep structured data because it still earns rich results in ordinary search. That is the honest reason, and it is the one we give.
Engines re-crawl and re-index on their own schedule. First movement usually shows in the second or third monthly run. Anyone quoting you a number of weeks is describing something that is not theirs to promise.
Where an engine is too unstable across its own runs to support a claim, the report says so. A figure that moved inside the noise is not a result, and putting it in a deck is how a programme loses the room six months later.
If there are ten pages and no publishing cadence, the content has to exist before an engine can quote it. That is a different engagement and we will say so on the call rather than three months in.

ChannelSight is named in 34 of 168 AI answers across four engines, more than MikMak, Wayvia and Pear together. Every one of those numbers comes from our own monthly panel run.

It gets your company named in the answers AI engines give, and proves the change. In practice that means measuring where you are cited today across the engines your buyers use, rewriting the pages that should be quoted so they can be, fixing the technical layer that stops an engine reading you, and re-measuring on a fixed cadence.
SEO competes for a position on a results page. AEO competes to be the source an engine quotes when it answers instead of listing. The underlying work overlaps heavily, which is why running them as separate vendors wastes money, but the target and the measurement are different.
Generative engine optimization and answer engine optimization describe the same work. GEO is the term the academic research uses, AEO is the term the industry settled on. Anyone selling them as two services is selling the same thing twice.
We ask each engine a fixed set of buyer questions, repeat each question so a one-off answer cannot skew the result, and record whether you were named, who else was, and what was cited. Repeated monthly on the same prompts, that produces a trend rather than a snapshot.
Engines re-crawl and re-index on their own schedule, so first movement usually appears in the second or third monthly run. Anyone promising results in weeks is describing something they cannot control.
Yes, and the evidence points that way. The most-cited research on AI citations tested content changes, not markup, and found that adding quotations, statistics and sources lifted citation rates the most. We keep structured data because it still earns rich results in ordinary search. We do not sell it as the AI play.
B2B companies with a real content estate and a marketing team to work with. If a site has ten pages and no publishing cadence, the honest answer is that the content has to exist before it can be cited, and that is a different engagement.