Short answer: change the published date only when you have made a real, substantive update to the post, and say so visibly by showing both the original date and a “last updated” date. Resetting dates on posts you merely touched is a short-term trick that readers notice and that search engines have explicitly discouraged. A fresh date supports trust and relevance when the content is actually fresher; it does not create relevance on its own.
Updating old posts is one of the most efficient things a small content team can do. The question that follows is practical: what do you do with the date? This guide explains what dates signal to readers, search engines and AI assistants, when updating them is honest, and how to implement it cleanly.
Why do dates matter at all?
For topics where information changes, readers use dates to judge whether a page is still reliable. Pricing, platform features, regulations and tools all age quickly. A guide to Google Ads settings from three years ago can mislead. Search systems model this too. Google has described freshness as a factor for queries where recency matters, and AI assistants that retrieve live pages tend to prefer recent material for fast-moving subjects. Neither works as a rule that “newer always wins”, because a thorough older page can beat a thin newer one, especially for evergreen topics such as how to write a brief.
What is the difference between published and modified dates?
A post has two dates that matter:
- Date published: when the piece first went live.
- Date modified: when it was last meaningfully changed.
WordPress tracks both. Many themes show only the published date, and many SEO plugins output both in structured data using the datePublished and dateModified properties. Showing both on the page is the most transparent approach. It tells the reader: this started in March and was checked or revised in October.
What counts as a real update?
A useful test is to imagine a reader comparing the old and new versions side by side. Would they see something that changes what they would do? Updates that justify a new modified date include:
- Correcting facts that have changed, such as prices, features, deadlines or legal requirements.
- Adding a new section that answers a question readers now ask.
- Replacing outdated screenshots or steps.
- Rewriting weak passages and fixing broken links, if the changes are substantial.
- Adding fresh data or examples.
Updates that do not justify one are typos, a changed image alt text, a tweaked meta description, or swapping one phrase for a synonym. You can make those edits without touching the date, or let WordPress record the modified time quietly without displaying it prominently.
Is it acceptable to change the published date?
Mostly no. Changing the original published date erases the history of the page. Readers lose context about how old the advice is, and the practice can look like an attempt to appear newer than the content really is. Google’s guidance on dates in search results encourages publishers to show accurate dates and to avoid manipulating them without significant changes; it also advises using structured data and visible dates that agree with each other. We follow a simple rule: leave the published date alone and show an honest modified date.
The exception is a full rewrite so extensive that the old article no longer exists in any meaningful sense. Even then, you can keep the original URL, add a note such as “Originally published in 2024; rewritten in 2026”, and choose to show the newer date as the primary one. Document the change on the page so readers understand.
What do AI assistants do with dates?
Retrieval-based assistants often pull in a page’s visible date, structured data and the surrounding text to judge currency. They also infer age from content itself, for example from mentions of years or product versions. A page showing a modified date this month but still describing a feature that was retired last year gives a mixed signal, and a careful system may favour a page that is consistent. For that reason, a date refresh without content changes is a weak tactic. When you do update, check the entire post for stale references, including the year in the title, examples that cite old numbers, and outdated screenshots. Our guide on why ChatGPT recommends a competitor touches on how consistency affects whether you are trusted as a source.
How do you decide which posts to update?
You will not have time to refresh everything, so prioritise. We look at four groups:
- Posts that used to rank and have slipped. Search Console shows impressions and position over time.
- Posts on fast-moving topics. Platform features, costs, regulations.
- Posts with strong links or traffic. They are worth keeping accurate.
- Posts that support commercial pages. If a post answers a buyer’s question, accuracy affects trust.
Our guide to content decay covers how to find posts losing traffic and decide whether to refresh, merge or retire them. And if a post is stuck on page two, the seven-step triage may reveal that a date is not the problem at all.
How do you show an update properly?
- Make the content changes first.
- Add a short note near the top or bottom: “Updated 16 October 2026: revised pricing and added a section on X.”
- Make sure the visible modified date and the structured data modified date match.
- Resubmit the URL in Google Search Console and, if you use it, notify Bing through IndexNow. See our setup guide.
- Keep the same URL. A new URL for an updated post throws away links and history.
A changelog line is useful for readers and gives assistants a precise summary of what changed. Keep it factual and short.
How often should an evergreen post be reviewed?
It depends on how quickly the subject moves. We use three tiers as a starting point, not a rule. Posts about platform settings, prices or regulations get a review every three to six months, because a single product change can make them wrong. Posts about methods and principles, such as how to write a brief, can wait twelve months, and often need only a read-through and a link check. Posts that are tied to a moment, like a seasonal guide, should be reviewed just before the season returns, so the update lands when readers are looking. Put the review dates in a simple spreadsheet next to the URL and the person responsible. A calendar reminder is cheap, and it turns “we should update old posts” into a task that actually happens.
Common mistakes
Updating the year in the title without updating the content. This is the most common trick and the easiest for readers to spot.
Mass-editing dates with a plugin. A bulk change makes every page look new on the same day, and it is not credible.
Displaying no date at all. For time-sensitive content, hiding the date reduces trust.
Mismatched dates. If the page says one thing and structured data says another, you create ambiguity.
Treating updates as one-time. Put important posts on a calendar for review every six to twelve months.
A small rule that keeps you honest
Before changing a modified date, ask yourself whether you would be comfortable explaining the change to a reader in one sentence. If the sentence is “we corrected the pricing and added a new section”, change the date. If the sentence is “we wanted it to look newer”, don’t. That test protects both your credibility and the long-term value of your archive, and it is also the version of the practice that holds up as search systems grow better at telling real updates from cosmetic ones.