Safeguard
Security Guides•

Honest publish and updated dates on technical pages

Show a visible date, match it in datePublished and dateModified, and only bump it when content really changes. What Google's date guidance says.

Safeguard Security Team
3 min read

Show a clear, labeled date on the page, mirror it in datePublished and dateModified, and change the updated date only when the content genuinely changed. Google's guidance asks for consistent dates that describe the page itself, and warns against changing dates to seem fresh.

What Google asks for

Google's date guidance says to show a prominent date and label it clearly, such as "Published" or "Last updated". You can show either or both.

For structured data, use a CreativeWork subtype such as Article or BlogPosting and set datePublished and dateModified. Time and timezone are optional but add precision, and the timezone should be right. Visible and structured dates should match.

Dates should describe when the page was published or updated, not the events it covers, and should not be in the future. Google also says it does not guarantee a byline date will appear in results.

Why honesty matters for technical content

Readers use dates to judge whether a command, version number or policy is still valid. A page claiming to be updated yesterday that still describes a retired flag costs trust, and it can cause a real mistake.

Google's helpful content guidance lists changing dates to make content seem fresh as a warning sign.

A simple update policy

  1. Record the first publish date once. Do not change it.
  2. Change the updated date only for substantive edits: facts, steps, versions, links to sources.
  3. Typo fixes do not need a new date.
  4. State what changed in a short note for big updates.
  5. End the page with a review line that carries the true review date.

A review date is different from a modification date. "Last reviewed" says someone checked the facts on that day, even if nothing needed editing. If you use it, do review.

Example markup

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Rotate an API key safely",
  "datePublished": "2026-10-19T09:00:00+00:00",
  "dateModified": "2026-10-19T09:00:00+00:00"
}

Generate this from the same fields that print the visible date, so they cannot disagree.

Pages with moving facts

Pages on versions, prices or regulations go stale quickly. Name the thing that can change and link to the primary source. If you cannot confirm a fact, say it should be checked rather than guessing.

Quick check

Should I show both published and updated dates?

Google allows either or both. Showing both helps readers judge age and maintenance.

Can I use a future date for a scheduled post?

Google says not to use future dates. Publish when the date is true.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.