← The journalMEASUREMENT / FIELD GUIDE

When AI answers change, what should you do?

Separate collection problems, sampling variation, product changes, and lasting visibility shifts before changing strategy.

Stockholm street and car with directional camera-motion blur.MEASUREMENT / SUNDIAL
Photography: Danial / Unsplash ↗ · Sundial motion treatment
THE PRACTICAL TAKEAWAY

Investigate a movement before explaining its cause.

A changed answer is an observation

A brand disappearing from one answer can feel urgent. It is still one observation. The question, conversation context, available sources, product behavior, and collection method can all affect what you receive. Treat the result as a reason to investigate rather than immediate evidence that a content change failed.

Retain complete answers from repeated observations. A percentage alone cannot tell you whether the brand vanished, became an unlinked mention, moved lower in a list, or appeared under a different product name.

Check the collection first

Confirm that scheduled requests succeeded and that the same question version, market, language, and product surface were used. Review any parser changes. A new rule for detecting citations or aliases can move a chart even if the underlying answers remain identical.

Keep a change log for both marketing work and measurement work. Include page releases, crawler-rule updates, prompt-set revisions, and provider or collection changes. When a trend breaks, this log gives you competing explanations to test.

Compare the affected slices

Look for concentration. Did the shift affect one topic, one engine, one geography, or the entire panel? Compare cited pages in the changed answers with earlier observations. If only one category moved, a universal recommendation to rewrite the whole site is unlikely to be well targeted.

Choose monitoring frequency according to the decision. A major product launch may justify closer observation; an evergreen explanatory page may not need repeated intraday checks. More collection can help describe variability, but it does not turn a changing system into a deterministic one.

Set an escalation rule

Define what warrants action before you see the next dip. For example, your team might investigate a recurring loss across several scheduled runs on a commercially important question group. The number of runs and materiality threshold should reflect your data volume and risk, not a universal industry rule.

Publish a short incident note: what changed, where it changed, what you ruled out, and what remains uncertain. If the evidence points to an inaccessible page, fix it. If it points to a changed answer preference, run a narrower experiment. If the evidence is thin, keep observing.