How do I mark a postponed event in structured data?

Definition: A postponed event uses the Event structured data type with eventStatus set to https://schema.org/EventPostponed while its replacement date remains unknown. Google's instructions retain the original dates during that period, then change the status to EventRescheduled and update the dates when the new schedule is known.

Key facts

• Schema.org's EventPostponed definition describes an event that has been postponed without a new date being set.
• As of 17 October 2026, Google's Event documentation instructs publishers to preserve startDate and location when marking a postponement.
• Schema.org's previousStartDate property records the previously scheduled start date and can repeat when an event is rescheduled multiple times.
• Google's general structured data guidelines require up-to-date information and content that is visible to readers.

What changes while the replacement date is unknown?

The eventStatus property describes the event's status. Google's postponement instructions say to change that property to EventPostponed while preserving the other existing values. In particular, the original startDate and location help Google identify the event.

The following property fragment belongs inside the existing event object:

{
  "eventStatus": "https://schema.org/EventPostponed"
}

This fragment shows the status change only; the complete markup retains the event's other properties, including its original dates. Google requires each event to have a unique URL and markup on that page, with the page focused on a single event.

What changes when the new date is confirmed?

Google's rescheduling guidance says to update startDate and endDate with the new dates. Its postponement instructions also specify changing the status to EventRescheduled once the replacement date is known.

The property previousStartDate holds the old start date. Google lists it as recommended; when it is supplied, Google requires eventStatus to be EventRescheduled.

This extract from Google's rescheduled-event example shows how the dates fit together. It is a property fragment for use within the complete Event object:

{
  "startDate": "2025-07-21T19:00-05:00",
  "endDate": "2025-07-21T23:00-05:00",
  "eventStatus": "https://schema.org/EventRescheduled",
  "previousStartDate": "2025-03-21T19:00-05:00"
}

The new start and end dates describe the replacement schedule; the previous start date preserves the earlier schedule. Google's date guidelines call for the appropriate time-zone offset when a time is supplied. When the day is known but the starting hour is unknown, they recommend a date without an invented time.

How do the other status values fit?

Google's supported status values distinguish these situations:

There is a vocabulary distinction: Schema.org's EventPostponed page says to set previousStartDate, whereas Google's property instructions restrict that field to EventRescheduled. For Google's event feature, its documented combination is EventPostponed with the original startDate until the replacement schedule is known.

How is the updated markup checked?

Google's Event implementation steps specify validation with the Rich Results Test and correction of critical errors. After deployment, the URL Inspection tool checks how Google sees the page; the same instructions allow a recrawl request.

The visible event information also needs the status update: Google's content guidelines require current information and prohibit markup describing content hidden from readers. Testing the markup and checking the event announcement therefore address different parts of the update.

Related terms

• Structured data
• JSON-LD
• How do I test a URL or code snippet with Google's Rich Results Test?
• How does Schema.org validation differ from Google's Rich Results Test?

FAQ

Should I remove the original start date after postponement?

Keep it while the replacement date is unknown. Google's Event status instructions use the original startDate to help identify the event.

Can I omit the status and just leave the old dates?

Google treats an omitted eventStatus as EventScheduled. Set EventPostponed to express that the event is delayed.

What if the event moves more than once?

For a rescheduled event, keep the latest schedule in startDate and endDate. The same documentation allows repeated previousStartDate values for earlier schedules.

Sources

1. Google Search Central, "Event (Event) structured data", updated 8 September 2026
2. Schema.org, "EventPostponed", accessed 17 October 2026
3. Schema.org, "previousStartDate", accessed 17 October 2026
4. Google Search Central, "General structured data guidelines", updated 10 July 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer