How does the visibility of a publication date affect your Google ranking for news content?

Why does Google need a visible date on news content?

Google's ranking algorithms for news rely on the freshness of content. When a user searches for "SNCF strike" or "election results", they want an article published today, not three months ago. To serve this intent, Google must determine with certainty when the content was published.

If the date is absent or hidden at the bottom of the page in microscopic font, Google may make mistakes. It will then guess from other signals: schema.org tags, XML sitemaps, the date of the first crawl, Open Graph metadata. The problem? These sources can contradict each other or be poorly reported. The result: your article ranks 15th when it should be in the top 3.

What does

Is this recommendation consistent with practices observed in the field?

Yes, and it's even one of the few areas where Google is consistent. For years, news sites that hide their dates have noticed inconsistencies in the SERPs: recent articles not appearing in the News tab, incorrect dates displayed in snippets, ranking in "Old news" despite the content being two hours old.

It's also observed that Google Discover — which prioritizes freshness — penalizes content lacking a clear date. Several publishers have seen their Discover traffic plummet after removing the date from their articles to avoid appearing "old". Google needs this temporal anchor to decide if the content deserves to be pushed.

What nuances should be added to this statement?

Müller talks about "news content", but the boundary is blurry. Is a corporate blog article on an industry trend considered "news content"? Should a regularly updated practical guide display the initial publication date or the last modification date? [To be verified] — Google does not provide a clear line of demarcation.

Then, the notion of "well visible" remains subjective. Is it enough to have the date in small font under the title, or should it be bold in 16px font? Müller sidesteps. On high-traffic sites, we've tested: a date in 14px light gray generates more interpretation errors than a date in 16px black. But this remains empirical, not officially documented.

In what cases does this rule not apply or present challenges?

For evergreen content — guides, tutorials, product pages — displaying a date can hurt CTR. A user seeing "published in 2019" might not click, even if the content is updated each quarter. Some publishers then hide the publication date and only display the last modification date.

The problem: if Google ranks this content as "news", it will misfire. Hence the importance of not using NewsArticle in schema.org for evergreen content, even if you update it frequently. Instead, use Article or TechArticle, and prioritize dateModified. But beware — if you completely remove datePublished from the JSON-LD, Google might create a date from the first crawl, which skews everything.

How can you display the date to avoid Google misinterpretation?

Place the publication date above the main content, in the editorial area, ideally just below the title or next to the author's name. Recommended format: "Published on March 12, 2023" or "12/03/2023". Avoid ambiguous formats like "03/12/2023" (March or December?) that can confuse crawlers depending on server config.

Then, double-check with Schema.org markup. Use NewsArticle for pure news, Article for informative content. Fill in datePublished in ISO 8601 format with time zone (e.g., "2023-03-12T08:30:00+01:00"). If you make a substantial update, add dateModified, but do not touch datePublished — it's the historical anchor.

What technical mistakes should be avoided at all costs?

First classic mistake: changing datePublished with every minor modification. You correct a typo, and boom, the CMS automatically updates the date to today. Google sees a "new article", pushes it in Google News, then realizes it's recycled. You lose credibility.

Second mistake: displaying a date in client-side JavaScript that doesn’t match the one seen by Googlebot. If your date is generated dynamically without server rendering, Googlebot might see a page without a date or with a default date. Test with the URL inspection tool in Search Console.

How can you verify that Google interprets your content dates correctly?

Go to Google Search Console > URL Inspection. Paste the URL of a recent article, run the live test. In the "Structured Data" tab, check that datePublished and dateModified are correctly detected. If Google shows "No structured data detected", then your markup is absent or invalid.

Then, search for your article in Google News or standard search. Look at the date displayed in the snippet. If it differs from what you've set, dig deeper: conflict between visible text and JSON-LD, incorrect Open Graph tag, XML sitemap with a wrong lastmod date. Fix it, then force a reindexing via Search Console.

• Display the publication date at the top of the page, in clear text, explicit format (day/month/year)
• Implement Schema.org Article or NewsArticle markup with datePublished and dateModified in ISO 8601 format
• Synchronize the visible date, JSON-LD, Open Graph tags, and XML sitemap
• Never modify datePublished for minor corrections — use dateModified only for substantial revisions
• Test Google's interpretation using the URL inspection tool in Search Console
• Regularly check that the date shown in Google News snippets matches the one provided