Update old blog posts by changing what is out of date, keeping the URL, and moving the date only when the page changed in a way a reader would care about. Google says it estimates a page's date from several signals, including the visible date and structured data, and that you should not artificially freshen a story without significant new information [1]. A refresh that edits the facts is worth dating. A refresh that edits the timestamp is not.
Substantive vs cosmetic changes
Ahrefs describes a meaningful refresh as replacing outdated stats, examples, subtopics and screenshots, and says that changing the year in a title is not a real refresh [7]. Use that as the line.
| Change | Substantive? | Move the date? |
|---|---|---|
| Replace a stat, price or screenshot that is no longer true | Yes | Yes |
| Correct a wrong claim or outdated instruction | Yes | Yes |
| Add a subtopic readers now expect | Yes | Yes |
| Rewrite the post for a changed search intent | Yes | Yes |
| Remove a section about something that no longer exists | Yes | Yes |
| Fix a typo or a single broken link | No | No |
| Swap "2023" for "2025" in the title with no other change | No | No |
| Reword sentences, same facts | No | No |
| Template, font or layout change | No | No |
A test that settles most cases: would a returning reader find something different that matters to them? If not, the update is cosmetic.
What to keep
Keep anything still correct and anything other pages depend on:
- The URL. Existing links, bookmarks and citations point to it.
- The original publish date. It stays in the markup and, ideally, on the page.
- Sections that still hold up. Rewriting accurate text only adds risk of introducing errors.
- The anchors of headings that other pages or your own internal links point to.
What to change
Work through the post in this order:
- Check every number, price, version, date and named product against its current source. Replace or remove what no longer holds.
- Re-test every procedure or command. If a step fails now, fix it or delete it.
- Replace screenshots that show an old interface.
- Compare the post against what currently ranks for its main query. If searchers now expect a subtopic you skip, add it.
- Update the title, intro and meta description only if the content they describe changed.
- Check internal links, both the ones in the post and the ones that point to it.
When dateModified may change
Schema.org defines dateModified as the date a CreativeWork was most recently modified [2]. Google's guidance is that a significant update can justify a fresh date, but not an update that adds no significant information [1]. Put together, the rule is:
- Change
dateModifiedwhen you made a substantive change from the table above. - Leave it alone for typo fixes, link repairs, reformatting and template changes.
- Never touch
datePublishedon an existing post.
Format both values in ISO 8601 with the correct time zone designator, and show a clear date on the page [1]. Label it in plain words such as "Published" or "Last updated" [4]. The visible date and the structured data should say the same thing. If a validator reports a date it cannot parse, or the two disagree, the JSON-LD errors guide shows how to find the cause.
Google does not guarantee that a date from your page or markup will show in search results [4]. Date honestly regardless. The date is for readers first.
Write a changelog line
A short note under the post is the most honest way to show what changed. It also keeps you from bumping the date for nothing, because you have to write down what was different.
**Last updated:** May 14, 2025
**Originally published:** June 3, 2022
**Changes in this update**
- Replaced the pricing table with current plans.
- Removed the section on API v1, which is retired.
- Added a section on rate limits.
- Retook all screenshots.
Rules for the note:
- One line per change a reader could verify.
- Do not log typo fixes.
- Keep older entries; do not overwrite them.
- If the update corrects an error in the original, say so.
Rewrite in place, or redirect
Ahrefs separates quick updates from full rewrites, and notes that a full rewrite may fit when the post has to serve a new business goal beyond organic traffic [6]. Both can happen at the same URL.
- Same topic, same intent: edit the existing post. Keep the URL.
- Same topic, new angle: rewrite the content at the existing URL. Date it as a substantive update.
- Two posts covering one topic: pick the stronger one, fold the useful parts of the other into it, and 301 the weaker URL to the survivor. The canonical tags guide covers when a canonical is enough and when a redirect is the right tool.
- Topic no longer relevant: remove the post. Redirect only if a close replacement exists; otherwise let it return 404 or 410.
Do not publish a slightly changed copy of an old story, delete the original and redirect to the copy. Google advises against it [1]. It resets the date without adding information, which is the exact pattern the guidance warns about.
What fake freshness looks like
- Changing the date and nothing else.
- Changing the year in the title or slug and nothing else [7].
- Setting
dateModifiedin markup to the current date on every page load or deploy. - Showing "Updated today" in the template while the content is years old.
- Setting
lastmodin the sitemap to the build time for every URL. The XML sitemap guide covers how to keeplastmodtied to real content changes.
These are cheap to do and easy for readers to spot. A post dated this week that still describes a product the company discontinued costs trust faster than an honest old date does.
After you publish
If you own the page, ask Google to recrawl the URL in Search Console. Google's Refresh Outdated Content tool is meant for pages or images that no longer exist or have been significantly changed, and is not the right tool for a page you own [5].
What to do next
- List your ten oldest posts that still get traffic or links.
- For each, run the checks above and mark it: substantive update, cosmetic fix only, merge, or retire.
- Update the substantive ones in place, then change
dateModified, the visible date and the changelog together. - Leave the cosmetic-only posts with their original dates.
- Request a recrawl for each updated URL.