Why does Google sometimes show the original publish date instead of the update date?

Which date does Google really prioritize in search results?

John Mueller's response breaks a long-held misconception: Google does not simply read your datePublished or dateModified markup and mechanically display it. The algorithms evaluate which timestamp provides the most value to the user in the specific context of their query.

Specifically, if someone searches for a fundamental SEO guide, Google may determine that the original publish date (2018) is more relevant than the last minor update (typo corrections in 2023). Conversely, for a query about new tax rules, the recent modification date will be preferred because freshness is critical.

How does Google determine which date to display?

Mueller remains deliberately vague about the exact criteria. We know that contextual algorithms analyze multiple signals: the type of content (evergreen vs news), the detected search intent, the extent of changes made to the content, and likely the consistency between the markup and the actual content of the page.

What complicates matters is that Google can ignore your markup if it detects manipulation. If you change the modified date every week without making substantial content changes, the algorithm may revert to the original publish date. This is an anti-abuse mechanism designed to maintain the relevance of displayed dates.

Does this logic apply equally to all types of content?

No, and this is where it gets interesting. News content follows distinct rules where freshness is almost always favored. For classic informational content, Google has greater latitude for interpretation.

A regularly updated evergreen technical blog post may see Google alternate between the two dates depending on queries. A product page updated to reflect a new price will likely display the modification date. The very nature of the content influences the algorithm's choice.

• Google does not blindly rely on the datePublished/dateModified markup
• The user query context plays a decisive role in choosing the displayed date
• Substantial changes carry more weight than cosmetic adjustments
• Date manipulation without real content changes can be detected and ignored
• News vs evergreen content are not treated with the same logic

Is this statement consistent with on-the-ground observations?

Yes, and it confirms what many of us have observed for years. Sites that republish slightly edited old content with a new modified date do not consistently see that date displayed in the SERPs. Google has clearly built filters to detect superficial updates.

What remains unclear is the exact threshold that defines a substantial change. Is changing 10% of the text enough? Does an entire section need to be added? Mueller provides no figures, likely to prevent SEOs from mechanically optimizing around a precise percentage. [To be verified] through A/B testing on different volumes of modification.

In what situations does this rule pose a problem for SEOs?

The first troublesome case: annual updates of guides. You enrich your SEO guide every year with the latest trends, but Google continues to show the date from 2019. For the user, it feels like outdated content, even if that's incorrect. The result is a low CTR despite up-to-date content.

The second issue: product pages where the descriptive content remains stable but the price, availability, or specs change. Google may decide that these changes do not warrant displaying the new date, while for the buyer, that's the information that matters. The algorithm's logic does not always align with business value.

What nuances should be added to this statement?

Mueller speaks of user relevance, but it is Google that decides what is relevant. This algorithmic subjectivity can create absurd situations where freshly updated content shows an old date because the algorithm poorly assessed the extent of the changes.

Another blind spot: Mueller does not mention the role of the XML sitemap. If your sitemap indicates a recent lastmod but the content hasn't truly changed, Google may cross-reference these signals and conclude that there's an attempt at manipulation. Consistency among all your freshness signals probably matters more than isolated markup.

What practical steps should be taken to maximize the chances of displaying the correct date?

The first rule: only change the modified date if you substantially modify the content. No cosmetic updates just to appear fresh. Google has the technical means to compare crawled versions and detect if you only changed three words.

The second approach: when updating content, add a visible "Last updated" section with a summary of the changes. This provides a human signal in addition to technical markup, and Google can analyze this text to assess the substantiality of the modification.

How should you structure your date markup to avoid pitfalls?

Use Schema.org Article with distinct datePublished AND dateModified. Never remove datePublished, even if you want to push the modification date. Google needs both to make its contextual choice.

For regularly enriched evergreen content, consider adding a version property or a structured changelog. Even if Google does not exploit it directly today, this strengthens the validity of your modified date and may influence the qualitative assessment of the content.

What mistakes should absolutely be avoided?

Do not tamper with dates to simulate artificial freshness. Changing the modified date every week on static content will eventually be detected, and Google will likely revert to the original publish date permanently.

Avoid inconsistencies among your signals: if your XML sitemap indicates a lastmod but neither the content nor the on-page markup reflect this change, you create confusion. Google may then make an arbitrary choice or completely ignore your dates.

• Ensure your CMS does not update dateModified for non-editorial changes (admin logins, CSS/JS modifications)
• Add a visible note "Updated on [date]" with a summary of changes for major updates
• Maintain both datePublished AND dateModified in Schema.org markup, never one without the other
• Audit key pages to check which date Google is actually displaying in the SERPs vs what you've marked up
• Synchronize dates between the XML sitemap, Schema.org markup, and visible display on the page
• Document substantial updates in a structured changelog