Article dates appear in visible copy, metadata, JSON-LD, and sitemaps, but those fields do not always describe the same event. This study outlines a route-level consistency audit.
Methodology
For each canonical article, extract the visible publication date, datePublished, dateModified, Open Graph article time when present, and sitemap lastmod. Compare normalized calendar dates while preserving their semantic roles. Validate the final rendered HTML rather than only source templates.
Scope
The audit applies to editorial Blog and Research pages with a declared publication date. It does not prescribe whether a site should show an update date; it tests whether the chosen representation is accurate and consistent.
Findings
Sitemap lastmod may reflect a build or meaningful update and should not be used alone as a publication-date census. The strongest release check pairs the reader-visible date with datePublished, then evaluates modification signals separately.
Inference boundaries
Date agreement shows that page surfaces communicate the same editorial history at fetch time. It does not prove when a search engine first discovered or indexed the page.
Limitations
Timezone conversion can shift timestamps near midnight. Cached HTML can also temporarily disagree across edges. Auditors should record the fetch time, timezone rule, and response headers when investigating mismatches.
Sources
Sources
- https://developers.google.com/search/docs/appearance/publication-dates
- https://schema.org/datePublished