Publication-Date Evidence Across Visible Copy and Article Structured Data

Published September 9, 2026.

Publication dates appear in several layers of an article: visible copy, machine-readable HTML, structured data, and sometimes Open Graph metadata. Daily workflows need a single source of truth so these surfaces do not contradict one another.

Research question

What date evidence should an article release verify, and what can that evidence actually prove?

Methodology and scope

We reviewed Google Search Central guidance for Article structured data and byline dates, plus the Schema.org definition of datePublished. We compared the documented properties and consistency recommendations with a static publishing workflow. We did not test rich-result eligibility, measure click-through effects, or infer Google’s displayed date for any specific result.

Findings

Schema.org defines datePublished as the date of first publication or broadcast. Google recommends prominent visible dates and consistent date information, and its Article documentation accepts ISO 8601 date and time values for publication and modification properties. Google can use several signals to estimate a page date; structured data does not force a particular search display.

The distinction between publication and modification matters. Treating every update as a new publication can obscure article history. Conversely, changing visible copy without updating an appropriate modification field may leave readers with incomplete context.

Operating interpretation

At release, compare the visible date, HTML <time> value, Article JSON-LD datePublished, Open Graph publication time, and the editorial record. They should describe the same intended first-publication date. When a substantive later update occurs, preserve the original publication date and add a clearly supported modification date according to policy.

Inspect the deployed HTML rather than only source files. Validate JSON syntax and ensure the structured entity names the same canonical article a reader sees.

Inference limits and limitations

Consistency does not guarantee a rich result, indexing, freshness treatment, or the date Google displays. This synthesis does not resolve edge cases involving timezone boundaries, continuously updated live pages, migrations, republishing policies, or legal definitions of publication. Editors should document those policies before automating date fields.