Gemini

Google's official help describes the user-facing Sources mechanism: sources related to an answer can be shown and opened for further checking. That documents an interface and a user action, not the complete search pipeline.

This profile records what can be observed: whether an answer appeared, whether a Sources control or list was present, and which titles and URLs were displayed. It does not invent hidden signals, weights, or processing order.

Section sources:[1] Google Gemini Help

A link in Sources is a page Gemini offers the user for checking. Save the visible title, the exact URL after following it, the date, and the answer claim to which it appeared to relate.

A link does not necessarily support the whole answer. Compare each claim with the page content; if the source is merely topical, label the relationship as weak or unsupported.

Section sources:[1] Google Gemini Help

The documented user flow is useful as an audit procedure: open the sources, read the original page, and check whether the answer changed its meaning while summarizing it. Capture the answer before navigating because the interface may change.

Log four separate observations: a link was shown, it opened, the source supported the claim, and a user continued to the site. They are not one combined citation metric.

Section sources:[1] Google Gemini Help

When the interface offers material similar to or different from the answer, treat it as a navigation layer for checking. It can broaden reading, but it is not a statement that a page ranked better or was selected as proof.

Compare the meaning, date, and scope of each item. A “similar” label does not replace reading and does not show that every displayed page was used to generate the answer.

Section sources:[1] Google Gemini Help

Use a fixed question set, language, region, device, and date. For every run, save the full answer, the Sources state, URLs, a screenshot or export, and the page identifier.

Repeat the test at regular intervals and do not change the site and question set at the same time. Compare a URL's display share only within the same sample; one answer is not a trend.

Section sources:[1] Google Gemini Help

Server logs can show a request, user agent, verified network information, status, response time, and delivered HTML. They help assess technical availability, but do not prove that Gemini displayed the page to a user.

In particular, no request is not proof of no citation: a page may have been indexed or obtained through another layer. Conversely, a bot request is not retrieval or an answer mention.

Section sources:[1] Google Gemini Help

A minimum report should separate availability, display in Sources, exact claim support, brand mention, referral, and repeatability. State sample size, period, language, and missing observations beside every rate.

Do not call AI readiness actual AI visibility. Even a stable increase in a small sample does not establish causality, ranking, or future traffic without a controlled experiment.

Section sources:[1] Google Gemini Help

The practical publishing lesson is simple: write for human verification, make claims checkable, keep canonical URLs stable, and cite primary sources. This is an operational hypothesis about auditability and citation, not a Gemini promise.

In every publication, separate an interface observation from an inference and a hypothesis. If Sources points to material that does not support the claim, correct the wording and record the case in Corrections instead of assigning intent to the system.

Section sources:[1] Google Gemini Help