An article has a recent update date but outdated content: how can substantive updates and dates be checked?

List the time-sensitive facts in the article

This applies to old APIs described under a “just updated” label. Identify versions, availability and other changing fields and their direct sources. Publication, event and source-update dates differ. Finding a page today does not make its event current, and a template date is not evidence of editorial review.

Separate publication, content revision and source-check dates

Compare content against current primary documentation for continued applicability, historical labeling or errors. Check builders for unconditional dateModified changes and consistency with visible labels. A source check without substantive revision can have a checked-at date without pretending the article was rewritten.

Verify substance before synchronizing visible dates and markup

Repair outdated conclusions, steps and limitations while preserving the topic. Keep historical material scoped and add current explanations where useful. Do not change old dates without facts. Synchronize fields and labels, retain original publication and document actual changes so readers can assess freshness.

Inspect the live version and meaningful change records

Reopen the published page and verify body version, evidence and dates, including stale caches. Check markup agrees with the page and avoids future modifications or event dates presented as publication. Acceptance means factual state and labels match. A new search-result date does not prove updated content or guarantee AI citations.

This article changed no existing dates or established a particular article is stale. Google uses several date signals and does not guarantee display. Facts need risk-appropriate review schedules. Without source checking, retain the original status instead of batch-fabricating reviewers, check dates or test records.