How to Document Corrections in an Online Article

When an online article contains an error, correcting the text is only part of the job. A clear correction record explains what changed, why it changed, when it changed, and how readers can distinguish a correction from a silent edit.

Understand what counts as a correction

A correction is a documented response to a factual, numerical, attribution, spelling, or contextual error that appeared in a published article. It is different from a routine copy edit, a scheduled update, or a change made because circumstances have developed since publication.

Common examples include:

• A person’s name, title, location, date, or organization is incorrect.
• A statistic, calculation, quotation, or percentage is wrong.
• A paragraph attributes information to the wrong source.
• A caption or image description identifies the wrong person or place.
• A headline makes a factual claim that the article does not support.
• A link points to the wrong document or source.
• A translation, transcription, or spelling error changes the meaning.

Not every change needs a public correction note. Fixing a typo that does not affect meaning may be recorded internally without adding a notice to the article. However, the more a change affects a reader’s understanding, the stronger the case for documenting it publicly.

A useful distinction is this:

Change type	Public note usually needed?	Example
Minor spelling or punctuation fix	No	Correcting an obvious typo
Factual error	Yes	Incorrect date, name, amount, or location
Misleading wording	Usually	Headline implies an unsupported conclusion
New information	Usually no correction	Adding a later development with a dated update
Legal or safety-sensitive error	Yes	Incorrect medical, legal, or emergency information

When uncertain, consider the reader’s perspective. If someone relied on the original wording, would they reasonably need to know that it was wrong? If the answer is yes, publish a correction note.

Verify the error before editing

Do not change an article based only on a comment, social-media post, or unverified complaint. First determine whether the criticism identifies a genuine error and whether the source supporting the correction is reliable.

Use this verification process:

1. Locate the disputed statement. Copy the exact sentence, figure, headline, caption, or link into an editorial note. Recording the original wording prevents confusion if several versions of the article exist.
2. Identify the relevant source. Use the primary document whenever possible: an official record, transcript, court filing, research paper, data set, press release, direct interview recording, or authoritative institutional page.
3. Compare the evidence. Check whether the source actually supports the proposed correction. Watch for differences in dates, units, definitions, time zones, and similarly named people or organizations.
4. Ask a second editor to review important changes. A fresh reader can catch a mistaken interpretation, especially when the correction involves numbers, legal matters, health information, or allegations.
5. Preserve the evidence. Save the source URL, publication date, relevant page or section, and notes describing what was checked. If the source may change, save an approved copy or screenshot according to your organization’s records policy.

If the issue is a disputed opinion rather than a factual error, do not label it a correction simply because a reader disagrees. You may need to add context, clarify wording, request a response, or publish an editor’s note instead.

Create a correction record

A correction record should be specific enough that another editor can understand the decision without repeating the entire investigation. Store it in your content-management system, editorial database, shared document, or corrections log.

Include these fields:

• Article title and permanent URL
• Article ID or internal slug
• Original publication date and time
• Date and time the problem was discovered
• Person or source that reported the issue
• Exact original wording
• Corrected wording
• Error category
• Evidence supporting the correction
• Name or initials of the reviewer
• Date and time the public correction was published
• Whether the headline, metadata, social copy, newsletter copy, or image was also changed
• Whether a notification or follow-up is required

Use neutral language in the record. Instead of writing “the writer made a careless mistake,” write “the article gave the wrong publication year for the report.” The record is intended to preserve accountability and improve future work, not to assign blame.

A simple internal entry might look like this:

Article: How Local Transit Funding Changed
URL: https://example.org/local-transit-funding
Original statement: The program began in 2018.
Correct information: The program began in 2019.
Source: City budget document, page 14, accessed 2026-09-24.
Action: Updated paragraph two and added a correction note below the article.
Reviewer: Editorial desk
Published correction: 2026-09-24 at 14:20 UTC
Related assets checked: Headline unchanged; newsletter copy updated.

Keep the original wording in the internal record even after the article is corrected. This creates an audit trail and helps editors identify recurring problems, such as confusion between preliminary and final figures.

Edit the article carefully

Before changing the page, decide whether the correction requires a sentence, paragraph, headline, caption, graphic, or multiple related assets to be revised. Correct only what is necessary, but review the surrounding text for consequences.

For example, changing “the largest increase” to “the second-largest increase” may require updates to the next paragraph, a chart label, the page title, and search metadata. A corrected name in the body may also require a change to the image caption and social-media description.

Follow these steps:

1. Open the article in the content-management system and make a backup or revision snapshot if the system supports it.
2. Read the entire affected section before editing.
3. Replace the inaccurate wording with precise wording that the evidence supports.
4. Check nearby pronouns, numbers, references, hyperlinks, captions, charts, and pull quotes.
5. Preview the page on desktop and mobile.
6. Confirm that the correction note is visible to ordinary readers, not only logged-in editors.
7. Publish the update and record the exact publication time.

Do not rewrite the article so extensively that the original mistake becomes impossible to identify. A correction note should correspond to a meaningful, traceable change. If a major restructuring is necessary, explain the relevant factual correction separately and keep a detailed internal version history.

For collaborative editing, use track changes or revision comparison when available. A visual comparison can show which wording was removed and added, reduce accidental omissions, and give a second editor a focused review task. Track changes are especially useful before publishing corrections to long articles, tables, or technical material.

Write a clear public correction note

Place the note near the beginning or end of the article, using a consistent label such as “Correction,” “Editor’s note,” or “Correction and update.” The label should be easy to find, visually distinct, and accessible to screen readers.

A good correction note answers four questions:

• What was wrong?
• What is correct?
• When was the article corrected?
• Did the error affect the article’s meaning or conclusion?

A concise template is:

Correction, September 24, 2026: An earlier version of this article stated that the program began in 2018. It began in 2019, according to the city budget document. The article has been corrected.

For a more serious mistake, add a direct acknowledgment:

Correction: An earlier version incorrectly identified the speaker as the organization’s director. The speaker was the organization’s deputy director. The article and caption have been updated. We regret the error.

Avoid vague wording such as “some details have been updated.” Readers should not have to guess what changed. Also avoid defensive explanations, speculation about how the mistake happened, or language that shifts responsibility to a source when the publication made the error.

If the article has been updated with new developments as well as corrected, separate the notices:

Update, September 24, 2026: The council approved the proposal after this article was published.

Correction, September 24, 2026: An earlier version misstated the proposal’s estimated cost. The correct estimate is $2.4 million.

This distinction prevents a routine update from obscuring a factual correction.

Preserve transparency across versions

Online content is often copied into newsletters, mobile applications, RSS feeds, social platforms, search previews, and syndicated pages. Correcting the main article does not automatically correct every version.

After publishing the correction, check:

• Page title and headline
• Search-engine title and description
• Open Graph and social-sharing text
• Newsletter or email version
• RSS feed entry
• Downloadable PDF or print view
• Embedded charts, images, and captions
• Translations or republished versions
• Partner or syndicated copies

If a third party republished the incorrect version, contact that publisher with the corrected wording and a link to the public correction note. Keep a record of the request and any response. You may not control the third-party page, so describe the limitation accurately rather than claiming that all copies have been fixed.

For articles that receive significant traffic, consider adding a visible “last updated” timestamp, but do not use it as a substitute for a correction note. A timestamp tells readers that something changed; it does not explain what changed.

Handle corrections involving sources and people

Some corrections affect a person’s reputation, employment, safety, or legal position. Treat these cases with additional care. Verify the facts, consult the relevant editor, and consider whether legal or standards review is appropriate under your organization’s policy.

If an article contains a serious allegation that is later shown to be false, a small note at the bottom may be insufficient. The publication may need to correct the headline, metadata, social posts, image, and search-facing text, and it may need to contact directly affected parties. The remedy should match the prominence and reach of the original error.

Do not remove a correction note merely because the corrected article has been online for a long time. Historical transparency is valuable, particularly for public-interest reporting and pages that continue to receive search traffic.

If a source asks you to change accurate information, evaluate the request separately from a correction. A correction fixes an error; an editorial revision may reflect a new source, a clarification, a privacy concern, or a legal requirement. Document the reason for any change so the public notice remains truthful.

Troubleshoot common problems

The correction note is not displaying. Check whether the CMS places notices in a hidden custom field, whether the article template supports the field, and whether caching is serving an older page. View the page in a private browser window and clear the relevant cache only after confirming the updated revision is published.

The original wording is no longer available. Check revision history, backups, editorial emails, cached internal previews, and syndicated copies. If you cannot reconstruct it exactly, describe the error accurately without inventing a quotation. For example, say that an earlier version gave an incorrect date rather than claiming a precise sentence you cannot verify.

Editors disagree about whether a change is a correction. Return to the evidence and ask what a reasonable reader would have understood from the original text. Record the decision and apply the same standard to similar cases. A standards editor can help resolve recurring disagreements.

A chart or graphic still contains the error. Treat visual elements as part of the article, not as separate decoration. Update the source data, labels, alt text, downloadable files, and any image embedded elsewhere.

The article is translated. Send the correction to every language editor and verify that the public notice explains which language versions were affected. Literal translation may not preserve the meaning of the correction, so have a fluent editor review it.

A correction would expose private information. Do not add unnecessary personal data in the name of transparency. State the factual correction while following privacy, safeguarding, and legal policies.

Build a repeatable corrections policy

A written policy makes correction decisions faster and more consistent. Define who can approve a correction, which errors require a public note, where records are stored, and how quickly urgent mistakes must be addressed.

At minimum, establish:

• A single corrections-log location
• A severity scale for minor, significant, and urgent errors
• A reviewer for legal, health, safety, and reputational issues
• A standard correction-note format
• A process for correcting related content and syndicated copies
• A retention period for revision histories and evidence
• A regular review of correction patterns

Periodically analyze the log for recurring causes. If several corrections involve copied figures, add a second-person number check. If names are frequently misspelled, require confirmation against a primary source. The purpose of documentation is not merely to prove that a correction occurred; it is to make the next article more accurate.

When the correction is complete, the reader should be able to see the corrected information, understand what was wrong, and find enough context to trust the record. That combination of accuracy, clarity, and traceability is the practical standard for responsible online publishing.