Colquhoun.AI
← All guides

Research Guides

Cite the Returned Web Capture, Not the Requested Date

· Colquhoun.shop editorial

An archived web page can answer a historical question, but a date entered into an archive is not necessarily the date of the page it returns. Before citing a past price, policy statement or research claim, make the capture date part of the evidence rather than assuming the archive found an exact match.

This worksheet concerns public web research and an invented example. It does not claim that Colquhoun.shop provides archive access or that every archive exposes the same protocol.

1. Keep the requested and returned times separate

RFC 7089's Memento framework describes Accept-Datetime as the desired date and time sent to a time-negotiation endpoint. The returned Memento-Datetime describes the archived state supplied by a compatible service. The framework also provides a link relationship identifying the original resource.

The service chooses among available captures. RFC 7089 notes that the returned date can differ substantially from the requested one, depending on what is available. An archive that does not implement the framework may instead identify captures in its interface. Record whichever actual capture evidence is available; do not invent a missing header.

2. Ask what the capture actually supports

Imagine an editor investigating which support wording a fictional vendor displayed on June 10. The archive returns a June 13 capture that says “weekday support.” A separately retrieved June 7 capture says “daily support.” Both show the same original page address.

A supported sentence is: “The June 7 capture shows ‘daily support’; the June 13 capture shows ‘weekday support.’ I did not verify the wording on June 10.” The captures do not establish the exact edit time or rule out other wording between them. A date-selection widget set to June 10 cannot fill that gap.

If the article only needs a documented older example, one clearly dated capture may suffice. If a conclusion depends on the specific date, seek a dated publisher record or other independent evidence. If none can be verified, keep the gap visible in the published note.

3. Keep a capture ledger

Do not substitute the current retrieval time or a date printed in the original article for the archive's capture time. They answer different questions. When comparing dates across zones, record the date and time before converting them for display.

4. Inspect the relevant content, not just the archive wrapper

RFC 7089 explains that an archive replay may differ byte for byte from an earlier original response, for example if links were rewritten or a banner was added. Check whether the exact passage is visible. If the relevant price or policy was loaded by a missing script, the page shell does not confirm the value.

Do not count a missing replay element as evidence that it was absent from the original. Replace that assumption with a narrow observation, such as “the capture replay did not show the price widget.”

5. Cite the dated evidence

Keep the original address and the capture link next to the statement, and state the capture's date in plain text. Another editor should be able to tell what was observed without reproducing the same archive search. This verifies the evidence boundary, not the claim that the publisher's archived statement was itself accurate.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.