Published vs Updated Dates: How to Show Dates Google Trusts

Many site owners believe a simple trick keeps their pages looking fresh in Google: change the date at the top of the post to today, hit update, and wait for traffic to come back. Others go the opposite way and hide every date on the site, worried that an old date will scare clicks away.

Both habits come from the same real worry. People do look at dates in search results, especially for topics that change, and an old date next to your result can make a searcher pick the competitor above you. But Google does not simply read whatever date you print. It estimates a date from several signals, and it has clear rules about which dates it trusts.

Let me explain how Google picks the date it shows, the difference between a published date and an updated date, how to set up visible dates and schema so they agree, when hiding dates is a sensible choice, and why fake updates are a bad bet. I will finish with a troubleshooting table for the most common “Google is showing the wrong date” problems.

How Google decides which date to show next to your result

Google calls the date it sometimes shows in a result a byline date. The important word in its own definition is “estimates”:

“A byline date is the date that Google estimates that the web page was updated or published.”

— Google Search Central, Influence your byline dates in Google Search

In plain words, Google looks at several clues and makes its own call. According to the same Search Central page (last updated December 2025), Google does not rely on one single factor. It also says it may show the date when it seems useful to the searcher, and that there is no guarantee it will show one at all.

The clues Google can use include:

• The date you show on the page, especially a clearly labeled one near the title, such as “Published March 3, 2026”.
• Structured data, mainly the datePublished and dateModified properties in Article markup.
• Other dates it finds on the page, such as dates in comments, event dates, dates inside the content or dates in related-post widgets. These are the ones that cause confusion.
• What Google itself observed, such as when it first discovered the URL and whether the content really changed between crawls.

That last point is why tricks fail. If the date says “updated today” but Google’s copy of the page from last month has the same text, the clues disagree. When clues disagree, Google is free to ignore yours.

For a quick beginner’s background on why freshness matters at all, see our lesson on refreshing, merging or deleting old content. In this guide I want to stay on the date itself.

Published date or last-updated date: which one should you show?

These two dates answer different questions for the reader:

• The published date says “when was this first written?” It matters for news, opinion pieces, announcements and anything that describes a moment in time.
• The last-updated date says “can I still trust this?” It matters for guides, tutorials, pricing pages, comparisons and anything a reader will act on.

You do not have to choose. Showing both is often the most honest option, and Google’s documentation allows both datePublished and dateModified in markup. The question is which one you put first and make most visible.

Type of page	Date to make prominent	Why
News article or press release	Published date (plus an “Updated” line if facts changed)	Readers need to know when the event was reported
How-to guide or tutorial	Last-updated date, with published date smaller	Readers want to know the steps still work
Software or tool comparison	Last-updated date	Prices and features change often
Opinion or case-style essay	Published date	The view belongs to a moment in time
Recipe or evergreen explainer	Either, or none (see below)	The content rarely goes out of date
Service or product page	Usually none	A date adds little and can look stale

A pattern I like for blog posts is simple: “Updated October 14, 2026 · First published May 2, 2023” on one line under the title, with the byline next to it. The reader sees that the page is maintained, and Google sees one clear, labeled pair of dates instead of a guessing game.

If your topic is one where the year in the title helps, there is a separate decision to make there, which I cover in our guide on when to put the year in a title tag. And if your URLs contain dates, read dates in URLs and what they cost you before you add or remove them.

Making the visible date and the schema date agree

This is where most sites slip. The theme prints one date, the SEO plugin outputs another in the schema, and a “related posts” box below the article shows five more. Google’s advice is clear on the main rule:

“Ensure that the date (and optional time and timezone) match between the equivalent user-visible and structured values.”

— Google Search Central, Influence your byline dates in Google Search

What the markup should look like

Google’s Article structured data documentation describes datePublished as the date and time the article was first published and dateModified as the date and time it was most recently modified, both in ISO 8601 format. Both are recommended, not required. Google also recommends adding timezone information, otherwise it falls back to a default timezone.

Here is a clean example for a post first published in May 2023 and updated in October 2026:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Winterize a Garden Irrigation System",
  "datePublished": "2023-05-02T09:00:00+05:30",
  "dateModified": "2026-10-14T11:30:00+05:30",
  "author": [{
    "@type": "Person",
    "name": "Jane Example",
    "url": "https://example.com/authors/jane-example/"
  }]
}
</script>

And the matching visible line on the page:

<p class="byline">By <a href="https://example.com/authors/jane-example/">Jane Example</a> ·
Updated <time datetime="2026-10-14">October 14, 2026</time> ·
First published <time datetime="2023-05-02">May 2, 2023</time></p>

The HTML <time> element is not a Google requirement, but it gives a machine-readable date next to the human one, which costs nothing. If you want the full setup, including publisher and image properties, our guide to Article schema for blogs and publishers walks through it.

A five-minute check for date agreement

1. Open the post and note the date (or dates) printed near the title.
2. Run the URL through Google’s Rich Results Test or view the page source and search for datePublished.
3. Compare the two. Same day? Same timezone? If your schema says 23:30 UTC and your site is in India, the visible date may be one day later. That small mismatch is enough to confuse things.
4. Search the page for other dates: comments, “latest posts” widgets, event dates, footers. Write them down.
5. Check your XML sitemap <lastmod> for the URL. It should match the real last significant change, not today’s date on every URL.

On that last step, Google’s sitemap documentation says it uses lastmod only when it is consistently and verifiably accurate, and that a change to the main content, the structured data or links counts as significant while a change to the copyright date does not. Many CMS plugins refresh lastmod on every tiny save. If that happens site-wide, Google learns to ignore your sitemap dates. Our guide to freshness signals, dates and lastmod for AI search goes deeper on this.

When hiding the date is the sensible choice

Some people remove dates from every page and call it an SEO tactic. I don’t see it that way. Hiding a date does not make a page fresher in Google’s eyes; it only removes one clue. Google can still estimate a date from other signals, and if it can’t find a good one, it may simply show none.

Still, there are honest reasons to leave a visible date off certain pages:

• Service, product and category pages. A plumber’s “Drain cleaning in Leeds” page does not need a date. Nobody judges it by age.
• Glossary or definition pages that explain something that has not changed in years, as long as you really check them.
• Landing pages built for ads or campaigns, where a date would distract.

And there are pages where hiding the date hurts trust:

• Anything with prices, laws, rules, statistics, software steps or health information.
• Comparisons and “best of” lists.
• News and anything time-bound.

A useful test: would a careful reader want to know how old this is before acting on it? If yes, show the date. If you are hiding it because the honest date is embarrassing, the real fix is to update the content, not hide the evidence.

Google’s helpful content guidance also asks whether pages carry a byline where a reader would expect one, and says it strongly encourages accurate authorship information. Dates and bylines usually travel together, so a blog post with no author and no date tends to look less trustworthy to readers, whatever Google does with it.

Why changing the date without changing the page backfires

The “bump the date” trick is common enough that Google calls it out by name. In its self-assessment questions for helpful content, it lists this as a warning sign:

“Are you changing the date of pages to make them seem fresh when the content has not substantially changed?”

— Google Search Central, Creating helpful, reliable, people-first content

Here is how I see the risk, in plain terms:

• It often doesn’t work. Google compares versions of a page. If nothing meaningful changed, it can keep its own estimate and ignore your new date.
• It teaches Google to distrust your signals. If every lastmod and every dateModified on your site changes weekly with no real edits, those fields stop meaning anything for your whole domain.
• It annoys readers. A post that says “Updated this week” but quotes 2022 prices, mentions a retired product or links to dead pages tells the reader you are not honest.
• It is a pattern Google describes as search-engine-first. That is the type of content its systems are designed to reward less.

What counts as a real update?

I suggest a simple rule of thumb for your team. Change the visible “Updated” date only when at least one of these is true:

Change	Update the date?
New section, new steps, or rewritten advice	Yes
Prices, statistics, screenshots or product names refreshed	Yes
Facts corrected that changed the meaning	Yes, and consider a short note saying what changed
Typos, commas, image compression	No
New internal links only	Usually no for the visible date (the sitemap lastmod may still change, as Google counts link changes as significant)
Theme change, new sidebar, footer year	No

If you want a full process for deciding what to refresh, rewrite or retire, our guide on how to update old content to boost rankings covers it step by step.

Dates on evergreen pages: a worked example

Evergreen pages are where date choices get tricky. Let me walk through a hypothetical example so the trade-offs are concrete.

Example (hypothetical): A garden-supply store has a guide called “How to Winterize a Garden Irrigation System.” It was published in May 2023. In Search Console it gets about 40,000 impressions a year and ranks around position 4. The content is still correct, but two of the products it recommends were discontinued, and the photos are from an older model of the controller.

The team has three options:

Option	What they do	Likely effect
A. Bump the date	Change “Published May 2023” to “Updated October 2026”, nothing else	Readers still hit discontinued products. Google may keep its own date estimate. Little upside, some trust risk
B. Hide the date	Remove the date from the template	The old date disappears from the page but Google may still show one it estimated. The stale product advice remains
C. Real refresh	Replace the two products, retake two photos, add a short section on smart controllers, then set “Updated October 2026 · First published May 2023” and update dateModified	Honest fresh date, better page for readers, every signal agrees

Option C takes perhaps three hours. Options A and B take five minutes, and that is exactly why so many sites choose them. In my view, the five-minute options are not shortcuts; they are a way of putting off the work while adding risk.

For truly timeless content, such as a page explaining what a soil pH number means, a reasonable middle path is to show “Reviewed October 2026” after someone has actually checked the page, and to keep dateModified unchanged unless the text changed. Be careful here: a “reviewed” label is only honest if a person really reviewed it.

Before and after any refresh like this, record the page’s clicks, impressions and position so you can see what moved. Our guide on measuring on-page SEO changes explains how to set up a fair comparison.

Dates and click-through: what the data does and doesn’t say

I want to be careful here, because the internet is full of confident claims about dates and clicks. There is good reason to believe freshness matters to searchers for some queries. Ahrefs’ guide on how to improve click-through rate (first published July 2022) suggests highlighting the month or year when a query demands up-to-date information, such as poll results or statistics. The same guide cites Ahrefs’ own finding that Google rewrote title tags 33.4% of the time in a study of 953,276 pages, which is a good reminder that you don’t fully control how your result looks. I explain why that happens in our guide to why Google rewrites title tags.

What I have not seen is reliable public data showing that a date in a snippet raises or lowers click-through rate by a fixed amount across all topics. It depends on the query. For “income tax slabs”, an old date is a reason to skip a result. For “how to tie a bowline knot”, nobody cares. So I treat the effect of dates on clicks as direction, not hard science, and make decisions page by page.

A practical way to judge your own pages: search your main keyword and look at the competitors. If most of the top results show recent dates, your old date stands out. If none show dates, a date on yours is unlikely to be the deciding factor.

Fixing the wrong date in Google results

Sometimes Google shows a date you never intended: a comment date, a date from an event mentioned in the post, or the original date long after a major rewrite. Google’s documentation lists guidelines that help here, including: use a clear, labeled date; don’t specify future dates or the date of an action described on the page; add a time and timezone in markup for precision; and, if Google picks the wrong date, remove or minimize other dates on the page.

Symptom	Likely cause	Fix
Result shows a date from a comment	Comment dates are more prominent than the article date, or the article has no visible date	Add a clear labeled date near the title; make comment dates smaller or show them as “2 days ago”
Result shows an event or deadline date	The post talks about an event, and that date is prominent	Make the byline date clearly labeled; make sure schema dates refer to the page, not the event
Result shows a date one day off	Timezone mismatch between visible date and schema	Add full ISO 8601 time and timezone offset in schema and check they produce the same calendar day
Result still shows the old date after a big rewrite	dateModified not updated, visible date not updated, or Google has not recrawled yet	Update both, request indexing in Search Console, then wait
Result shows a future date	Scheduled post or a template bug	Fix the template; Google says not to specify future dates
Every page shows today’s date	Theme prints the current date, or plugin sets dateModified on each page load	Fix the template to read the stored post dates
Different date for the same page on different queries	Several competing dates on the page	Reduce the number of dates on the page, especially in widgets and sidebars

After any fix, use the URL Inspection tool in Search Console to request a recrawl. Be patient: a changed date in results can take days or weeks to appear, and Google may still decide not to show a date at all.

A quick note on WordPress and Shopify

In WordPress, many themes have a setting to show either the published or the modified date, and most SEO plugins output both in schema automatically. The common trap is a theme that shows the published date while the plugin’s schema leads with the modified date, or the reverse. Check both outputs, as described in the five-minute check above. Our WordPress SEO setup guide covers theme and plugin settings more broadly.

In Shopify, blog articles show a published date by default in most themes, but there is usually no built-in “updated” date. If you refresh articles often, ask your developer to add a custom field for a reviewed or updated date and output it in both the template and the schema.

Questions site owners ask about dates in Google results

Does Google always show a date next to my result?

No. Google shows a byline date only when it thinks the date helps the searcher, and it gives no guarantee. Many evergreen and commercial pages never show one.

Should I put both published and updated dates on a blog post?

For most guides, yes. Make the updated date prominent and keep the original date visible in smaller text. Mark up both with datePublished and dateModified, and make sure they match what readers see.

Will removing dates from my blog improve rankings?

There is no evidence that removing dates improves rankings. It removes a clue for readers and for Google. Hide dates only on pages where a date has no meaning, such as service pages.

Can I update the date after fixing a few typos?

I suggest not. Change the visible updated date when the content changed in a way a reader would notice, such as new steps, new prices or corrected facts. Google specifically warns against changing dates when content has not substantially changed.

Why is Google showing a date from my comments section?

Usually because the article’s own date is missing, hidden or less prominent than the comment dates. Add a clearly labeled date near the title, match it in schema and make comment dates less prominent.

Does the sitemap lastmod date change what Google shows?

Not directly. Google uses lastmod to help schedule crawling, and only trusts it when it is consistently accurate. The date in results comes from Google’s own estimate, which leans on visible and structured dates.

Where to start with your page dates this week

In brief: Google estimates dates from several clues, so your job is to make every clue honest and consistent. Show a clear, labeled date on content where age matters. Keep the schema dates identical to the visible ones, with a timezone. Keep your sitemap lastmod accurate. And change the updated date only when you really updated the page.

Here is how I would spend one afternoon on it:

1. Pick your ten highest-traffic blog posts in Search Console.
2. Run the five-minute date check on each one.
3. Fix any template issue once, so it is fixed site-wide.
4. List the posts that need a real refresh, and schedule that work instead of bumping the date.

If you would like a second pair of eyes on your templates, schema and refresh plan, our SEO team and content writers can help. Get in touch for a quote and tell us which pages matter most to you.

Further reading on published vs updated dates

• Table of Contents and Jump Links for SEO
• Related Posts Modules: Internal Links That Actually Help
• Meta Description Templates for Large Sites

Sources for this guide to dates in Google results

1. Google Search Central: Influence your byline dates in Google Search
2. Google Search Central: Article structured data
3. Google Search Central: Creating helpful, reliable, people-first content
4. Google Search Central: Build and submit a sitemap
5. Google Search Central: SEO Starter Guide
6. Ahrefs: How to Improve CTR