Colquhoun.AI
← All guides

Research Guides

Keep the Full Page Body When a Citation Check Returns 304

· Colquhoun.shop editorial

A 304 Not Modified in your audit is not a fresh copy of the page. It tells a client that it can reuse an existing representation. If you saved only the 304, keep looking for the earlier response whose body you actually reviewed.

Why two successful checks can tell different stories

Say an editor fixes the source link beneath a research chart. A teammate sends you a screenshot of a 304 from their browser and says the link is verified. They may have seen the correction, but the status alone cannot tell you that. Their browser might have revalidated a copy it already had. Without the earlier body, you have nothing to compare with the correction.

RFC 9110 explains the purpose of a 304: a qualifying conditional GET or HEAD can reuse the stored representation rather than receiving it again. The response does not carry the page body. An entity tag, when present, is a validator for a representation, not a publication date or a digest you should interpret yourself.

A two-request worksheet

  1. Capture a full baseline. Use a signed-out GET with no conditional headers. Record the requested URL, final URL, time, status, and the public request settings that matter, such as language. Save the response body and copy the exact sentence or link under review.
  2. Record any validator the server sent. If there is an ETag, keep its quotes and any W/ prefix. If there is no validator, say so rather than inventing one. Keep the request conditions with the capture so you do not compare unrelated variants.
  3. Recheck the same representation. On a public page you own or are authorized to review, repeat the request with the earlier entity tag in If-None-Match. A 304 lets a cache reuse its stored body. A 200 gives you another body to compare, but on its own does not prove a change: the endpoint may ignore the condition.
  4. Verify the editorial change in the body. Check the exact corrected link or sentence rather than relying on the response status. If you have only a 304, record “revalidated, body not inspected” and capture a full response before signing off.

Worked example: a citation under a chart

In this fictional example, Monday's full response links to the 2024 survey and has the entity tag "chart-a". Tuesday's conditional check with that tag gets 304. The saved evidence still shows the 2024 citation. Later, a full Tuesday response shows the 2025 survey link and provides a different entity tag. The changed link in that response is the evidence you can cite. The later tag helps keep your captures straight but is not the evidence of the edit.

A useful worksheet row reads: Chart citation | signed-out English | full GET 200 | 15:02 UTC | 2025 survey href confirmed | comparison: Monday 200 body. If the content still differs from what another visitor saw, log both request contexts instead of assuming the newest capture applies everywhere. This check does not establish that a search engine has recrawled or indexed the correction.

For the broader release checklist, see separating deployment, cache, and search evidence.

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.