ClasesSEO
ES EN
SEO Search Engine Optimization

Publication Dates and SEO: How to Control the Date Google Shows

8 min read Leer en español
Publication Dates and SEO: How to Control the Date Google Shows
Table of contents

The publication date under your search result in Google is not yours to pick: Google estimates it. If your article shows 2024 and you updated it yesterday, that is not a penalty, it is a misreading of your page signals. And it can be fixed.

What a Publication Date Is and Why Google Shows It

Google defines a byline date as the date it estimates that the page was published or updated. That single word, estimates, explains everything that follows: there is no field you fill in and Google obeys. There is a set of signals Google reads and a date it decides to show. The definition lives in its guide to publication dates.

And it shows that date only when it finds it useful: the documentation says Google can expose this information in search results if it is considered useful to the user. It is not a publisher right, it is a search engine decision.

It is not a declared ranking factor either. What changes is the perception of freshness and the click: a result dated two days ago invites a visit, one dated 2023 invites a skip. In Discover and in News that effect multiplies, because there the present is the product.

So the job is not to set the date that suits you. It is to make the correct date the easiest one to find.

How Google Decides Which Date to Show

Google put it plainly: it does not depend on a single date factor because all factors can fail. Its systems look at several signals at once and keep the best estimate of when the page was published or significantly updated.

The usual signals are four:

  • The date visible in the HTML, especially when it is prominent and labelled.
  • Structured data: datePublished and dateModified.
  • The sitemap lastmod, when it is consistent and verifiable.
  • The content itself, which sometimes mentions dates or seasons.

The classic problem appears when a page carries four different dates: the template one, the footer one, the first comment one and the one from an old season. Google picks one, and it may pick the wrong one. The practical consequence is simple: the fewer irrelevant dates you leave lying around, the less room for error. If you want to work sitemaps properly, the lastmod detail is in the sitemap and lastmod guide.

There is a cheap test to see what Google is reading: search for the exact article title in Google and compare the date in the result with the dates your HTML serves. If it matches none of them, you do not have an indexing problem, you have too many signals competing for the same job.

The Minimum Pattern That Works: Visible Date and JSON-LD

Three steps and you cover most of the problem.

Step 1: A Visible, Prominent, Labelled Date

Put the date near the top, not buried in the footer. Label it explicitly: Published, or Last updated. And wrap it in <time datetime="..."> so the human-readable value and the machine value come from the same place.

Step 2: JSON-LD With ISO 8601 and a Timezone

The Article, BlogPosting or NewsArticle markup carries both dates in ISO 8601 format, as described in the Article structured data documentation. A minimal block:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article title",
  "datePublished": "2026-11-19T09:30:00-03:00",
  "dateModified": "2026-11-19T09:30:00-03:00"
}
</script>

The timezone matters more than it looks: if you omit it, Google defaults to the timezone used by Googlebot. And if your country shifts for daylight saving, a date without a timezone can slide a full day in the result.

Step 3: Visible and Structured Data Must Agree

Same instant, same precision. The time may be missing from the visible text even when it is in the markup, but the visible date cannot contradict the JSON-LD. A coherent case measured on this very site: the HTML serves <time datetime="2026-11-18T12:07:24+00:00">18 de noviembre de 2026</time> and the NewsArticle repeats exactly 2026-11-18T12:07:24+00:00 in both properties. Google has nothing to guess. If you need to review the markup, there is the structured data guide for SEO.

The Five Rules Google Actually Wrote

The official publication dates guide is not long, and almost nobody cites it. These are its rules, ordered the way someone auditing a site would use them:

  • Date required, time optional. The time is recommended, with the correct timezone.
  • Consistency. Visible and structured data have to tell the same story.
  • No future dates and no dates of the event you describe. If you write about a March event, that is the event date, not yours: that is what Event markup is for.
  • Minimize other dates. If Google picks the wrong one, start with the leftover dates in the template.
  • No guarantees. The documentation is explicit: following the guidelines helps its systems find and process the information, but does not ensure the date will be shown.

When to Update dateModified and When It Is Just a Trick

Google defines what counts as a significant update for lastmod: a change to the main content, the structured data or the links usually counts; a change to the copyright date in the footer does not. The same logic applies to dateModified.

The anti-pattern is well known and very common: a CMS or plugin that rewrites the date every time you hit save, or a script that sets it to today every morning. The result is a value that changes while nothing else does. Google can detect it and simply ignore it. Worse still: you lose the one honest signal you had.

What does help is keeping a change log in the CMS itself: a short note per edit with what was touched and why. When the moment comes to move dateModified, you know whether the change was substantive or cosmetic, and the decision no longer depends on the editor memory.

When the update is real, the order should be this: check facts and figures, confirm the links still work, rewrite the section that went stale and add what changed in the field. Then, yes, move the date. If nothing substantial changed, leave the date alone. The deeper work is in how to optimize old content.

Google Shows the Wrong Date: What to Do, in Order

  1. Inspect the URL and look at the rendered HTML and the served JSON-LD, not just what the browser inspector shows.
  2. Compare the three sources: visible text, structured data and lastmod. The one that disagrees is the culprit.
  3. Remove or downgrade irrelevant dates: comments, counters, season labels.
  4. Fix, validate and request a recrawl. Without promising 48 hours: real timings are in how long SEO takes to show results.
  5. If the problem is at scale, the Search Console URL Inspection API lets you check in bulk without opening a hundred tabs.

One detail that gets overlooked: the validator you open in a browser may be reading markup injected by JavaScript rather than what the server returns. Always compare against the served HTML tab. If the JSON-LD only exists after scripts run, Googlebot may take much longer to see it, and meanwhile the date estimate is built from whatever does arrive on time.

Dates, Discover and News: Where It Matters Most

Discover asks for content that is timely for current interests, and the date is part of that promise. That is why a refreshed date with no new content does more damage here than anywhere else: it erodes exactly the trust the feed is trying to measure. Steady cadence and honest dates beat any calendar trick. If the site is a news site, there are extra rules of its own, summarised in how to appear in Google News and Top Stories.

The date will not rank you. But it will give you away.

Eight-Point Date Checklist

  • Visible date with an explicit label, inside a <time datetime> element.
  • JSON-LD with datePublished and dateModified in ISO 8601.
  • Timezone included, with daylight saving handled correctly.
  • Visible value and structured value identical.
  • No future dates and no third-party dates in the template.
  • One primary date per page.
  • lastmod that reflects real changes, not saves.
  • All three sources reviewed after every update.

We use cookies to improve your experience and analyze site traffic. By continuing to browse you accept their use.

Privacy