Should you change the date when you update a blog post?
Only after a significant update. Keep the original published date, add a visible Updated date, match dateModified to it, and move lastmod at the same time.
LLaunchScaler·Published ·8 min read
Change the date on a blog post only when you have made a significant update, and when you do, keep the original published date and add a visible "Updated" date beside it. Make the datePublished and dateModified values in your Article structured data match what the page shows, and update the sitemap's lastmod at the same moment.
Google treats a new date on unchanged content as a warning sign rather than a freshness signal. Below is what Google says about dates, how to display and mark up both dates, what counts as a significant update, and how dates matter for AI answer engines.
Does changing the date of a blog post help SEO?
Not on its own. Google says it "doesn't depend on a single date factor" and that its systems "look at several factors to determine our best estimate of when a page was published or significantly updated." A new date on an unchanged page is not one of the things that makes a page better, and Google names it as a warning sign.
Google's list of signs that content is made for search engines rather than people includes "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" The next question on the same list covers the bulk version: "Are you adding a lot of new content or removing a lot of older content primarily because you believe it will help your search rankings overall by somehow making your site seem 'fresh?' (No, it won't)."
Freshness does matter for some searches. Google's ranking systems guide describes "query deserves freshness" systems that show fresher content "for queries where it would be expected," such as a film that has just been released. What those systems reward is a page that has current information for a timely query, and that comes from a real update, not a changed date.
How should you display published and updated dates?
Show dates visibly near the headline, with labels that say which is which. Google's own examples are "Posted Feb 4, 2019" and "Last updated: Feb 14, 2018." For an updated post, show both: the original publication date and the date of the last significant update. Readers then see the post's age and its currency at once.
Google's byline date guidance adds rules for the page:
Questions, answered
What people ask about this
01
Should I change the publish date when I update a blog post?
Keep the original published date and add an updated date instead, and only when the content changed substantially. Google lists changing dates to make pages seem fresh without substantial changes as a warning sign.
02
What is the difference between datePublished and dateModified?
Don't show future dates, or the date of an event the page describes; the date "must describe the publication or update date of the page."
If you give a time and timezone, make them correct, "taking into account daylight saving time as appropriate."
"Minimize the presence of other dates on the page." Google suggests removing other dates if the wrong one is being picked up.
A pattern that satisfies all of these, directly under the H1:
<p class="byline">
By <a href="/authors/jane-doe">Jane Doe</a> ·
Published <time datetime="2025-03-10">March 10, 2025</time> ·
Updated <time datetime="2026-09-28">September 28, 2026</time>
</p>
When nothing has changed since publication, show only the published date. An "Updated" label that always equals today's date, which some themes print automatically, is the pattern Google warns about, so turn it off.
How do datePublished and dateModified work?
datePublished is when the article was first published; dateModified is when it was most recently modified. Both go in Article, BlogPosting or NewsArticle structured data as ISO 8601 date-times. Google recommends a timezone on both, and asks that the structured dates "match between the equivalent user-visible and structured values."
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to rotate API keys without downtime",
"datePublished": "2025-03-10T09:00:00+00:00",
"dateModified": "2026-09-28T14:30:00+00:00",
"author": [{ "@type": "Person", "name": "Jane Doe", "url": "https://www.example.com/authors/jane-doe" }]
}
Google's Article documentation lists both as recommended properties and explains that without timezone information it "will default to the timezone used by Googlebot." It also notes the Rich Results Test won't warn you if either is missing, because they are recommended rather than required, so check them yourself.
Property
Means
Changes when
datePublished
First publication
Never, once set
dateModified
Most recent modification
Each significant update
Visible "Published" date
Same as datePublished
Never
Visible "Updated" date
Same as dateModified
Each significant update
Sitemap lastmod
Last significant update
Same moment as dateModified
The table's rule is simple: five values, two dates, always in step.
What counts as a significant update?
A significant update changes what the page tells the reader. Google's sitemap documentation gives the clearest line: "an update to the main content, the structured data, or links on the page is generally considered significant, however an update to the copyright date is not." Rewriting sections, correcting facts and adding new answers qualify; cosmetic edits don't.
Change
Significant?
Update the dates?
New section answering a question the post missed
Yes
Yes
Prices, limits or steps corrected to current values
Yes
Yes
Outdated advice removed or replaced
Yes
Yes
New or changed links in the body
Yes, per Google's sitemap guidance
Yes
Structured data changed
Yes, per Google's sitemap guidance
Yes
Typo or grammar fix
No
No
New featured image with the same content
No
No
Copyright year in the footer
No, per Google
No
Theme or layout change
No
No
When in doubt, ask whether a reader who saw the old version would learn something new from the new one. If yes, it's an update. The content refresh guide covers which posts to update first and what a real refresh changes.
When should you update the sitemap's lastmod?
Update <lastmod> at the same time as dateModified, and only for significant updates. Google says it uses lastmod "if it's consistently and verifiably (for example by comparing to the last modification of the page) accurate," and that the value "should reflect the date and time of the last significant update to the page."
The risk is a CMS that rewrites lastmod on every save, or sets every URL to the build time on every deploy. Google can compare the value with the page, so a lastmod that moves without the page changing becomes a value it cannot trust. Check your sitemap after a trivial edit: if lastmod changed, fix the setting that drives it. The sitemap lastmod guide walks through the common CMS and framework settings.
Do dates matter for AI answer engines?
Some AI search products let developers restrict results to recent sources, which makes an accurate updated date part of whether your page is eligible at all. Perplexity's Search API, for example, can filter results by publication date, by "when content was last modified or updated," and by recency windows such as "week", "month" or "year."
The practical effect: a post you genuinely updated last week, with a visible updated date and a matching dateModified, can qualify for a "past month" answer, while an unchanged post from 2023 cannot. The reverse also holds. Stamping a new date on old content to pass such filters is exactly the practice Google's guidance warns against, and a reader who clicks through to stale content loses trust in the page that cited it. The guide to content freshness in AI citations covers how each engine treats recency.
What if you checked a post and nothing needed to change?
Leave the dates alone. A review that confirms the post is still accurate is not a modification, so dateModified, the visible "Updated" date and lastmod should stay where they are. If you want readers to know the facts were re-checked, say so next to the facts themselves: "Prices checked in September 2026" beside a pricing table tells the reader exactly what was verified without claiming the article changed.
A complete rewrite at the same URL is the opposite case. Keep the original datePublished, because the URL and its history are the same, and set the updated date to the rewrite. If the rewrite answers a different question from the original, it is really a new article: publish it at a new URL and redirect the old one only if the new page replaces it for the same reader.
What steps should you follow when you update a post?
Make the change first, then update every date in one pass so the values stay in step. The order below avoids the common failure where the visible date changes but the structured data or sitemap keeps the old value, or the reverse.
Make the content change and confirm it is significant by the table above.
Keep the visible "Published" date and datePublished exactly as they were.
Set the visible "Updated" date to today.
Set dateModified to the same date, with a timezone.
Confirm the sitemap's lastmod for the URL now shows the same date.
Inspect the URL in Search Console and request indexing once.
Note the date and what changed in your own log, so the next review starts from facts.
Keep dates honest with a steady supply of new articles
The pressure to re-date old posts often comes from not having new ones. LaunchScaler's content engine plans a month of articles from your own Search Console queries, writes one a day in your voice from what your product does, and by default holds every draft in your workspace for you to rewrite, trim or scrap before it publishes to WordPress, Webflow, Ghost, Shopify, Notion, Medium or a signed webhook.
It costs $99/mo per website, with 3 days free before the first charge. Start the engine and the first article is ready on day one.
datePublished is when the article was first published and dateModified is when it was most recently modified, both in ISO 8601 format. Google recommends adding both to Article structured data and making them match the dates shown on the page.
03
Does updating the date of a post improve rankings?
Not by itself. Google looks at several factors to estimate when a page was published or significantly updated, and its helpful content guidance says adding or removing content just to seem fresh won't help.
04
What counts as a significant update to a page?
Google's sitemap documentation counts changes to the main content, the structured data or the links on a page as significant, and says an update to the copyright date is not.
05
Should sitemap lastmod change when I update a post?
Yes, when the update is significant. Google says it uses lastmod only when it is consistently and verifiably accurate, so a lastmod that changes on every trivial save teaches Google to ignore it.
Create and publish a Webflow CMS post with the Data API v2: a cms:write token, the collection's field slugs, HTML rich text and the rate-limit headers.
The Application Passwords section disappears when WordPress can't detect HTTPS or a plugin disables it. Every cause, how to spot it, and the exact fix.
Answer in the first two sentences, write 40 to 60 word passages under question headings, and back claims with sources and statistics. Rules with examples.
