usdigitalmarketingindex.com SEO
What should happen to an SEO landing page for a one-time event that has ended?
Updated November 15, 2026
Keep the page as an accurate record of what happened, change everything on it that implied the event was still to come, and point visitors to whatever comes next. That means removing or disabling registration, putting the date in the past tense, adding outcomes such as recordings, results, or photos where they exist, and linking to a successor event if there is one. Redirect the page only when a true successor page exists that a visitor to the old one would want. Delete it only when the event left nothing worth recording and nobody links to it. The one thing the page must not do is go on presenting a finished event as upcoming.
Archived factual record
An ended event page still answers questions: when it was, who spoke, what was decided, where the materials are. Convert it from an invitation into a record.
- State at the top that the event has taken place, with its date.
- Replace the registration form with what a visitor now wants: recordings, slides, results, a photo set, a summary.
- Keep the program, speakers, and location as historical fact.
- Remove countdown timers, early-bird prices, and urgency wording.
- Add a link to the next event or to the organizer’s events listing.
A page converted this way continues to be useful to people who attended, people who missed it, and anyone citing it.
Next-year successor page
If the event will happen again, decide how the editions relate.
| Approach | How it works | Suits |
|---|---|---|
| A new page per edition | Each year has its own URL; the old one becomes an archive and links to the new | Events where each edition has its own program worth keeping |
| One permanent page | The same URL is updated for each edition; past editions move to an archive section | Events that are essentially the same each time |
For a true one-time event there is no successor, and the archive is the end state. If a successor is announced later, add the link then.
Redirect versus archive choices
The table separates the two cases the question raises, a cancelled event and an event with a recurring successor, along with the plain completed case.
| Situation | Evidence | Outcome |
|---|---|---|
| Event took place; no successor | Program completed | Archive in place: mark as past, add outcomes |
| Event took place; a successor edition has its own page | New page live | Keep the old page as an archive and link prominently to the new one |
| Event took place; a single permanent page is used for all editions | Site's URL policy | Update the permanent page for the next edition; move this edition's details to an archive section |
| Event was cancelled; no replacement | Cancellation notice | Keep the page, state clearly that it was cancelled and when, explain refunds or next steps, remove registration |
| Event was cancelled and replaced by a different event | Replacement announced | State the cancellation and link to the replacement; redirect only if the replacement serves the same audience and purpose |
| Event was postponed to a new date | New date confirmed | Keep the same page and update the date, marking it as rescheduled |
| Thin page for a minor event; no outcomes, no links from other sites | Nothing to archive | Remove, returning a not-found status |
Two cautions on redirects. A redirect makes the old page’s content unreachable, so anything worth keeping must be moved first. And a redirect to a page about a different event, or to the home page, leaves the visitor without what they were looking for.
A cancelled event deserves particular care. People search for it to find out what happened. A page that says so plainly, with the date of the announcement and what ticket holders should do, serves them. Deleting the page leaves them with nothing, and leaving it unchanged misleads them.
Updating date and registration signals
Bring every signal on the page into line with the facts.
Visible content:
- Past-tense wording and the actual date
- Registration removed or replaced with a closed notice
- Prices and deadlines removed
Structured data, if the page carries Event markup:
- The dates must be the real dates of the event.
- For a cancelled or rescheduled event, Google’s Event documentation provides status values. It lists EventCancelled, defined as “The event has been canceled”, and EventRescheduled among the options for the eventStatus property (Google’s Event structured data documentation).
- Remove offer details that no longer apply, such as ticket availability.
- The same documentation requires that each event have “a unique URL (a leaf page) and markup on that URL”, which supports giving each edition its own page where editions differ.
Site references:
- Take the event out of upcoming-events listings and navigation.
- Update internal links that describe it as upcoming.
- Keep it in the sitemap if it remains a live archive page.
Check the page a week after the event from a visitor’s point of view. Search for the event’s name, open the page, and confirm that nothing on it invites an action that is no longer possible.
A short checklist for the day after:
- Top-of-page status statement added.
- Registration closed.
- Urgency and pricing removed.
- Outcomes added, or a note saying when they will be.
- Markup updated.
- Listings and links updated.
- Successor linked, if any.
Events that recur on a schedule raise further questions about dates in markup and how each occurrence is addressed. Those are handled in the guide to exposing accurate dates on recurring event pages.
The criterion: after the event, the page should tell the truth about the past and point to the future, or it should not exist.
Add your comment to this answer