How can you control the date displayed in Google search results?

Why does Google sometimes display the wrong date?

The confusion comes from the fact that Google automatically detects a date if you don't explicitly specify one. The engine scans visible content, HTML tags, footer elements, modification mentions — basically anything that looks like a date.

The problem? This detection is imperfect. Result: Google may display the date of a recent comment rather than the original publication, or confuse a date mentioned in the text with the actual publication date.

What structured metadata should you use?

Google recommends using Article-type structured data (NewsArticle, BlogPosting, etc.) with the properties datePublished and dateModified. These properties must be in ISO 8601 format.

The schema.org Article is the standard. Other formats like OpenGraph can influence display on social networks, but for SERPs, only schema.org structured data really matters.

What's the difference between datePublished and dateModified?

datePublished indicates the first publication. dateModified signals the last significant update. Google may display one or the other depending on its algorithm and the context of the query.

For evergreen content regularly updated, dateModified can boost perceived freshness. For news content, datePublished remains priority.

• Use schema.org Article with mandatory datePublished
• Add dateModified only if substantial update
• ISO 8601 format with timezone (e.g., 2026-03-05T14:30:00+01:00)
• Avoid dynamic dates automatically generated on each page load
• Test display with Google's rich result testing tool

Is this statement really new?

No. Google has been saying for years that structured data influences date display. What's changing is the clarity of the message: without appropriate metadata, you lose control.

Let's be honest — many sites still rely on automatic detection. It sometimes works, but when it breaks (redesign, CMS change, widget addition), you lose your dates in the SERPs. And that can kill CTR on freshness-sensitive content.

What nuances should be noted?

Google doesn't guarantee it will always display your dateModified. The algorithm may decide to display datePublished if the update is deemed minor — typo fixes, CSS adjustments, etc.

In practice? If you update an article to add a sentence, Google may ignore your dateModified. [To verify]: Google has never precisely documented what constitutes a "significant update" in its eyes.

In what cases does this rule not apply?

For e-commerce sites, product pages don't necessarily need a date. Google generally doesn't display a date on product cards in organic SERPs — except in specific contexts (tech product release, for example).

About pages, Terms & Conditions, contact pages, static landing pages don't need datePublished. Adding a date to this type of content can even harm credibility if it becomes outdated.

What should you do concretely on your site?

Start with an audit of existing structured data. Crawl your site with Screaming Frog or OnCrawl, extract JSON-LD tags or Article-type Microdata, verify that datePublished and dateModified are present and consistent.

Next, test a sample of pages with Google's rich results testing tool. Compare the date displayed in real SERPs with the one declared in your metadata — if they differ, there's a detection or format problem.

What errors should you absolutely avoid?

Error #1: dateModified automatically updated on each visit or page reload. Google detects this and may blacklist your structured data.

Error #2: dateModified earlier than datePublished. It seems obvious, but some poorly configured CMS generate this inconsistency.

Error #3: multiple contradictory dates (one in JSON-LD, another in OpenGraph, a third in a meta tag). Google prioritizes JSON-LD, but inconsistencies create confusion.

How do you verify that everything is in order?

• Implement schema.org Article with datePublished on all editorial content
• Add dateModified only during substantial updates (rewritten content, updated information)
• Use ISO 8601 format with correct timezone
• Test with Google's rich results testing tool
• Crawl the site to detect date inconsistencies
• Monitor SERPs to verify that displayed dates match expectations
• Document the date update policy in an internal editorial guide