Question sets need versions, not silent rewrites

You can change a saved AI visibility question. The new wording may be better for the work you offer now. It is still a different measurement.

One changed word can alter the people an engine considers relevant. A locale can narrow the field. Adding a client type can turn a broad comparison into a fit question. If you overwrite the original question and draw a line from the old result to the new one, the chart suggests that one thing changed when several things may have changed.

Keep the old question set. Give the replacement set a new version name. Repeated scans can be compared within the new scope. Keep the earlier scope as a separate series.

See the break before you edit

Imagine a consultant's original saved question is:

Which independent Google Ads consultants can help a growing business in the US?

After several buyer conversations, the consultant changes it to:

Which independent Google Ads consultants can help a US B2B software company diagnose poor lead quality?

The second question may be more useful. It asks for a narrower buyer, problem, and type of help. It cannot be treated as the next reading of the first question. A different answer could follow from the wording alone, even if no public page changed.

Google says that search results can differ because of factors including time, location, language, device, settings, and recent searches. That guidance concerns Google Search, but it is a practical reason to retain scope when you record any AI-answer observation. Read Google's explanation of differing results.

Keep a version record outside the scan result

Gistful saves the selected question text with scan evidence and only compares scan history when the saved scope matches. It does not currently give your edited set a reader-facing label such as “v2” or retain a separate question-set version history for you. Make that record yourself when the wording changes.

Use a simple log:

The dates and prompts in this table are illustrative. Your log should contain your real question text, the country and language used, included engines, profile scope, and any methodology note. It can live in a worksheet, a project note, or the report that accompanies your scan.

What can stay in the same series

Keep a direct comparison only when the saved discovery question, locale, language, engine scope, profile context, and collection method match. If an engine failed or returned no answer in one scan, compare the matching completed checks and show the gap. A thin returned answer remains part of the evidence and may simply have no confirmed mention. Do not turn an unavailable answer into a non-mention.

These edits start a new baseline:

• You add a name, employer, or biography detail to a discovery question.
• You change the client type, service, problem, or decision.
• You change country or language.
• You add or remove an engine.
• The collection method changes in a way that alters what the result means.

Preserve the old wording even for a punctuation fix. A reader should not have to trust your memory to know what you measured.

Annotate the report in plain language

Use a note a client can understand. For example:

The October and November observations use the same saved discovery questions, US English locale, four-engine scope, and collection method. They can be reviewed as one series.

Or:

The December observation starts a new series because one question now asks about B2B software lead quality. It is shown beside the prior series, not as a gain or loss from it.

The note tells the reader what changed and prevents a convenient but unsupported causal story. Gistful's published baseline study keeps the same separation between saved evidence, parsing, and interpretation.

Before you edit, copy the current questions and scan scope into your record. Save the revised questions as a new set, then compare future rescans only within that revised scope.