usdigitalmarketingindex.com SEO
How should recurring event pages expose accurate dates and avoid obsolete results in organic search?
Updated November 15, 2026
By separating the event series from its individual occurrences. The series gets one stable page that always describes the event and points to the next date. Each occurrence, this year’s and last year’s, gets its own page with its own date, and its own structured data stating that date. When an occurrence passes, its page says so and stops presenting itself as upcoming. Google’s event documentation requires this shape for markup: “Each event MUST have a unique URL (a leaf page) and markup on that URL”, and the event experience “only supports pages that focus on a single event” (Google’s event structured data documentation). A single page that is overwritten each year, or a page whose markup still gives last year’s date, is how a past event appears in search as though it were still to come.
Stable series overview versus dated occurrence
Two kinds of page, with different jobs.
| Page | Purpose | Dates | Event markup |
|---|---|---|---|
| Series page | What the event is, who it is for, when it recurs, where to find the next one | States the pattern, and links to the next occurrence | None of its own for a specific date; it is not a single event |
| Occurrence page | One dated instance: time, place, programme, tickets | A specific start and end date | One Event, for this occurrence |
A recurring event URL and calendar example. The event is fictional. Today, for the purpose of the example, is in November 2026.
| URL | What it is | Date | Status shown |
|---|---|---|---|
| /events/ashby-heating-trade-show/ | Series page | Annual, each May | Links to the 2027 edition |
| /events/ashby-heating-trade-show/2025/ | Occurrence | May 15, 2025 | Past: "This event took place on May 15, 2025" |
| /events/ashby-heating-trade-show/2026/ | Occurrence | May 14, 2026 | Past: "This event took place on May 14, 2026" |
| /events/ashby-heating-trade-show/2027/ | Occurrence | May 13, 2027 | Upcoming: registration open |
For events that repeat often, such as a weekly class, the same principle applies with judgment.
| Pattern | Structure |
|---|---|
| Annual or seasonal event | Series page plus a page per edition |
| Monthly event with distinct programmes | Series page plus a page per date |
| Weekly class, identical each time | Series page with the schedule; individual pages only for sessions people book separately |
| A run of performances of one show | One page for the production; the documentation says that where there are "several different performances across different days, each with individual tickets", a separate Event element is added for each performance |
| Multi-day event | One occurrence page, with both start and end dates, as the documentation specifies |
The series page keeps its URL forever. Links from other sites, bookmarks, and the event’s reputation accumulate there. It is updated when the next date is announced and never becomes out of date in itself, because it describes the series.
Updating event details
When details change, change them everywhere at once.
| Change | Visible page | Structured data |
|---|---|---|
| Date or time moved | New date prominent; note that it changed | startDate and endDate updated; eventStatus set to rescheduled; previousStartDate holds the old date |
| Cancelled | Clear cancellation notice at the top | eventStatus set to cancelled; original dates kept |
| Venue changed | New venue; directions | location updated |
| Online stream added to an in-person event | Stated | The physical location stays; the documentation says events must take place in a physical location |
| Sold out | Stated | Offer availability updated |
| New edition announced | New occurrence page created; series page updated to link to it | New Event on the new page |
The documentation shows the status values in its examples: EventScheduled, EventCancelled, and EventRescheduled, with previousStartDate for a rescheduled event. For a cancelled event, keep the page and the original date and change the status. Deleting the page leaves people who heard about the event with nothing to find.
Rules for accuracy:
- The content guideline is that “Each event must accurately describe the event name, start date, and location”.
- Dates include the time zone offset, as the documentation’s date guidelines require.
- The visible date and the marked-up date are the same.
- The year appears in the visible date. “May 13” alone becomes ambiguous within months.
- Relative wording such as “this Saturday” or “next month” is avoided in page text, since it becomes false as time passes.
- Titles of occurrence pages include the year.
Old-date handling
A past occurrence should not look upcoming, to a reader or to a search engine.
Options for a past occurrence page:
| Option | When it fits | What to do |
|---|---|---|
| Keep as an archive | The edition has lasting interest: recordings, photographs, results, programme | Mark it clearly as past; add what happened; link prominently to the series page and the next edition |
| Redirect to the series page | The page had nothing beyond logistics, and the series continues | Permanent redirect, once the next edition is announced or the event is over |
| Remove | The series has ended and the page has no value | 404 or 410 |
On a kept archive page:
| Element | Treatment |
|---|---|
| Heading and title | Include the year |
| Status line at the top | "This event took place on [date]. The next edition is on [date]." |
| Registration and ticket buttons | Removed, or replaced with a link to the next edition |
| "Register now", "Book today" | Removed |
| Event markup | The start date remains the true, past date; do not advance it; do not mark a past event as scheduled for a future date |
| Offers in markup | Removed or marked unavailable |
| Link to the series page | Prominent |
Do not edit the old page into the new edition. Overwriting /2026/ with 2027 content destroys the record and puts new details at an address that says otherwise. If a site has only ever used one URL for the event, that URL should become the series page, with occurrences created beneath it from now on.
The state to prevent is a page that still says “Register now” with last year’s date in its markup. It presents a past event as available.
A date-driven template prevents this. The page compares the event’s end date with today and switches its own status line, buttons, and offer details when the date passes, without anyone having to remember.
Job postings expire too, and Google’s job-search feature has its own removal procedure, covered in the guide to how expired job postings should be removed from Google’s job-search experience.
Schema and validation
An occurrence’s markup, for the upcoming edition in the example:
{
"@context": "https://schema.org",
"@type": "Event",
"name": "Ashby Heating Trade Show 2027",
"startDate": "2027-05-13T09:00+01:00",
"endDate": "2027-05-13T17:00+01:00",
"eventStatus": "https://schema.org/EventScheduled",
"location": {
"@type": "Place",
"name": "Ashby Exhibition Hall",
"address": {
"@type": "PostalAddress",
"streetAddress": "1 Mill Road",
"addressLocality": "Ashby",
"addressCountry": "GB"
}
},
"description": "Annual trade show for heating engineers and suppliers.",
"organizer": {
"@type": "Organization",
"name": "Example Heating Events",
"url": "https://www.example.com/"
}
}
Placement rules from the documentation:
- The markup goes on the occurrence’s own page, the “leaf page”.
- It recommends adding markup to event posting pages “instead of pages that list schedules or multiple events”. The series page and any calendar listing are of that second kind.
- One Event per occurrence.
Content rules worth checking against the documentation before marking anything up: it excludes things that are not events, such as business hours and short-term discounts, says events must be bookable to the general public, and says events must take place in a physical location.
Validation:
| Check | Method | Pass condition |
|---|---|---|
| Markup valid | Rich Results Test on each occurrence page | Event detected; no errors |
| Dates | Read startDate and endDate | Correct, with time zone offset; equal to the visible date |
| Status | Read eventStatus | Matches reality |
| One event per page | Inspect | A single Event on an occurrence page |
| No stale markup | Crawl all event pages; list startDate values | No page presenting a past date as scheduled with open offers |
| Series page | Inspect | No Event markup for a specific past date |
| Past pages | View | Clearly marked as past; no registration route |
| Internal links | Check navigation and the series page | Point to the next occurrence, not a past one |
| Sitemap | Review | Current occurrence present; redirected or removed past pages absent |
| Search check | Search for the event name | The result shows the upcoming edition or the series page, with the right date |
A scheduled check keeps the set honest: a monthly crawl that lists every page carrying Event markup with its start date, sorted, and flags any whose date has passed while the page still offers registration.
The annual cycle, written down once:
| When | Action |
|---|---|
| Next date confirmed | Create the new occurrence page; add markup; update the series page to link to it |
| Event day passes | Occurrence page switches to past state, automatically |
| Shortly after | Add outcomes, recordings, or photographs if kept as an archive |
| When the following edition is announced | Series page updated again; the oldest thin archives redirected to the series page if they hold nothing of value |
A one-off event that will not happen again has no series to point to, and its page needs a different decision once the date passes, as discussed in the guide to what should happen to an SEO landing page for a one-time event that has ended.
The rule: one permanent page for the series, one dated page with its own markup for each occurrence, the true date on each, and a past occurrence that says it is past.
Add your comment to this answer