Why dates and corrections are trust signals
A reader deciding whether to act on a page asks two quiet questions: is this still true, and would they tell me if it were not? Visible dates answer the first. Correction notes answer the second. A library that changes pages silently, or moves dates forward without changing anything, teaches readers that its dates mean nothing and its pages may have been different yesterday.
Search quality guidance points the same way. Google's guidance on helpful, reliable, people-first content asks whether content is accurate and whether a site can be trusted, which the content governance guide uses as the case for review cycles. The E-E-A-T guide reports that Google's rater guidelines treat trust as the most important of the four qualities, and that a page can show experience, expertise and authority and still be untrustworthy if it is inaccurate. The same guide lists visible dates, recorded updates and corrections made openly as on-page practice, and published editorial standards, saying how content is researched, reviewed and corrected, as site-wide practice. That is the whole of what this guide claims about search. No source this site cites says how dates affect ranking, so the rules below are written for readers, and the search benefit, where there is one, follows from pages being accurate and E-E-A-TExperience, Expertise, Authoritativeness, Trust. being visible.
Four kinds of change
Most confusion about corrections comes from treating every edit the same way. Four kinds of change cover almost everything, and each has a different rule for the page, the dates and the record.
| Kind of change | What it looks like | Visible dates | Note on the page | Record in the inventory |
|---|---|---|---|---|
| Slip | A typo, a broken link replaced, a formatting fix, a clearer sentence with the same meaning | Unchanged | None | Optional, batched |
| Substantive update | New facts, a new section, steps rewritten for a redesigned product, examples replaced | Updated date added or changed; published date kept | A short note of what changed | Yes: what, why, who, when |
| Correction | Something the page said was wrong: a figure, an instruction, a claim, a name | Updated date added or changed; published date kept | A dated correction note saying what was wrong and what is right | Yes, flagged as a correction |
| Withdrawal | The page cannot be made accurate, or the question is no longer asked | Not applicable | A notice, a redirect or removal, depending on what points at it | Yes: decision, reason, destination |
The line between a slip and a correction is the one people argue about, and a single test settles it: what would the old version have made a reader believe or do? If a reader of the old version would have understood the same thing, it was a slip. If they would have believed a wrong figure, followed a wrong instruction or relied on a wrong claim, it is a correction, however small the edit. The tutorial on fixing a mistake in a sent email uses the same question for email: the worth of a correction depends on what the mistake would make a reader do.
The line between a slip and an update is easier. If the change would be worth telling a returning reader about, it is an update. The content refresh test draws a similar line for refreshes: changing the date, a few words or the title alone is not a refresh.
What a published date and an updated date should mean
Write the meaning of each date into the house standards so that nobody has to guess.
- The published date is the day the piece first appeared at its address. It does not move. It tells readers how old the original thinking is, which matters for anything that ages.
- The updated date is the day the substance last changed: a substantive update or a correction. It is not the day someone fixed a typo, changed a template or re-saved the page. Show it beside the published date, not in place of it.
- A reviewed date, if the house uses one, is the day an owner checked the page and found nothing to change. It is honest only if the check really happened, and it is worth showing only where readers care that a page has been checked recently, such as guides that quote prices or rules.
Moving a date forward without changing the page is the practice to rule out. The site's evergreen content entry puts it plainly: changing the date without updating the content misleads readers. The diagnosis of old content losing traffic adds that it does nothing for the reasons a page was declining. A refreshed Evergreen ContentContent that stays relevant and useful long after it is published, rather than being tied to a date or a news moment. page earns its new date by being revised.
Dates also appear in markup. The structured data guide records two requirements from Google's structured data policies: markup must describe content visible on the page and must not misrepresent it, and for articles, dates must be real. So the published and updated dates in the page's Schema MarkupStructured data vocabulary. are the same dates the reader sees, generated from the same fields, and they change only when the visible dates change. Nothing in the sources this site cites describes any other date rule, and this guide does not attribute one to Google.
Update notes readers can use
An update note tells a returning reader whether they need to read the page again. It is short, dated and specific: what changed and, where it helps, why.
Good notes name the change: "Updated to cover the redesigned settings menu; steps four to six rewritten." Weak notes say only that something happened: "This post has been updated for freshness." A note that says nothing specific is worse than none, because it looks like the date was moved for its own sake.
Put the note where returning readers will see it. A line under the dates at the top suits a single important change. A short change history at the foot of the page suits pages that are revised often, such as reference guides, with the latest change also mentioned at the top. Keep old notes rather than replacing them, so the history accumulates.
Notes are part of the house style. The editorial style guide tutorial is the place to record the wording pattern, the date format and where the note sits, with a right and a wrong example, so that every writer produces the same kind of note.
Correcting an error openly
A correction is different from an update because the page was wrong, and readers may have acted on it. Four things make a correction open.
Fix the page and say so. Change the wrong content, then add a dated correction note near the top that says what was wrong and what is now right: "Correction: an earlier version of this guide gave the wrong setting for older models. The correct setting is shown in step three." Do not leave the reader to compare versions.
Correct where people saw it. The guide to handling an AI mistake sets out the principle, whatever produced the error: a corrected page does not reach the person who already acted on it, so correct in the channels where people met the wrong version and with similar prominence. If the page was sent in a newsletter, shared on social accounts or quoted in a sales deck, the correction follows it there. For a marketing email, the sent-email tutorial covers when a follow-up is needed and how to keep it to the original recipients.
Tell the people who acted on it, where practical. If the wrong page led people to buy, book or do something that could harm them or cost them, find out who they were from order records, sign-ups or support contacts and tell them directly. This is the step teams skip, and the one readers remember.
Fix the copies. Check whether the error was repeated elsewhere on the site, in derivatives made from the page, in a syndicated copyRepublishing the same article, in full or nearly so, on another organisation's site with permission and credit, to reach readers your own channels do not. or in a template the page shares with others. One wrong figure can sit in several places. An open correctionA correction made visibly: the error is fixed, a dated note says what was wrong and what is right, and the correction follows the mistake to where it was seen. is complete only once each of those copies has been fixed as well.
Some errors carry legal, regulatory or reputational weight: a claim about a person or company, a safety instruction, a regulated product. Those go to the approver the governance roles name before the correction is written, and the wording is theirs to approve. Nothing here is legal advice.
When to withdraw a page instead
Most wrong pages should be corrected, not removed, because a corrected page keeps its record and helps the reader who comes back to check. Withdraw a page when it cannot be made accurate at reasonable cost, when the thing it describes no longer exists, or when the question it answers is no longer asked, which is the retire decision in the governance guide.
How to withdraw depends on what still points at the page. The governance guide's rule is that a page with inbound links, search traffic or a close replacement is redirected to the page that now answers the question, and a page with none of those is removed and allowed to return a not-found response. The guide to expired pages adds the honesty test for redirects: Google's redirects documentation describes a permanent redirectA permanent server redirect telling browsers and search engines a URL has moved for good. as a strong signal that the target should be treated as canonical, which is only honest when the target really answers the same question. Redirecting a withdrawn page to the home page or a broad category leaves the visitor with nothing.
| Situation | What to do | What readers see |
|---|---|---|
| Wrong, but fixable | Correct it openly | The corrected page with a correction note |
| Replaced by a better page on the same question | Redirect to the replacement | The replacement, which can mention that it supersedes the old guide |
| Wrong, unfixable, with readers who relied on it | Keep a short notice at the address explaining the withdrawal, linking to the best current answer | The notice, then the current answer |
| No longer relevant, nothing points at it | Remove it | A not-found page |
The third row is the exception to removing quietly. Where a page was widely used and readers may come back to check what it said, a brief notice at the old address that says the page was withdrawn and why is kinder than a redirect that makes the old advice vanish. Once the decision is made, the SOP for removing a web page carries out the notice or the removal, clearing the page's links, sitemap entry, ads and emails and recording it.
Recording every change
The content inventory the governance guide describes is where changes are recorded, so that the next review knows what happened. For every update, correction and withdrawal, log the page, the date, the kind of change, what changed, why, who made it and who approved it. Corrections get a flag of their own, because a run of corrections on one pillar or from one writer is a signal about the review process, not only about the page. The change record column of the content inventory and audit template holds this log beside each page's owner, review dates and audit decision. Where a page also exists in other languages, the guide to keeping localised content in step with the source adds the editions each change touches to the same record, so a correction reaches every market. A video library needs the same record: the tutorial on auditing a YouTube video library applies it to corrected descriptions, pinned comments and replacement videos on a channel.
The record also lets you publish a corrections policy, which is the editorial-standards practice the E-E-A-T guide lists: a page that says how the site defines an update and a correction, how readers can report an error, and how quickly reports are looked at, in your own words. Link it from the site footer or the about page, and from every correction note. The policy, the notes and the log then tell the same story. The policy can sit as one section of a wider public page, and the tutorial on publishing your editorial standards places it beside authorship, sourcing, how the site earns and the use of AI. Placed there, the corrections policy is one part of the site's editorial standardsThe rules for how content is made and kept honest: who writes and reviews it, how claims are sourced, how it is funded, where AI helps and how it is corrected., and the notes on corrected pages show whether that part is kept.
A coffee equipment shop corrects a guide (illustrative)
Kettlespur Espresso Supplies corrects its descaling guide
Kettlespur Espresso Supplies, an invented online shop for coffee equipment, published a guide to descaling home espresso machines on 12 February 2025. In March 2026 a customer emails to say the dilution in step 4 is wrong for machines with a thermoblock heater: the guide says 1 part descaler to 5 parts water, and the descaler maker's instructions for those machines say 1 to 10. The content owner checks, confirms the error and treats it as a correction, not a slip, because a reader following the old step could have damaged a machine. She fixes step 4, adds a note under the dates ("Correction, 18 March 2026: an earlier version gave a 1:5 dilution for thermoblock machines; the correct dilution is 1:10, as shown in step 4"), and keeps the published date of 12 February 2025 beside an updated date of 18 March 2026, with the article markup generated from the same two fields. Order records show 37 customers bought descaler from the guide's links in the previous year; the shop emails them the corrected step and an apology. She finds the same figure in a product page and a newsletter archive and fixes both. The inventory entry records the change as a correction, with the reporter, the evidence, the approver and the pages touched.
Common mistakes
- Moving the date without changing the page. It misleads readers, and the next reader who notices stops trusting every date on the site.
- Replacing the published date with the updated date. Readers lose the age of the original; show both.
- Correcting silently. A reader who acted on the old version has no way to know it changed. Say what was wrong.
- Vague update notes. "Updated for freshness" tells a returning reader nothing; name what changed.
- Dates in markup that differ from the page. Structured data has to describe what is visible, and article dates must be real.
- Fixing the page but not the copies. The same error survives in the newsletter, the product page and the syndicated version.
- Deleting a wrong page that people relied on. The record disappears with it. Correct it, or leave a notice that explains the withdrawal.
- Redirecting a withdrawn page to the home page. The visitor gets nothing they asked for; redirect only to a page that answers the same question.
- No log. Without a record, nobody can see whether corrections cluster in one pillar, one writer or one stage of review.
