A date beside a headline looks simple, yet it can answer three different questions: when the article became public, when its explanation changed, or when the event it describes took place. Without a label, readers must guess. A useful date is not decoration that makes a page look newer. It is part of the explanation.
Give each date a clear job
Keep the first publication date attached to the article’s history. If a report discusses an earlier announcement, identify the announcement date in the story instead of presenting it as the article’s publication date. When both dates matter, label both. This is especially important for a roundup: publishing a selection today does not make every event in it new today.
Explain a meaningful update
Use a visible “Updated” label when a revision changes something the reader needs to know: a corrected condition, a new step or a replaced source. A short note about what changed is often more helpful than a newer date alone. Fixing punctuation, rebuilding a site or changing a button’s color should not automatically create the impression that the article has been researched again. Decide that editorial rule before automating dates.
One meaning, two representations
People need a readable date; software needs an unambiguous value. HTML’s <time> element can pair localized visible wording with a datetime attribute. A date-only value such as 2026-03-14 means a calendar day, not an exact publication instant. For article structured data, datePublished describes first publication and dateModified a modification. Keep these values aligned with what the page actually tells the reader, rather than maintaining unrelated dates in several templates.
A schedule is not a publication record
A planned slot belongs in an internal queue until the material is actually released. If publishing is delayed or fails, do not show that planned moment as an accomplished event. When an exact timestamp is needed, store its timezone or UTC offset and format it deliberately for the audience. Near midnight, the same instant can fall on different calendar days; check that difference instead of “correcting” one value by guesswork.
Check the whole reading path
Compare the archive card, article heading, metadata and each translation. Ask what every date refers to, whether an update note is still accurate, and whether a future time has accidentally reached the public page. Prefer clear month names when a numeric date could be misread across languages. Google recommends consistent date information but does not guarantee a date will appear in search results. Honest dating supports understanding; it is not a promise of rankings or extra traffic.