AI Citation Source URL Evidence Card

A cited URL needs a traceable identity before a reviewer accepts it as an owned source. Preserve the raw address from the saved AI answer, the destination observed during inspection and the evidence supporting the ownership decision. Keep an unresolved destination visible instead of assigning it from the link label.

This proposed ten-field card reviews one source link. The blank CSV and fillable PDF share the same field names. C-19 is a fictional example showing a link that leads to a different domain while the ownership review remains open. No AI answer or redirect was collected to create it.

Download the working files

Blank CSV · Fillable blank PDF · Fictional C-19 CSV

The blank files contain no example values. Use them within your own evidence-access rules. This page does not collect your answers or source records.

Fill the ten fields

1. record_id: Keep one ID for this source-link review. Link any later correction to the original entry.
2. engine_and_surface: Name the visible product and answer surface. Include the saved-answer reference; a source panel and the main answer are different locations.
3. query_variant_ref: Point to the exact prompt or query and its revision. Keep market, language and known session conditions with that reference.
4. observed_at: Record the source-link capture time with a timezone. Put the later destination-inspection time in its evidence packet.
5. raw_citation_url: Preserve the complete captured address before cleaning tracking parameters or applying a comparison form.
6. resolved_destination_url: Record the destination reached under the documented inspection conditions. Use UNRESOLVED when inspection cannot establish it.
7. redirect_evidence_ref: Link to the retained inspection record: time, method, intermediate addresses where available and outcome. A final screenshot alone may not expose each redirect.
8. ownership_relation: Record owned, third-party or unresolved under a named domain rule, with its evidence reference. An external-looking address does not settle control of a domain.
9. page_version_ref: Reference the saved destination content and its capture time. Keep page identity and content evidence together.
10. review_disposition: Record the decision, reviewer and next action. When evidence is missing, name its owner and leave the owned-source classification on hold.

The question reference and evidence references carry context that would make a single worksheet row too large. Keep those referenced files retrievable by the receiving reviewer. An inaccessible evidence pointer leaves the review incomplete even when every cell contains text.

Field order (the downloadable CSV contains the exact header):

record_id, engine_and_surface, query_variant_ref, observed_at, raw_citation_url, resolved_destination_url, redirect_evidence_ref, ownership_relation, page_version_ref, review_disposition

Follow the fictional C-19 link

In the invented answer capture, the visible citation points to https://answer.example.com/citations/C-19?src=fixture. The proposed inspection note says it leads to https://publisher.example.org/reviews/agency. These documentation-domain addresses are illustrative. They are not links from a real answer, and no request was made to test their redirect behavior.

1. record_id: C-19 (FICTIONAL)
2. engine_and_surface: FixtureEngine / source panel; ANSWER-C19-F1 (invented)
3. query_variant_ref: Q-C19-v1; English buyer question; all context fictional
4. observed_at: 2026-11-06T09:00:00Z (fictional capture time)
5. raw_citation_url: https://answer.example.com/citations/C-19?src=fixture
6. resolved_destination_url: https://publisher.example.org/reviews/agency
7. redirect_evidence_ref: E-C19-F1; fictional redirect note, not an HTTP capture
8. ownership_relation: UNRESOLVED; different destination domain in fixture; domain-control review pending
9. page_version_ref: PAGE-C19-F1; fictional destination text and inspection time
10. review_disposition: HOLD; data owner to review domain evidence; not accepted as an owned citation

The changed destination supplies a reason to inspect the ownership rule. It does not establish who controls that domain. C-19 stays unresolved until the data owner reviews the relevant domain-control evidence. A company name on the destination page would not by itself turn that publisher into a company-controlled source.

The disposition therefore remains HOLD. The row can still support a source-page investigation, with the captured address and proposed destination preserved. It has not been accepted as an owned citation.

Inspect a real link without overwriting its origin

Start from the complete saved answer and visible source list. Copy the raw citation URL exactly, including its path and parameters, and associate it with the answer reference. Keep any normalized URL in a separate comparison note. Replacing the raw field with a cleaned address would erase part of the original observation.

Inspect the destination using an authorized method and record the time and conditions. A browser navigation, an HTTP inspection and an exported provider result are different evidence sources. State which one you actually used. Preserve intermediate locations when the method reveals them. Do not reconstruct a missing redirect chain from the final page alone.

Google Search Central documents server-side redirects, refresh redirects and JavaScript redirects. Its guidance explains Google Search behavior. It is not a guarantee that every assistant or collection method resolves links identically. Save the behavior observed in the method used for this review.

If a login screen, access denial or redirect loop prevents a useful inspection, set the destination or page evidence to unresolved as appropriate. A failed inspection is not evidence that the citation points to no page. Record the limitation in the evidence packet and give the missing evidence an owner.

Then compare the observed destination with the approved domain rule. That rule should explain which domains and subdomains the review treats as company-controlled and what evidence supports the relationship. A hostname match is only useful under that declared scope. Redirect behavior and ownership remain separate questions.

Capture the destination page version that informed the decision. Include the inspection time and enough retained content to identify what the reviewer saw. If the destination changes later, create a linked review revision rather than silently rewriting the historical source URL or page reference.

Know what the card leaves open

A completed URL card records a bounded source review. It does not prove that the cited page supports every claim in the answer, that the source was selected for a particular reason or that a later answer will cite it again. Claim verification needs the relevant answer passage and source content beyond this identity record.

The card also supplies no visitor, lead or revenue measurement. Its ten fields are a proposed working format, not an engine's required schema or a statistically validated monitoring method. Keep unknown values explicit and retain the review rule when sharing an export.

When a team needs help defining that evidence handover, TopClick's AI search and GEO services cover agreed brand and competitor analysis, query scope, website recommendations and content work. Specify who reviews source ownership and what the deliverable must retain. This card is an editorial resource, not a claim that a client implementation or ongoing monitoring service has already been delivered.

‍

Sources and scope

• Redirects and Google Search, Google Search Central. Supports the distinction between a source address and redirect destination. It does not establish domain ownership.
• Example Domains, IANA. The C-19 addresses use documentation domains and imply no operating service.

Checked November 7, 2026. The workflow and card are proposed. The example is fictional.

‍