Last checked: August 7, 2026
A news organization can correct an article in seconds. Correcting every copy of that article is a different problem.
The distinction matters because modern news does not remain on one webpage. A wire story may be copied into hundreds of customer systems. A photograph and its caption can be downloaded, cached and republished. Search engines may preserve an older snippet. Newsletters and alerts can outlive the page that generated them. Even when the originating newsroom acts responsibly, readers elsewhere may continue encountering the error.
Batmandir · Founders A numbered seat at the table. S3 · The Founders Club — 161 seats per location. By invitation. Explore membership →The public standards used by the Associated Press and the International Press Telecommunications Council show that correction propagation is not an afterthought. The distribution system has explicit mechanisms for it: correction notices, replacement versions, stable identifiers, machine-readable signals and instructions to downstream customers. But those mechanisms also reveal the weak link. A correction travels only when each recipient recognizes the signal and updates what it previously published.
What AP promises to do
AP’s published standards describe a correction as both an editorial act and a distribution event. In its News Values and Principles, AP says errors should be corrected “fully, quickly and ungrudgingly.” The same guidance says corrections are communicated to subscriber editors through notes, metadata or advisories, as well as to consumers.
For material already distributed, AP’s process is more specific than silently editing a page. A correction must identify what was wrong and supply the accurate information. Online versions replace the erroneous text. When an error appeared in a previous day’s report, AP says subscribers that used the erroneous information should carry the correction.
Its terms for content customers reinforce the operational duty: subscribers are expected to make AP kills, corrections and substitutions promptly. Photo workflows use their own notification system. AP’s documentation for picture notification banners says advisories can announce caption corrections, additions or kills, with a corrected picture following when appropriate.
That is a real propagation architecture. It does not rely on a reader happening to revisit the original story. The provider sends an explicit message downstream and issues replacement material.
The correction can be machine-readable
The technical standard beneath many news-distribution systems is NewsML-G2, maintained by the nonprofit IPTC. Its implementation guidelines describe how a publisher can mark a correction with a machine-readable signal while also explaining it to a human editor in an editorial note.
NewsML-G2 also distinguishes between updating an item and replacing it. A revised item can retain the same globally unique identifier while receiving a higher version number. A recipient can then understand that the newer package supersedes the older one instead of treating both as separate stories.
Those details are important. A correction buried in prose is easy for software to miss. A stable identifier, new version number and formal correction signal give a subscriber’s content-management system something it can process automatically. AP’s own content metadata includes editorial types such as “Correction,” “Corrective” and “Clarification,” according to its metadata field documentation.
In principle, the route looks like this:
| Stage | Primary actor | What must happen | Typical failure |
|---|---|---|---|
| 1. Verify | Originating newsroom | Confirm the error and accurate replacement | Ambiguous or incomplete correction |
| 2. Signal | Originating newsroom | Issue a labeled correction tied to the original ID | Silent overwrite with no machine-readable notice |
| 3. Deliver | Distribution system | Send the advisory and replacement version | Subscriber workflow misses the notice |
| 4. Apply | Syndication partner | Update or remove the public copy | Local edits block automated replacement |
| 5. Refresh | Search, feeds and social systems | Recrawl or regenerate secondary surfaces | Stale snippets, cards or cached copies persist |
How a correction moves—and where control changes hands
Source-controlled
Source-controlled
Shared control
Partner-controlled
Platform-controlled
The first three stages are largely controlled by the source. The last three are not.
Where the chain can break
The standards prove that a correction can travel. They do not prove that every public copy changes.
A subscriber may have imported the article into a local publishing system and edited it. An automated update may be disabled to avoid overwriting local changes. A correction advisory may reach an editor without triggering a page update. A newsletter already sent cannot be recalled from inboxes. A screenshot or social post may have no live connection to the source at all.
AP itself provides unusually clear evidence of this boundary in a different correction context. Its request page concerning reports of minor crimes tells applicants that an AP decision affects AP-controlled websites. If an AP report was also published on customer sites, the person must contact those publishers separately.
That does not mean customers routinely ignore corrections. It means control is distributed. The organization that created a story may be able to change its own archive and send instructions, but it cannot guarantee that every independent publisher, cache or quotation will follow.
Search adds another lag. Google says requesting a recrawl does not guarantee immediate inclusion and that crawling can take from days to weeks, in its guidance for asking Google to recrawl a page. A corrected page can therefore coexist temporarily with an outdated result or snippet even after both the source and a syndication partner have fixed their pages.
Why silent overwriting is not enough
Replacing bad text prevents future readers from seeing the error at the canonical URL, but it does little for people who already saw or reused it. A labeled correction performs a second function: it tells downstream editors and readers that an earlier version should no longer be trusted.
This is why the same-identifier, higher-version model is useful. It treats the article as a continuing record rather than an interchangeable blob of text. It also allows systems to compare what they hold with what the provider now considers current.
The harder cases are not typographical mistakes but errors that changed the meaning of a report: the wrong person identified, an allegation stated as fact, a number off by an order of magnitude or a photograph paired with the wrong event. In those cases, reaching only the original page is plainly insufficient. Every prominent reuse becomes a potential source of continuing harm.
What readers can and cannot infer
When a stale syndicated copy remains online, it does not by itself prove that the originating newsroom failed to send a correction. The source may have issued the correct advisory while a recipient failed to act. Conversely, a corrected source page does not establish that the newsroom notified everyone who received the original.
The strongest public evidence is a complete trail: the original item identifier and version, the correction or kill advisory, the replacement version, and timestamps showing what downstream pages displayed afterward. Without that trail, responsibility for a stale copy may remain uncertain.
News organizations could make this easier to audit by exposing version histories and linking corrections to the item they replace. Syndication partners could display a visible “updated” or “corrected” label instead of silently swapping text. Search engines and aggregators could give formal correction signals priority over ordinary recrawling.
The underlying infrastructure already recognizes the problem. AP’s rules tell subscribers to process corrections. IPTC provides a shared technical language for corrections and replacements. The remaining question is compliance across a fragmented chain.
So, do corrections travel beyond the original article? Yes—sometimes through a deliberately engineered system of advisories, metadata and replacement versions. But delivery is not the same as completion. Once a story leaves its source, correction becomes a relay race, and the record is only as accurate as the last publisher still carrying the baton.
Method note
This article reviews publicly available AP policies and technical documentation, AP customer terms, IPTC NewsML-G2 guidance and Google’s recrawling documentation. It describes documented correction mechanisms and their limits; it does not claim to measure downstream compliance or the frequency with which syndicated copies remain stale.
