Journalists: Archive Sources That Won't Rot

A web source is on the record until it suddenly is not. The company edits the blog post after publication. The press release moves behind a new CMS and loses its old URL. The local news site that broke the story shuts down. The page is fine at 9 a.m. and rewritten by lunch — and your quote is in a published story that points at the live URL.

This article is about the professional version of the problem: what a newsroom-grade source archive needs to contain, and a concrete workflow for it — save the source, organise by story, search across everything, and hand your editor a link to the exact copy you saw.

What actually happens to sources

The phenomenon is easy to describe without exaggeration, because it has been measured. A Pew Research Center analysis from May 2024 found that 38% of webpages that existed in 2013 were no longer accessible a decade later, and that 23% of news webpages contain at least one broken link. A quarter of all pages that existed at some point between 2013 and 2023 are gone.

Not every loss is a deletion. Sources also rot while technically surviving:

• Quiet edits — a page is updated after publication, and the sentence you relied on is rewritten or gone.
• Paywalls and region blocks — the page loads for you today and for no one you send it to tomorrow.
• Redesigns and migrations — the URL changes, and redirects die at the next replatforming.
• Takedowns and shutdowns — legal complaints, corporate PR cycles, and small sites going dark all remove pages entirely.

When any of these happens to a source in your story, the failure is not abstract: the quote becomes unverifiable, the editor asking "where did this come from?" gets a shrug, the fact-checker stalls, and if a subject disputes your characterisation of a page, you have nothing to show. Your citations are only as strong as the worst thing that has happened to their URLs since you reported the story.

What a source receipt has to do

Before the workflow, the requirements — because a screenshot on your phone does not meet them:

1. Faithful. The words, images, and layout come back the way the page looked when you saved it — not a re-rendered approximation.
2. Timestamped. You can say what the page showed on the day you captured it.
3. Private until you decide. Sources for an unpublished story must not be sitting in a public archive anyone can browse.
4. Shareable in one click. Your editor opens the exact copy from a link, without an account on your tools and without you sending files.
5. Findable months later. When the follow-up lands, you need every source from every related story — searchable, not archaeology.
6. Independent of the live site. The copy opens even when the original is edited, moved, paywalled, or deleted.

A workflow that survives editors and deadlines

Here is the same flow we walk through on the journalists use-case page, run with PagePocket.

1. Save the source at first contact

The moment a page matters — the executive's old statement, the forum post with the detail everyone missed, the competitor's pricing page — save it with the browser extension. One click captures a full-fidelity copy into your private library. The rule is simple: if you might cite it, capture it before you close the tab. Saving after publication is archaeology; saving at first contact is reporting.

2. One collection per story

As you report, saves land in a collection named for the story — "council rezoning vote", " merger filing", whatever your shorthand is. When the story is fact-checked, everything the piece rests on is in one place: articles, press releases, regulatory filings, the deleted tweet's page. No digging through browser history to reconstruct where a paragraph came from.

3. Note the why

Attach a note to the saves that need explaining: which sentence matters, what to verify, who claimed what. Future-you, or the colleague picking up the follow-up, needs the reason the page was worth capturing — the page itself cannot tell them.

4. Search across everything when the story moves

Six months later the follow-up lands, and you half-remember a detail from a source you can no longer find. Because every word of every save is full-text searchable, a phrase from the original surfaces the page — across every story you have covered, not just the one collection.

5. Hand your editor the exact copy

When an editor or fact-checker needs to see a source, create a share link to the saved copy. They see precisely what you saw — the page cannot be edited under their feet between your read and theirs — and the link can carry an expiry date. Meanwhile nothing becomes public: the library stays private, and only the pages you deliberately share have links at all.

6. On publication, keep the public record too

For sources the public should be able to check, a public archive earns its place: the Wayback Machine's Save Page Now turns a page into a citable public URL in seconds. Private working archive for the reporting, public receipts for the readership — the two are complements, and using both is the professional default. We compare the two approaches honestly in Wayback Machine alternatives for personal archiving.

What this does — and does not — solve

The honest limits: PagePocket requires an account, works online, and has plan quotas — the free plan covers 50 saves a month and 500 MB, and Pro is $2/month billed yearly — so it is sized for working journalists rather than automated bulk capture. And it is not legal-grade citation infrastructure: a page archived to your account is your receipt, not an institutionally preserved citation. Where a court filing or formal academic citation is involved, Perma.cc remains the standard — see how to cite web pages that won't rot for that comparison.

For the daily job — sources that must still exist, verbatim, when the editor, the lawyer, or the subject of the story comes asking — a private, searchable archive you control is the tool that fits.

Start with your next story

You do not need a system on day one. Pick the next story you report and run this workflow on it: save each source as you touch it, keep them in one collection, and share one link with your editor instead of a folder of screenshots. Create a free account to start — and for the general method behind all of this, read how to save a web page forever.