Guides

How to measure an AI visibility change

A page can change and the answers can change. Those are two measurements. One does not prove it caused the other.

Keep the before sample

The report is a snapshot: the date, the engines, the questions and the coverage. A later scan is a new sample. Cached answers are not a fresh observation, and a comparable sample has to use the same questions, the same model, the same methodology and the same collection mode, or the comparison is between two different experiments.

Check the page separately from the answers

You can see whether a suggested edit is on the site by reading the page. A hash change confirms the stored bytes changed. It does not confirm the words a customer sees, and it certainly does not explain a change in mentions. You can see whether a later API answer names you by running the questions again. Those are two records and they stay two records.

What not to claim

Do not turn one before-and-after pair into a percentage uplift. Models, competitors and the rest of the web also change. A fix card is a hypothesis about the site, not a forecast of mentions. This is the discipline that separates a measurement from a marketing number, and it is the reason this page exists.

Why repeated sampling is the honest version

One measurement is an anecdote and two measurements are a line drawn through two points. Watching the same questions over time is the only way to tell a real movement from the noise a model produces by itself. ReplyScore does not currently sell a monitoring schedule that does this for you, so the practical answer today is to re-run the diagnostic deliberately rather than continuously.

Read next

Last reviewed 2026-11-08.