# Website Monitoring for Journalists: Sources, Speed, and Audit Trail
Source: PageCrawl.io Blog
URL: https://pagecrawl.io/blog/website-monitoring-for-journalists
---
At 2:14 in the morning, a federal agency updates the eligibility threshold on a benefits page from $75,000 to $50,000. No press release, no statement, no tweet. The old number is gone, and unless someone saved the page, there is no public record it ever said anything else. A corporate communications team deletes a paragraph admitting a recall and replaces it with softer language. A city council quietly swaps the agenda item that was going to be controversial. Each of these is a story, and each vanishes the moment the page reloads.
Reporters have always known that the most revealing changes happen in the dark, between the version a source confirmed last week and the version that is live right now. The problem was never finding the story. It was being awake at 2:14 in the morning, on the right page, with proof of what it said before.
Website monitoring closes that gap. Instead of refreshing tabs and hoping you catch an edit while it is happening, you set a tool to watch the pages that matter, capture every version with a timestamp, and ping you the instant a word changes. This guide covers what journalists should monitor, how to set it up, how to build an audit trail that survives a legal challenge, and the ethics of reporting on changes you were not supposed to see.
### Why do journalists need website monitoring?
Journalists need website monitoring because the official record is editable, and the people who edit it rarely announce when they do. Monitoring gives a reporter three things that manual checking cannot: a watch on dozens of source pages at once, a timestamped copy of what each page said before it changed, and an alert that arrives in minutes rather than weeks.
Think of it as covering three jobs that map directly to the craft. **Sources**: you extend your beat to every page a person, agency, or company controls, so a quiet edit becomes a tip. **Speed**: you find out about a change while it is still news, not after a competitor publishes. **Audit trail**: you hold a defensible, dated record of the before and after, which is what separates a confirmed story from a rumor.
#### What do "quiet edits" actually look like?
Quiet edits are content changes made without any public notice, and they are far more common than most readers assume. They include silently revised press releases, scrubbed blog posts, reworked guidance documents, deleted FAQ answers, walked-back policy language, and dates or numbers swapped after the fact. The original wording usually disappears entirely.
A press office changes "we are aware of the issue" to "we have resolved the issue" without flagging the revision. A politician's bio loses a board membership the day before a conflict-of-interest story breaks. None of these come with a changelog. To you, with a monitor running, each one arrives as a diff that highlights exactly which words moved.
#### Why is the timestamp the most important part?
The timestamp is what turns a screenshot into evidence. Anyone can save a page; far fewer can prove when they saved it and that the saved version is the one the site actually served. For a journalist, a dated, unaltered capture of the page as it existed before the edit is the difference between "I think it used to say" and "here is what it said, captured at 2:14 AM on November 4." That record protects the story in a correction dispute and protects the reporter if the subject claims the change never happened. We cover the legal weight of dated captures in depth in our guide to [preserving internet evidence for defamation cases](/blog/preserving-internet-evidence-defamation).
[Image: Screenshot of federalregister.gov in a browser window, an example of a page PageCrawl can monitor for changes]
federalregister.gov is exactly the kind of page PageCrawl keeps an eye on for you.
### What should journalists monitor?
Journalists should monitor any page where a change is itself newsworthy or where an edit could quietly rewrite the record. In practice that means four buckets: government and public-sector pages, corporate and PR pages, the documentary record (filings, dockets, bios), and the feed layer where breaking signals first surface. Start with the pages tied to your active beat, then expand.
#### Which government and public-sector pages matter most?
Government pages are the highest-value targets because they carry authority and are edited constantly with little notice. Watch agency guidance and bulletins, regulatory pages, public-health advisories, council and committee agendas, contract and procurement notices, and any "current as of" page that publishes numbers like case counts, thresholds, or deadlines.
These pages change for reasons that are themselves the story: a deadline gets extended, a rule gets softened after lobbying, a statistic gets revised downward. Because the public treats government text as the final word, a quiet edit there has outsized impact. For a beat-specific approach to agency feeds and newsrooms, see our guide on [monitoring government agency news](/blog/government-agency-news-monitoring), and for tracking the legislative pipeline directly, our guide on [monitoring bills and laws](/blog/legislative-tracking-monitor-bills-laws).
#### Which corporate and PR pages should you watch?
Watch the pages a company controls and would most want to revise without you noticing: the press and newsroom section, executive and board bios, product and pricing pages, careers pages (hiring and layoff signals), and investor relations notices. A scrubbed press release, a removed executive bio, or a job posting that appears and disappears in a day can each anchor a story. Press pages are worth a tight watch: the gap between the statement issued and the statement currently live is where spin happens. Our guide to [press release and PR monitoring](/blog/press-release-monitoring-pr-tracking) goes deeper on building that beat.
#### How do you cover people, filings, and the record?
Cover the record by monitoring the pages that document who did what and when: official biographies, organizational charts, public filings and disclosures, license databases, and reference pages like Wikipedia entries for the people on your beat. These pages are edited to manage narrative. A bio that loses a credential, or an org chart that drops a name the week before a reshuffle, is a lead, not a coincidence.
#### How do you watch the feed layer for breaking signals?
Watch the feed layer (RSS feeds, social profiles, status pages, and any page that lists "latest" items) because it is usually where a change surfaces first, seconds before it spreads. Set keyword triggers so you are alerted only when a watched page mentions a name, place, or term you care about. Our [keyword and trigger-word monitoring](/blog/keyword-monitoring-website-trigger-word-alerts) guide explains how to tune those filters, and our roundup of [journalism and news monitoring tools](/blog/journalism-news-monitoring-tools) compares the broader category.
### How do you set up monitoring in PageCrawl?
You set up monitoring by adding the page URL, choosing a tracking mode that matches the content, setting how often it should check, and routing the alert to where you actually work. The full walkthrough below takes about ten minutes and works on the free tier, which covers 6 monitors and 220 checks per month, enough to watch your most important source pages before you commit to a paid plan.
[Image: PageCrawl change diff for Federal benefits eligibility page, highlighting the added and removed text]
**Step 1: Build your source list.** Before adding anything, list the 6 to 20 pages tied to your active beat: the agency bulletin, the company press page, the two or three bios, the council agenda, the regulatory notice. This beat sheet is the step most reporters skip.
**Step 2: Add your first monitor.** Create a free PageCrawl account and paste a URL into the new monitor field. Start with the single most important page on your beat: the one where a quiet edit would be the biggest story.
**Step 3: Choose the right tracking mode.** For a long article, bulletin, or press release, use reader mode, which extracts the main body text and ignores navigation and ads. For a page where you care about one number or line (a threshold, a count, a deadline), target just that element with a CSS selector. For a layout-sensitive page like an agenda or a results board, add visual monitoring so you catch a change even when the text is buried in an image.
**Step 4: Set the check frequency.** Match frequency to how fast the story moves. For a page where being first matters (a breaking-news source or a status page), check as often as your plan allows. For a stable bio or policy page, hourly or daily is plenty.
**Step 5: Turn on screenshots and enable the change history.** Make sure each check stores a screenshot and a saved copy of the page text. This is what builds your audit trail: every check becomes a dated entry, so when a page changes you have both the new version and the exact prior version side by side.
**Step 6: Route the alert to where you work.** Connect email for the desk and a chat channel for the team. Routing a "source page just changed" alert into a shared channel turns one reporter's monitor into a newsroom-wide tripwire. Our guide on [sending website change alerts to Slack](/blog/website-change-alerts-slack) covers the setup, including how to keep noise low so the channel stays useful.
**Step 7: Review the diff, then verify before you publish.** When an alert arrives, open the diff to see exactly which words changed, read the AI summary for a one-line description of the edit, then go do the reporting. The monitor found the change; confirming what it means is still your job.
### How do you build a defensible audit trail?
You build a defensible audit trail by capturing every version of a watched page automatically, with a timestamp, somewhere the subject of the story cannot reach. A monitoring tool does this as a side effect of checking: each check is a dated snapshot, so a page's history becomes a chronological record of exactly what it said and when, including the version that was deleted.
The key is that the capture happens before you know you need it. By the time an agency edits a page, the old wording is gone from the live web, but your monitor saved it on the last check. That saved version, with its timestamp and screenshot, is what you cite, what your editor reviews, and what survives a "we never said that" pushback. Pair active monitoring with independent archiving so you hold a second, externally verifiable copy; our comparison of [Wayback Machine alternatives for web archiving](/blog/wayback-machine-alternatives-web-archiving) covers the options, and our explainer on the [web evidence layer](/blog/web-evidence-layer-definitional) describes why a dated, tamper-evident capture is becoming standard practice for serious newsrooms.
Treat the trail as a chain of custody: log when the monitor first saw the page, every change it recorded, and the exact capture you are citing. A clean, dated trail is what lets your legal team defend the story and lets you correct the record precisely if you got something wrong.
### How do you beat the competition on breaking changes?
You beat the competition by watching the source directly and being alerted in minutes, while everyone else waits for the press release or refreshes manually. Monitoring removes the luck: the page tells you it changed, instantly, day or night.
Speed comes from two settings working together: frequency and routing. The more often a monitor checks, the smaller the window between the edit and your alert, and on a fast plan that window is minutes. An alert that lands silently in an inbox you read twice a day is not fast, so push it to your phone or a chat channel that is always open, where the change reaches you while it is still exclusive.
The advantage compounds across a beat. One reporter can watch five pages by hand; a monitoring setup watches a hundred without fatigue, so you are first not just on the page you guessed would change, but on the forty you would never have thought to refresh.
### What are the ethics and verification rules?
The ethics rules are straightforward: a detected change is a tip, not a published fact. Monitoring tells you that a page changed and what the old version said. It does not tell you why, what it means, or whether the change is even significant. Reporting the diff as the story, without confirming intent and context, is how monitoring goes wrong.
Follow three rules. **Verify before you publish.** A quiet edit can be a correction, a typo fix, or a routine update as easily as a cover-up, so ask the source and give them the chance to explain it on the record. **Distinguish public from private.** Monitoring public web pages is fair game and no different from a reporter visiting the site repeatedly; it is not hacking. Do not use monitoring to defeat logins, paywalls, or pages a subject reasonably expects to be private. **Preserve, do not alter.** Captured evidence is only credible if it is unmodified, so cite the timestamp, show the diff honestly, and never crop the record to make an edit look worse than it is.
Done right, monitoring makes journalism more accurate, not less: you catch changes you would otherwise miss and hold a precise record of them, so your corrections are sharper and your accusations better sourced.
### Common newsroom monitoring scenarios
#### Catching a scrubbed government statistic
**The scenario:** An agency revises a public dashboard, lowering a reported figure overnight with no announcement, and the old number is gone by morning.
**With monitoring:** Your hourly monitor captured the change at 2:14 AM. The alert shows the figure dropped from 4,820 to 3,610, with a dated screenshot of both versions. You get the agency on record explaining the revision and publish a sourced story by mid-morning.
**Without monitoring:** The revised number becomes the only public version. Weeks later a source mentions it "used to be higher," but with no capture of the original, the story is unprovable and dies.
#### Documenting a deleted corporate apology
**The scenario:** A company posts a statement acknowledging a defect, then quietly replaces it with vaguer language after legal review, hoping no one saved the first version.
**With monitoring:** Your reader-mode monitor on the press page saved the original wording on its last check. The diff shows the exact paragraph that was removed, with a timestamp. You have both versions side by side, which is the story: not just the defect, but the walk-back.
**Without monitoring:** The softened statement is the only one on the record. You have a vague memory of a stronger admission and no way to prove it existed.
### Choosing your PageCrawl plan
PageCrawl's **Free plan** lets you monitor **6 pages** with **220 checks per month**, which is enough for a single reporter to watch a core beat and confirm the workflow before committing.
| Plan | Price | Pages | Checks / month | Frequency |
|------|-------|-------|----------------|-----------|
| Free | $0 | 6 | 220 | every 60 min |
| Standard | $8/mo or $80/yr | 100 | 15,000 | every 15 min |
| Enterprise | $30/mo or $300/yr | 500 | 100,000 | every 5 min |
| Ultimate | $99/mo or $999/yr | 1,000 | 100,000 | every 2 min |
Annual billing saves two months across every paid tier. Enterprise and Ultimate scale up to 100x if you need thousands of pages or multi-team access.
Standard at $80/year pays for itself the first time it captures a deleted statement before the wording is gone. Its 100 pages cover a serious beat (agency bulletins, executive bios, press pages, plus the competitor newsrooms you want to stay ahead of), and 15-minute checks shrink the window between an edit and your alert from an hour to minutes, the margin that decides who breaks the story. Enterprise at $300/year fits an investigations desk watching 500 pages at five-minute frequency, and Ultimate suits a wire-style operation needing near-real-time coverage across a thousand sources.
All plans include the **PageCrawl MCP Server**, so you can ask an AI assistant to summarize every change across your beat over the past week, in plain language, instead of scanning a dashboard before each shift. AI assistants can create monitors through conversation on every plan, including Free.
### Getting Started
Pick the one page on your beat where a quiet edit would be the biggest story, and put a monitor on it right now. Add a second for the press page you check by habit, and a third for the bio you suspect will change. Turn on screenshots so every check builds your timestamped record, and route the alerts to wherever you actually work.
The next time a source page changes at 2:14 in the morning, you will not have to be awake to catch it, and you will have the proof in hand. Be the reporter who already knew.
---
Need more? The complete PageCrawl.io help center, with every article, is available as a single document at https://pagecrawl.io/llms-full.txt. Read it for context on anything this page does not cover.