Service AI visibility diagnosisSite readabilityContent and sourcesMonitoringPricingCasesFAQHow an engagement runs
Platforms DeepSeekERNIE BotKimiDoubaoTencent YuanbaoTongyi QianwenWhy report them separately
Industries Legal servicesHealthcareEducationIndustrial equipmentBusiness services / B2BLocal servicesConsumer electronicsSkincare and cosmeticsWhat actually differs by industry
Resources Learning centreBlogGEO glossaryComparisonsFAQ
Free toolsPartners
About About DaleGEOContact us
Start free trial
GEO Service

Monitoring and re-measurement

The step most vendors skip, and the only one that proves anything.

Generative answers vary between runs. That variance is exactly why a fixed method matters: without one, any movement can be presented as an effect and any lack of movement can be explained away.

Our reporting is deliberately narrow: three metrics, the raw answers behind them, and what changed since last round. Short reports are harder to hide a weak method inside.

What you get

What is actually handed over.

Everything listed here is a thing you can look at, not a status update.

01

Three metrics

Mention rate, share of voice, and source coverage — reported per platform.

02

The raw answers

Every answer kept verbatim. You can check any number against its source at any time.

03

Change from last round

What moved, what did not, and the most likely reason for each.

04

Context breakdown

Positive, neutral and negative mentions counted separately. A negative mention is not a win.

How it runs

Four steps, in this order.

Order matters — each step produces what the next one needs.

01 Re-run unchanged Same questions, same conditions, same number of runs per question.
02 Count symmetrically Identical matching rules for your brand and competitors; questions that name your brand in the prompt are excluded.
03 Separate what varies Web-enabled and non-web-enabled results reported separately, not averaged.
04 Review together A call per round, walking through what changed and what the next round targets.
FAQ

Questions teams ask before they start

How often should re-measurement happen?

Monthly suits most engagements. More frequent runs get lost in the natural variance of generated answers; less frequent and you cannot correct course in time.

What if the numbers go down?

We report the drop and what most likely caused it — a model version change, a competitor placement, a source that went offline. Reporting a drop is the point of measuring; a method that can only produce increases is not measuring anything.

Can we see the raw answers ourselves?

Yes. Every answer is kept verbatim and provided with each round, so any figure in the report can be traced back to the text it came from.

What does a report look like?

Two pages: three metrics per platform, the change against the previous round, the three questions that moved most with the most likely reason for each, and the context distribution reported separately from the totals.

Is there a dashboard?

Not as part of this stage. Reporting is delivered as records you can check rather than as a live figure, because a number without the answer behind it cannot be verified.

What if a model version changes mid-round?

It is recorded and stated in that round's report. A round spanning a version change is not comparable in the usual way, and we do not attribute its movement — in either direction — to the work.

Can we run the re-measurement ourselves to check?

Yes, and the method is published in full for that purpose. Run the same frozen set under the same conditions; where your numbers and ours diverge, the raw answers from both sides show which step differs.

Find out where your brand actually stands in AI answers.

An AI visibility diagnosis across the platforms your customers use, on your real questions. No charge for the first look.