What actually makes an answer change?

Three forces drive it. Source changes: a directory edit, a fresh review wave or a new article alters what live-retrieval answers read, sometimes within days. Model updates: when a platform ships a new model version, answers drawn from memory can reshuffle overnight, including businesses that currently rank well. And ordinary variance: the same question asked twice can produce slightly different answers, because generation is not deterministic.

The three move on different clocks, which is why an answer can be stable for months and then flip without warning.

How volatile are recommendation answers in practice?

It depends on the question. Broad questions with many plausible candidates churn most, because small source shifts reorder a crowded field. Specific questions with few qualified businesses stay steadier. Teams that re-run fixed question sets month after month typically see a core of stable names with a rotating edge, and the edge is where businesses enter or vanish. For example, imagine a physiotherapy search in a busy district: two clinics might hold their spot most months while a third slot rotates between several candidates, often because of something as small as outdated business hours.

That pattern is the practical reason a Brand Mention Rate is tracked as a monthly trend rather than read from any single answer.

What does volatility mean for your business?

Volatility cuts both ways. The encouraging side: fixes show up fast. Corrected facts and new sources can move live-retrieval answers in weeks, so effort is visible within a quarter. The uncomfortable one: your current ranking is not permanent. A competitor who starts working their sources can enter answers you considered yours, and you will not notice without measurement. Businesses that check regularly catch these shifts. Businesses that do not, lose position without knowing why. It also resets opportunity on a schedule: every model update reshuffles crowded answers, and businesses with clean sources are positioned to win the reshuffle.

How do you manage it without obsessing?

Fix the cadence and the method, then relax. A stable question set, all four platforms, both languages, once a month, judged on the trend rather than single answers. Panic on one bad answer wastes effort; drift discovered six months late costs real customers. This is the working rhythm behind your overall AI visibility, and it is exactly what the monthly retainer automates after an AI Visibility Audit sets the baseline: same questions, native scoring in both languages, a monthly trend you can hold someone accountable to.

When a real drop does happen, resist rewriting everything. Read which platform moved, check the cited sources for what changed, fix that one thing, and wait a cycle. Panic edits create the same noise you are trying to measure through, and they make the next month's reading impossible to interpret.