Article Schema Hygiene: datePublished, dateModified, and author.name

TL;DR

• Google’s Article docs call out date and author fields that affect machine interpretation and presentation [1].

• Timestamp and byline drift often comes from CMS ambiguity rather than schema syntax errors [1][2].

• Hygiene should be enforced with templates and tests, not one-off manual patches [1][3].

What we know

Google recommends datePublished/dateModified formatting and clear author.name handling, including multiple author formatting [1].

Title-link guidance reinforces that metadata should accurately represent visible content and editorial intent [2].

Sitemap and canonical practices support predictable page identity across updates and republishing flows [3].

Implementation analysis

Model publish/update events explicitly; avoid reusing one timestamp field for multiple editorial actions [1].

Source author data from canonical identity records rather than free-text bylines to prevent profile fragmentation [1][2].

Run schema regression checks in CI and block deploys on missing required fields for key templates [1][3].

What's next

Backfill legacy pages with incomplete author/date fields using controlled migration scripts and sampling audits [1].

Track schema completeness metrics at section level to identify high-risk templates early [3].

Why it matters

Reliable article schema improves machine readability and reduces noisy presentation outcomes in search surfaces [1][2].

Clean timestamps and bylines also cut support load for ‘wrong date’ and attribution disputes [1][3].

Sources

[1] Google Search Central: article structured data (2025-12 update) — https://developers.google.com/search/docs/appearance/structured-data/article

[2] Google Search Central: title links (2025-12 update) — https://developers.google.com/search/docs/appearance/title-link

[3] Google Search Central: build and submit sitemaps (2025-12 update) — https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap