How to prove what was published on a website — before it changes or disappears

The core problem

Online content is fluid. Pages are edited, prices change, posts are deleted, and entire sites disappear.

When a dispute arises later, the critical question becomes:

“How do you prove what was actually published at that time?”

Why checking the website later does not work

Many people assume they can simply revisit a website if needed. That rarely works.

• the content may be edited
• the page may return a different version
• the URL may redirect or vanish
• the site may be taken offline entirely

Once the content changes, the original state is usually gone forever — unless it was preserved at the right moment.

The screenshot trap

Screenshots are the most common reaction. They feel immediate and intuitive.

Unfortunately, screenshots alone fail to answer key questions:

• When exactly was this taken?
• From which URL?
• Was it publicly visible?
• Has the image been altered?

In serious reviews, screenshots are often treated as illustrative — not authoritative.

What “proving publication” actually means

To prove that something was published, you must establish four facts:

• Content: what was shown
• Source: the exact URL and context
• Time: when it was visible
• Integrity: that the record was not changed later

Missing any of these weakens the claim.

The moment principle

The most important rule is simple:

You cannot prove the past retroactively.

Evidence must be created at — or very near — the moment the content exists. Everything else is reconstruction.

How tamper-evident capture solves the problem

A tamper-evident capture preserves not only the visual content, but also the context in which it existed.

• the exact URL
• a verifiable capture time
• cryptographic fingerprints of the content
• records that allow later verification

If the website later changes or disappears, the preserved record can still be independently verified.

Real-world situations where this matters

• pricing or terms changed after a transaction
• public statements later edited or denied
• policy pages modified during disputes
• false or misleading claims removed quietly

In each case, timing is everything.

The practical workflow

1. Identify the exact page that matters.
2. Capture it immediately, while it is live.
3. Preserve a tamper-evident record.
4. Archive the evidence for later verification.

This approach shifts the burden from memory and screenshots to verifiable records.

The takeaway

Websites are not static records. They are mutable interfaces.

If something matters, it must be preserved before it changes — not after.