Separate the event brand from the edition
A stable conference overview can explain audience, subject, organiser and the value of attending. An edition page records a particular date, venue, programme and speakers. Decide which information belongs to each layer before changing URLs. If every edition overwrites the same page, visitors may lose programme history; if everything moves to a new microsite annually, the event’s useful content can become fragmented.
The structure should serve delegates and organisers first, with a clear route between editions.
Inventory the previous event before changing it
List programme pages, speaker profiles, exhibitor information, sponsor pages, ticket links, session recordings and downloads. Identify pages that still attract relevant visitors or earn useful references. Check permissions before retaining speaker material, slides or recordings. A link to last year’s booking form should not remain the main action simply because it is buried in an old PDF.
Record which content is evergreen, edition-specific, superseded or no longer appropriate to retain.
Choose an honest treatment for each URL
| Page | Suggested treatment |
|---|---|
| Past edition overview | Mark clearly as past and link to the upcoming edition |
| Useful session recording | Retain with date, context and appropriate permissions |
| Obsolete ticket purchase | Close the action and provide a clear next step |
| Content genuinely replaced elsewhere | Assess a direct relevant redirect |
Do not redirect every archive URL to an unrelated registration page. People following an old citation may be looking for the original session, not a new ticket.
Publish the next edition in useful stages
When the date or venue is not confirmed, say so. Do not fabricate an agenda to make a page look complete. Publish the confirmed information, explain who the event serves and give a suitable notification or enquiry route. Update programme, accessibility, travel and registration information as decisions are approved. Make the current edition easy to find from the event overview and relevant archive pages.
For event structured data, describe the actual edition and check eligibility against Google’s current documentation.
Connect acquisition to registration
Separate delegate sales, sponsor enquiries and exhibitor applications in the measurement plan. Test the registration provider, payment journey and confirmation. Campaign attribution can be lost when users move domains, so validate a completed transaction rather than counting only clicks on the ticket button. Review cancellation and refund treatment before comparing revenue.
Our published conference marketing work illustrates relevant experience; it does not establish a guaranteed outcome for a new edition.
Maintain the archive as an asset
Assign ownership after the event, not only during the launch rush. Check broken links, media permissions, outdated contact details and accidental live booking actions. Use substantive programme history to demonstrate the event’s focus without implying that past speakers will return. Keep a documented URL plan for the next edition so search, content, ticketing and development teams do not make conflicting changes independently.
Common questions
Should the year be in the URL?
It can be useful for a genuine edition archive, but it is not mandatory. Choose a consistent structure that supports both the ongoing event and its history.
Can we reuse old speaker biographies?
Only when accurate, useful and permitted. Label the edition clearly and do not imply a past speaker is confirmed for the next event.