How to cite a changing product page without making the note stale

To cite a changing product page, record what you observed, when you observed it, and which page state mattered for the claim.

A product page can change price, feature wording, availability, bundle terms, trial length, screenshots, supported countries, or plan limits while keeping the same URL. If a note only says “according to the product page,” the citation may look current even after the evidence has moved. The reader cannot tell whether the summary is stale or whether the source still supports it.

A better citation has four parts. First, name the claim being supported: price tier, feature availability, release note, support policy, or comparison point. Second, add the checked date. Third, record the source state, such as country, plan, device, version selector, currency, or logged-out view. Fourth, explain the part of the page that mattered. For example, “checked June 2026, US pricing page, Pro plan table, export limit row” is much clearer than a bare homepage link.

If the product page is important and likely to change, add a recheck trigger. That could be a pricing change, release announcement, annual renewal date, or the next time the note is reused. If the source later changes, update the note with a correction trail instead of pretending the earlier citation was timeless.

This keeps the note useful even when the source evolves. The citation becomes a dated observation, not a claim that the page will always say the same thing.

How to cite a changing product page without making the note stale

// COMMENTS

ON THIS PAGE