TopClick SEO Expert
Keep comparison groups separate
Dmytro Nasyrov PhD
A report can use the same query ID after its wording changes. That stable label does not make the new observation answer the old question.
Before comparing visibility, record whether prompt text, intended audience, market or language changed. This proposed register separates revisions rather than hiding them inside one trend.
Version 1 asks about a supplier for a ten-person team. Version 2 asks about a supplier for a hundred-person team. This is a fictional change in the decision context.
Retain both exact prompts. Start a separate comparison group for version 2 unless the report explicitly explains a different comparison method. No AI answers were collected for this example.
| Field | Purpose |
|---|---|
| Query ID / version | Keep family identity and exact revision |
| Exact prompt | Preserve wording, not a paraphrase |
| Audience / task | Record who the query is for |
| Market / language | Keep observation scope visible |
| Comparison group | Specify which observations may be compared |
| Record | Fictional comparison scope |
|---|---|
| Q-18 v1 | Ten-person buyer; group G-18A |
| Q-18 v2 | Hundred-person buyer; group G-18B |
| Market / language | Same in both illustrative records |
| Observed answers | NONE COLLECTED |
| Reporting decision | Do not label the group change as a measured gain |
The same prompt can still produce different answers. Preserving wording supports a comparison protocol; it does not make engines deterministic.
Record the capture date and engine alongside the agreed conditions. Treat changes in the observation setup as separate metadata, even when the prompt stayed the same.
Keep a replacement log linking the retired prompt to its successor. Record the reason and date without rewriting earlier captures.
A report may explain the coverage of the current query set separately from the trend for unchanged queries. The chosen method must say which group and period each conclusion describes.
Ask the receiver to locate the exact prompt behind one reported comparison. They should be able to identify its revision and comparison group without guessing.
TopClick agrees query quantities and scope per platform in the proposal. A changed query set should remain visible in the evidence delivered under that agreed scope.
Google Search Central explains Google AI feature eligibility and reporting; it does not validate this proposed cross-engine comparison register. The versioning decision is an editorial measurement proposal.
Q-18 and its groups are fictional. No engine collection, client visibility result or statistically controlled experiment was performed. A preserved prompt alone does not establish causal improvement.
A useful trend states which question stayed comparable and which question was replaced.
Written by Dmytro Nasyrov PhD, software architect with 24 years of production experience. Dmytro is the CEO of TopClick.