Reviewing datePublished and dateModified for a prepared article
For a prepared article, keep preparation, first public publication, and later substantive revision as separate events. Review datePublished and dateModified against that editorial record instead of assigning a new date whenever a file is generated.
Write down the article lifecycle
Create a short event log before choosing date values. Include when the draft was prepared, whether it has actually been published, and what changes have occurred since publication. A planned release is not a completed release. Keep scheduled articles clearly identified in the internal record so a publishing template cannot turn a future intention into an unsupported public history.
- Draft preparation event and artifact.
- Confirmed first public release, if any.
- Later revision description and completion evidence.
- Visible dates and corresponding structured values.
Compare the meaning of the dates
Read the visible article date and any update label alongside the structured values. Determine what the site intends each label to communicate. Google requires structured data to be accurate and reflect visible content. If the page suggests a meaningful editorial update while only a build process ran, investigate that mismatch. Do not use a current timestamp merely to make an unchanged article appear newly reviewed.
Handle corrections explicitly
When the recorded date is wrong, recover the best available publication or revision evidence and note its limits. A source-control event may help establish preparation history but should not automatically be described as public publication. If a revision occurred, summarize what changed so the update date has a clear editorial basis. Where evidence is incomplete, resolve the record with the publisher instead of inventing precision.
Check the publishing output
Before release, inspect a prepared article and confirm its dates match its actual state. After release, verify the public page rather than relying only on the saved draft. Preserve the lifecycle record for future edits. This process supports truthful chronology; correct structured-data syntax does not guarantee a rich result or a particular search display. Add date review to the wider page assessment through /website-analyzer/.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Should every deployment change dateModified?
Do not equate a deployment with an editorial revision. Decide what changed and keep the public date consistent with the history it claims to describe.
Can a prepared article already have a confirmed publication date?
Only if the publication event is supported. A planned future release should remain a plan until the public release is verified.