Skip to content

Event schema when an event is cancelled or rescheduled

Update an event's visible notice and structured status without losing its identity. Check original dates, new dates, ticket links, and partner copies.

By Crawlito · 5 min read

In short

  • A cancelled event retains its identifying date and location while its status changes.
  • A postponed event can retain its original date until a replacement date is known.
  • A rescheduled event needs the new date and a clear explanation for people holding old tickets.
On this page

When an event is cancelled or moved, update its public notice and Event structured data together. Preserve the identity of the original event, use the status matching what the organizer has confirmed, and check the ticket link. Google documents distinct handling for cancellation, postponement without a known date, and rescheduling to a new date. Google’s event structured data guidance

Establish which event changed

Identify the exact performance, workshop, or session using its public URL and the organizer's event ID. A series can have several events with the same name at different times. An update intended for Saturday evening should not cancel the Friday matinee or next month's workshop. Record the original local date, timezone, venue, ticket provider, and the confirmed new state.

Ask the organizer to distinguish a delay with no replacement date from a confirmed new schedule. “We hope to move it to next month” is insufficient for publishing a new start date. A website editor can communicate that the date is pending while preserving the details people use to identify their booking. Keep the notice easy to find near the event heading and purchase controls.

Trace the entry points a ticket holder is likely to use. The public event page, confirmation email link, venue calendar, and external ticket provider may all resolve differently. Open the known public links and save their current messages. A correct announcement on the homepage can coexist with an event page still accepting sales.

Match the status to the organizer's decision

For cancellation, Google asks publishers to retain identifying properties such as the original start date and location and set eventStatus to EventCancelled. For postponement with an unknown replacement date, retain the identifying details and use EventPostponed. When the replacement date is confirmed, update the dates and use the documented rescheduling fields.

The fragment below illustrates a fictional workshop moved from one known date to another. Merge it into the event's existing complete markup, keeping its identity and other accurate information. Use the actual timezone offset applicable to the venue on each date.

json
{
  "@type": "Event",
  "name": "Example repair workshop",
  "eventStatus": "https://schema.org/EventRescheduled",
  "previousStartDate": "2026-11-20T18:00:00+03:00",
  "startDate": "2026-12-04T18:00:00+03:00"
}

Check the visible notice against those values. A headline saying “Postponed, date to follow” conflicts with structured data declaring a new date. A date picker can also update the start while leaving an earlier end time, creating an impossible interval. Review the date pair and duration as one change.

Keep the article's own publication date separate from the event schedule. A news report about the postponement may be published today while the event remains identified by its original date. The article date guide helps prevent an event date from being copied into the wrong field.

Preserve the public URL people already have

Keep a useful destination at the address printed on tickets and shared in emails. It should explain the status, the affected session, and where the organizer provides booking instructions. If the publishing system creates a new URL for a replacement event, decide whether it represents the same rescheduled event or a separate new occurrence. Make that relationship visible.

A redirect straight to the general calendar can make a cancellation hard to understand. Someone opening an old ticket link needs to know what happened to their booking. Preserve a clear notice at the original address or provide a specific destination that explains the change. The redirect guide helps test what the public link actually does.

Check the ticketing action independently. A button labeled “Book now” might point to an old offer even when the event title says cancelled. Update or remove the purchase action according to the organizer's confirmed policy and link to the relevant help information. Verify the result without submitting a transaction.

Find duplicate event data in the publishing chain

Inspect all JSON-LD blocks and other event markup in the public response. A theme, calendar extension, and ticket widget can each describe the same event. Updating the main calendar record may leave a widget emitting the old date. Identify the event ID, name, and URL in each occurrence before deciding which component owns the wrong values.

SurfaceEvidence to compare
Visible event detailsStatus notice, local date, venue, purchase action
Structured eventIdentity, status, original or replacement date as appropriate
Venue listingSame session and understandable current notice
Ticket providerSales state and information for existing bookings
Feed or exportThe update sent for the correct event ID

If a scheduled import restores the old state, compare the source revision and update order. A stale feed delivered after a cancellation can overwrite the corrected website unless the integration handles revisions appropriately. Test the closing or rescheduling event twice in a non-production fixture to see whether a retry duplicates the event or reverses its state.

The JSON-LD debugging guide explains how to inspect malformed or duplicated entities. A valid block can still describe the wrong session, so include a content comparison after syntax validation.

Verify the change as a ticket holder

Open the original URL in a fresh browser on a phone and desktop. Confirm the heading, notice, date, venue, and ticket action without relying on an editor's preview. Inspect the public structured data with the current supported testing tool and compare the recognized event with the page's visible information.

Test a neighboring session that should continue as scheduled. It catches a template or shared-record edit applied to an entire series. If the event is rescheduled across a timezone or daylight-saving boundary, confirm the displayed local time with the organizer's authoritative schedule. Avoid calculating a new time by adding a fixed offset to the old formatted string.

Keep a short record of the affected URL, event ID, confirmed status, release time, and observed public result. Search displays and partner listings may update later. Follow their current state separately, using the exact event identity when reporting a remaining stale copy. Your own site's acceptance test is that a person following their existing link gets an accurate answer.

Check a calendar export after the page is corrected

Follow any downloadable calendar link on the event page and inspect the event it represents. The website can show the new date while an independently generated calendar file still describes the original schedule. Compare the event identifier, timezone, start, end, and status information using the calendar integration's documented behavior.

Ask the owner of that export how updates reach people who already subscribed or downloaded a copy. Record which part of the experience your site controls. At minimum, a fresh download from the corrected public page should describe the current confirmed event. Include a neighboring unchanged session in the export test so the rescheduling repair cannot silently alter the entire series.

Frequently asked questions

Should a cancelled event be deleted immediately?

A maintained notice can help people who already have the link. Follow the event's actual retention policy and Google's documented handling for any markup that remains.

What if the new date is still unknown?

Use the postponed state and retain the identifying original details. Publish a confirmed replacement date when the organizer provides it.

Can all dates in a recurring series share one update?

Check the affected occurrences. Separate sessions can have different outcomes even when they share the same title or venue.

Check the affected event page

Run the free page check on the original public event URL after the update. Compare its readable notice and structure with the organizer's confirmed schedule.

Filed under Structure and schema. Topics: structured-data, google, events