Originally published: February 27, 2023 · Last updated: August 14, 2026
Updating an old article can improve its usefulness and make its current status clearer to readers. What does not help is changing a date while leaving the substance untouched. Google explicitly recommends using dates that reflect when a page was published or significantly updated, and keeping visible dates consistent with structured data.
Keep the original publication date when it is real
If an article genuinely dates from 2020, 2021 or 2023, there is no need to erase that history. A transparent format such as Originally published plus Last updated tells readers what happened and preserves the article’s chronology.
The publication date and modification date serve different purposes. Treating every updated article as if it were newly published makes the archive less trustworthy.
Change the update date only after a meaningful revision
A meaningful update can be short or long. What matters is whether the page has become materially more useful or accurate. Examples include:
- replacing obsolete instructions;
- updating product or platform behavior;
- correcting inaccurate claims;
- adding important missing context;
- restructuring a weak article into a clearer guide;
- removing recommendations that are no longer valid.
Changing a year in the title, rewriting a few sentences or fixing punctuation is not the same thing as substantively updating the content.
Make the date visible to readers
Google recommends displaying a date prominently and labeling it appropriately, for example with “Published” or “Last updated”. If you show both dates, make the distinction obvious.
Do not hide the date only in structured data. The page itself should tell readers whether they are looking at a historical article, a recently revised guide or both.
Keep structured data consistent
For article markup, datePublished should represent the original publication date and dateModified should represent the latest meaningful update. The visible date and the structured values should agree.
If your SEO plugin generates this markup automatically, verify the output rather than adding duplicate schema by hand.
Update the sitemap when the page really changes
A sitemap can include a last-modified value. Use it for genuine changes, not as a daily freshness signal for pages that have not changed. Consistency helps search engines interpret the update correctly.
Do not change the URL just to add a new year
Evergreen guides usually benefit from stable URLs. If the slug contains an old year but the page is still valuable, changing it creates redirect work and can break links. In many cases, the better option is to keep the historical URL and update the page title and content where necessary.
A practical content-update workflow
- Read the entire old article.
- Identify what is outdated, missing or redundant.
- Verify current facts from authoritative sources.
- Rewrite only if the page can become genuinely useful again.
- Preserve the original publication date.
- Set a real last-updated date.
- Check structured data and the sitemap.
- Request recrawling only for pages worth prioritizing.
The practical rule
Freshness should be the result of fresh work. A clear historical date plus a real modification date is more credible than pretending an old URL was newly published today.
Official reference: Google Search Central guidance on publication and update dates.