Skip to content
An independent documentation journalEvidence before opinion →
⌕
Knowledge / CT RESEARCH DESK

When a Product Page Changes: Preserve the Source Record

Keep the original URL, model context, access date and a checked preserved copy when a product page changes.

Original editorial illustration by CanineTutors Index.
READING LENSEditorial context
EVIDENCE STATUSMethods, sources & limitations
NEXT USEFUL STEPExplore the glossary ↗

A useful source record keeps the original product-page address, the exact model and market, the passage you relied on, your access date, and a checked preserved copy where one is available. Keep the live link too. An archive helps readers recover what you saw; it does not establish that the product claim was correct.

This guide concerns public documentation, not hands-on testing. It applies when reading a model file for Geek Bar, Alibarbar or Foger, as well as other changing product websites. A new page layout, missing paragraph or broken address is a reason to inspect the record, not a reason to invent an explanation. Our editorial standards describe that distinction.

Start with the claim you actually need

Before saving anything, write one sentence explaining why this page matters. Perhaps it identifies a model version, gives a specification or links to an instruction document. Keeping that question narrow makes the later check useful. A saved homepage is a poor substitute for a missing model page when the disputed wording appeared only on the model page.

Record the full name as displayed, including any suffix. Add the language and the stated market when present. If neither is identified, record that absence. Do not fill the gap from a reseller listing or assume a neighbouring model shares the same configuration. The model finder keeps individual records separate for this reason.

Blank documents, notebook and index cards arranged on an archival research table
Generated editorial illustration of a source-record workflow; not a photograph of collected evidence.

Keep a small record beside the saved page

The record should survive a change of software. Plain text or a simple table is often enough. Put the following fields beside the capture instead of relying on a filename such as final-page-new. A second reader should be able to work out what was collected without asking the original researcher.

Field What to record Why it matters
Original address Complete URL and final destination after a redirect Connects the record to the source
Identity Publisher, page title, model, version, language and market Limits which item the record describes
Dates Visible publication or update date, access date and archive capture date separately Avoids treating different events as one
Relevant passage A short attributed extract or precise section reference Shows what the citation supports
Preserved copy Archive URL or local file reference and inspection note Makes later checking possible
Limits Missing images, failed downloads or unavailable context Prevents overstating completeness

Provenance involves the object, the people or organisations and the processes behind it. The W3C PROV primer offers that broader framework. You do not need to implement its technical model to keep an orderly research note. Its useful lesson here is to distinguish the publisher of a page from the person who captured it and the writer who interpreted it.

Use an archive, then inspect the result

The Internet Archive explains how to browse existing captures and save a particular page in its Wayback Machine guide. A single saved page is not a complete website backup. Some resources may be missing, and following links can move you to another capture date. Check the displayed address and timestamp after navigating.

Open the preserved page yourself. Find the actual passage, inspect any relevant image and try the document link on which your note depends. If a specification is visible only inside an image that was not preserved, the surrounding page cannot supply that missing specification. Write down precisely which part failed.

Perma.cc is another preservation service. Stanford Law Library’s Perma guide walks through creating and checking a record; account and usage conditions apply. A service returning a link is the start of verification, not its conclusion. No preservation account is required to understand the workflow in this article.

Separate the dates before describing a change

A page might display an update date, while an archive has its own capture timestamp and your notebook has an access date. Preserve all three when available. If the page has no date, say so. An old archive capture can show that wording was present in that capture; it does not by itself tell you when the publisher first introduced it.

Imagine a hypothetical model page captured on Monday with a paragraph present and on Friday without it. Those observations support a difference between the two available records. They do not establish the exact hour of the edit, its author or its reason. Describe the observation and the interval rather than attaching an invented story.

This is also why a newly noticed difference should not automatically become a correction to a product fact. First ask whether both records concern the same model and market. Then check whether the wording was moved to a linked document. Our guide to specification context covers the identity and method questions that remain necessary.

Two archival folders and a magnifying glass on a green desktop
Generated editorial illustration. Keep the earlier and later record separate when comparing a change.

Compare records without rewriting history

Keep the original saved file intact and make comparison notes separately. Label your working copy clearly. If you annotate a screenshot, retain an unannotated version and describe the added marks. A highlight is your interpretation of importance; it was not part of the publisher’s page.

Use a short comparison log: field, earlier wording, later wording, source addresses, observation dates and consequence for your article. Sometimes the consequence is simply that a citation now needs a new destination. Sometimes a sentence must be narrowed because its original support is no longer recoverable. Neither outcome requires declaring a product improved or worsened.

For scholarly sources cited alongside product documentation, the publication’s update status matters too. Crossref’s versioning guidance describes how corrections and retractions relate to the scholarly record. That system should not be assumed to exist on an ordinary brand page. Look for the publisher’s actual notice rather than inventing a formal version history.

Write a citation that another reader can use

Include the publisher, title, original URL, the relevant page date if shown, your access date and the preserved-copy URL. State whether you checked the live page, the archive or both. When only a section supports your statement, name that section. A citation to a whole domain leaves the reader with avoidable detective work.

Keep the explanation proportionate. A note such as “Archived copy checked; instruction download unavailable” is more useful than claiming the source is permanently secured. If you cannot recover a passage, say that the earlier wording remains unverified. The source directory offers a starting point for primary sources, and the corrections policy explains how the index records material changes.

Frequently asked questions

Is a screenshot enough?

It can preserve a visible passage, but keep its URL, date and context separately. A cropped image alone may omit the model, market or surrounding qualification. Retain the wider view when practical and record what your crop leaves out.

Does an archive confirm the manufacturer’s claim?

No. It preserves available content. Product performance still requires appropriate evidence, and documentation alone is not a physical test. Saving a page does not turn a published statement into an independently measured result.

What if no archive exists?

Keep the live address, access note and any permitted local record. The University of Idaho web-archive guide also outlines ways to explore available captures. Mark the unavailable preserved copy clearly. Do not supply an archive link that you have not opened or imply that an unsuccessful capture succeeded.

Should the original live link be removed after archiving?

Usually keep both for research purposes: the original identifies the source, while the preserved copy identifies the version you inspected. Recheck each before relying on it. If the live destination changes, explain that change instead of silently substituting a different source.

End of this record.

Keep the source, method and limitations together.

Visit the source directory →

Take another path.

All stories ↗