Build the panel
Choose questions by intent: discovery, comparison, decision, verification and brand. Preserve exact wording.

GUIDE / PROTOCOL
Measure answers observed in a defined context without turning a screenshot into a visibility promise.
Direct answer
Use a stable question panel, date, identified interface, exact answer and links actually visible. Then compare accuracy, citations and change over time.
01 / Review method
Choose questions by intent: discovery, comparison, decision, verification and brand. Preserve exact wording.
Record date, country, language, interface, relevant settings and whether an account was used.
Separate brand mention, cited link, source actually used, answer position and factual accuracy.
Observe differences across engines and periods; inspect source pages, corrections and possible causes.
MEASUREMENT / VISIBILITY SOURCES
Appearing in an AI answer and receiving a website visit happen at different stages. Choose the signal that answers your question before comparing periods.
Crawling may make a page available for search.
A link can appear in an answer without receiving a click.
The site records an arrival within the limits of its measurement setup.
| Observation source | What is measured | Interpretation limit |
|---|---|---|
| Google · Generative AI in Search Console Official documentation | Link impressions in AI Overviews and AI Mode, with dimensions including page, country and device. | Days use Pacific Time (PT). Property totals can differ from the sum of page rows because of aggregation. |
| Bing Webmaster Tools · AI Performance Official documentation | Visible citations and cited pages in supported AI experiences; grounding queries are grouped. | A citation is neither a click, a ranking nor a measure of page importance. Grouped queries do not reproduce individual prompts. |
| Website measurement | Arrivals and actions recorded under your measurement configuration. | An attributed visit does not represent every impression. Missing referrers or blocked measurement limit attribution. |
| Documented question panel | Citation presence and fidelity across a set of observed answers. | The result depends on questions, mode, language and date. It does not describe all users. |
Google AI report impressions are included in the Search Console Web scope: do not add them to the Web total. Compare visibility, citations and visits separately.
Compare the scope of two observationsDocumentation accessed on .
MEASUREMENT WORKSHOP
Count answers citing the target domain separately from references whose contents support the claim. One answer can contain several links, so the two rates have different denominators.

Fictional example · no measurement of this site or a client
| Indicator | Calculation or threshold | What the result establishes |
|---|---|---|
| Presence in answers | 12 / 40 × 100 = 30 % | 12 of 40 answers cite the domain: 30% presence in this sample. |
| Support among checked references | 15 / 20 × 100 = 75 % | 15 of 20 references support the claim: 75% of checked references. This says nothing about unchecked references. |
Keep questions, language, service, mode, dates and repetitions. Include answers with no citation.
Match the exact passage to the claim; record inaccessible links and citations that do not support it.
A change requires the same panel and protocol. Publish counts and exclusions too.
Of 30 attempts in one programme, 20 answers are readable and 12 cite the target. The other 10 results remain unclassified.
| Observed unit | Fictional data |
|---|---|
| Attempts / readable answers / citations | 30 / 20 / 12 |
| Rate among readable answers | 12 / 20 = 60 % |
| Bounds across all attempts | 12 / 30 = 40 % ; 22 / 30 ≈ 73.33 % |
60% applies to the 20 readable answers. Across 30 attempts, possible assignments of 10 unknowns give about 40–73.33%. This descriptive range is not a confidence interval.
Documentation consulted on .
02 / Evidence to keep
ID, exact wording, intent and check frequency.
Text, capture, interface, language and context.
Clickable URL, accessible page and actual support for the claim.
Error, absence, entity confusion or uninterpretable variation.
PRACTICAL CHECK
A frequent misreading and the check that helps avoid it.
A single citation proves neither stable visibility nor system preference. Answers, models, languages and interfaces can vary.
Repeat a fixed query panel, record settings and date results. Separate presence, accuracy, source links and any actually observable traffic effect.
AFTER THE REVIEW
Count presence, not a citation. Keep the answer and check separately whether facts are accurate and assigned to the right entity.
Rerun the same questions in the same context at several times. Record variability before attributing the change to an edited page.
Decision and review trail
What the check must help decide and what to retain so the choice can be reviewed.
Keep a fixed query set, languages, dates, services, full answers and cited links. Measure appearance, accuracy and verifiable citation separately.
Correct false information under your control. Repeat the observation after the fix without calling one answer a trend or visibility guarantee.
Typical situations for preparing a check. They do not describe completed assignments or actual observations.
Compare recorded model identifiers, modes and interfaces across campaigns.
Separate periods before and after the change; repeat a control panel rather than attribute every difference to the site.
Displayed version, control questions and transition dates.
Separate no citation in a readable answer, generation failure and unavailable service.
Count valid observations separately from unavailable attempts; access failure is not an observed missing citation.
Attempts, readable answers and exclusion reasons.
Open the cited destination and locate support for each studied claim.
Separate citation presence from genuinely relevant evidence.
Query, answer, consulted URL and passage correspondence.
These questions complement the method. They help establish what is actually supported while retaining qualifications in the record.
Do before and after records use the same question panel, language, context and collection protocol? Separate site changes from engine variation.
Fictional example: the state applies only to the criterion and scope described.
Is each cited URL accessible and does it support the attributed passage? Retain wrong citations and uncited answers, not only favourable results.
Fictional example: the state applies only to the criterion and scope described.
Are inaccessible or unreadable answers separated from missing citations? Report counts and the denominator rule.
Documentation consulted : NIST · AI Risk Management Framework ·
Fictional example: the state applies only to the criterion and scope described.
TOOLS / REGISTERS
Count citations only within the observed panel. Retain the number of answers, answers without citations and repeated runs before calculating any proportion.
03 / FAQ
No. Google Search does not use it, including in its generative features. For other systems, check their documentation and observed use: having the file demonstrates neither retrieval nor citation.
Yes as brand presence, but it must be separate from a verifiable citation.
Enough to cover decisive intents; a stable, reviewed panel is better than a large unverified one.
No. Keep exact question, language, date, interface and context, then repeat before interpreting a difference.
Separate link presence from claim accuracy. A visible citation may support a different statement.
04 / Official references
DEEPER READING / PRACTICE
The captures are collected through the water on various assistants. To get a useful reading of it, each observation must be linked to a protocol and an identifiable question.
Updated on .
Identify questions and executions. Keep the answer, sources, platform, language and conditions known, and then use a stable grid to classify the results.
A apparent evolution may come from a change of question or protocol. A missing answer and a lack of quotation are two distinct events.
The observation journal allows you to reconstruct each test and compare compatible series. The modifications of the protocol are recorded with their date and their effect on the interpretation.
EXAMPLE / READING THE NUMBERS
Fictional data illustrating the method; not client results or measurements of this website.
| Observation | Count | Interpretation |
|---|---|---|
| Panel questions | 40 | Fixed comparison base. |
| Answers mentioning the brand | 12 | 12 / 40 = 30% of the panel. |
| Answers describing the offer correctly | 8 | 8 / 40 = 20% of the panel; 8 / 12 ≈ 66.7% of mentions. |
These observations measure neither market share nor sales. A mention may be inaccurate. Report the panel, date, language and repetitions alongside the result.
PRACTICAL CASE / WORKED EXAMPLE
This pedagogical case shows how to qualify a research result or a generated response. It distinguishes the punctual observation, its verification and the conclusion that the test conditions actually support.
A source appears in a response and is no longer cited in the next test. The team doubts between a loss of visibility and a variation of the response generated.
Check question, platform, language and known conditions. Repeat according to a documented rule and compare the proposals and sources. Consider the changes made in the Protocol.
The observation is preserved as a variation of the tested series. A sustainable conclusion requires a compatible set of executions, without transforming two different answers into a general trend.
Choose a frequency related to the need and the changes that are sought. Documenting this rule and the exceptions allows you to interpret the series without confusing a more intensive collection with a real evolution.
DETAILED WORKSHOP / APPLICATION
Assemble the list of questions, execution identifiers and known conditions. Identify the formulation or platform changes that occur between the series.
Compare the exact questions before the results. Separate the versions of the protocol and keep the repetitions. Qualify the quotations with the sources and proposals associated.
If a new question improves the test but changes the intention, open a separate series. The ancient history remains useful with its scope and its initial formulation.
The series is consistent when comparisons indicate common conditions and differences. Protocol changes are visible in the same way as results.
Transmit a journal question, execution, answer and judgment. Identifiers make it easier to review a ranking without losing the relationship to original observations.
ANNOTATED WORKING DOCUMENT / REVIEW GRID
The journal combines question, version, execution, answer and judgment. It allows you to follow the quotes while distinguishing observed variation and modification of the test conditions.
On a small screen, scroll the grid horizontally to read all three columns.
| Observation | Supported interpretation | Next step |
|---|---|---|
| Questions and conditions are comparable. | Observations can be approached according to the defined categories. | Examine sources and proposals before describing the differences. |
| The formula changes between two series. | Some of the variation may come from the new protocol. | Open a separate version and keep the old series with its scope. |
| An isolated response is presented as a trend. | The staff and coverage do not support this generalization. | Repeat according to an explicit rule and qualify the unknown. |
The final verification verifies the identifiers and conditions before the graphs. Protocol changes must be visible as well as results changes to avoid misleading comparisons.
REPORTING / EXAMPLE WORDING
A new question formulation can open another series rather than silently extend the old one.
Name the versions and explain the dimensions that remain comparable.
Compared observations use the indicated version of the protocol. The results obtained after changing the question are kept in a separate series.