Does Google really choose which date to display in the SERPs?

What date does Google display in snippets?

Google does not simply extract the first date it finds on your page. The algorithm makes a choice: it evaluates which temporal information will be the most useful to the user performing the query, depending on the context.

If someone is looking for a technical tutorial, Google will often prioritize the last updated date to indicate the freshness of the content. For a news article, it is the original publication date that matters. This mechanism is opaque and varies according to queries, sectors, and likely the relevance signals gathered.

How does Google identify these dates?

The engine relies on multiple sources: structured data tags (schema.org Article with datePublished and dateModified), HTML metadata, and the visible content of the page. If your tags are missing or contradictory to what is displayed, Google will make its own judgment, often in an unpredictable way.

In practice, it has been observed that sites that correctly mark their dates with schema.org are more likely to see the desired date displayed. However, there is no guarantee: the algorithm retains control, and some historical CMS without structured markup have their dates extracted from visible text, leading to random results.

Why display both dates on a page?

Mueller recommends indicating both the publication date and the last updated date. It is a matter of transparency for the user, but also a signal for Google. If you show only one date, the engine may get it wrong or display nothing at all.

Note: displaying “Updated on [date]” without showing the original date can be misleading if you just edit a comma to simulate freshness. Google detects these manipulations and may demote the content or ignore the date.

• Google chooses which date to display based on the query and user context, not you.
• Mark up in schema.org with datePublished and dateModified to maximize your chances of correct display.
• Display both dates visibly on the page to avoid ambiguity.
• Cosmetic updates fool no one: if the content hasn't truly evolved, changing the date can be counterproductive.
• The absence of a date in the SERPs is not always a drawback, but it reduces the visibility of the freshness signal.

Is this statement consistent with field observations?

Yes and no. On well-marked news sites, it is indeed observed that Google systematically displays the original publication date in the snippets. However, on evergreen content that is regularly updated, the display is erratic: sometimes the publication date, sometimes the modification date, and sometimes no date at all. [To be verified]: Google has never documented the specific criteria that trigger the display of one or the other.

It has also been observed that some niche sites, even with impeccable markup, never have a date displayed. This suggests that other trust factors or content types come into play, but Mueller remains vague on this point. It is impossible to determine whether this relates to domain authority, query category, or a quality threshold.

What nuances should be added to this statement?

Mueller says that displaying both dates “can be useful,” but he does not specify when it is useful and when it is not. For a news article, it’s obvious. But for a product page? A category page? A FAQ? No answer.

Second nuance: Google “sometimes displays” one or the other date. This “sometimes” is the crux of the problem. In short, you have no control. You can do everything correctly and see your dates ignored or misinterpreted. It’s frustrating, but that’s the game.

In what cases does this rule not apply?

For content that is not dated by nature — institutional pages, service pages, landing pages for permanent products — displaying a date may even be counterproductive. A visible date may give the impression that the content is outdated, even if it is not. In these situations, it’s better not to markup any date at all.

Another edge case: heavily revised content, like comprehensive guides updated every quarter. If you change 80% of the text, which publication date should you keep? The original? The new one? Some sites create a new URL, while others update the existing one. Google has never resolved this question, and practices vary widely.

What concrete actions should you take on your pages?

First action: systematically markup your articles and dated content with the schema.org Article properties (or NewsArticle, BlogPosting according to the type). Provide at least datePublished and dateModified. If you never modify the content, dateModified can be the same as datePublished, but it must still be provided.

Second action: display these dates visibly for the user, above or below the title. Readable format, no cryptic mention. If you only display “Updated on,” also add “Published on.” This transparency helps Google and reassures the reader.

What errors should you absolutely avoid?

Classic error: updating the modification date every time you correct a typo. If the content hasn’t truly evolved, this practice dilutes the signal and may be interpreted as manipulation. Reserve changing dateModified for substantial revisions.

Another trap: not synchronizing the visible date with the date marked up in schema.org. If your page displays “Published on March 12, 2023” but your markup indicates “2021-03-12,” Google detects the inconsistency and may ignore both. Check that your CMS or template generates the correct values in both places.

How to check if your markup is correct?

Use Google's Structured Data Testing Tool (Rich Results Test) or the schema.org validator. Paste the URL of a few representative articles and check that datePublished and dateModified are detected, in the correct ISO 8601 format (YYYY-MM-DD or with full time).

Then, inspect your snippets in Search Console: enable the “Appearance in Search Results” report and check whether dates are displayed. If they are absent while your markup is clean, it’s probably a Google choice related to the query type or the trust given to the domain. There’s nothing you can do about it, but at least you’ll know.

• Markup all dated content pages with schema.org Article, datePublished and dateModified
• Display both dates visibly and readably for the user
• Change the update date only during substantial content revisions
• Synchronize visible dates and dates marked up in schema.org
• Check your markup with the Rich Results Test and monitor display in Search Console
• Do not force the display of a date on evergreen or institutional content if it is not relevant