Choose the page before choosing the markup
Start with the page for one actual event. An agency's delegate acquisition service page describes a service, so adding Event markup there would misrepresent its purpose. A calendar listing several conferences needs different treatment from the page where a visitor can read about one conference and register.
Ask the website owner to check the current Google Event requirements for the particular event. Eligibility has limits, and adding code does not guarantee a special search appearance. If a ticketing platform already supplies the markup, inspect that output before asking another developer to add a second version.
Check the facts against the booking page
Use the organiser's approved event record as the source. Read the displayed page and the structured data together. A date changed in the page editor may still be out of date in a separate plugin. The same problem can affect a venue name or a ticket link.
For a paid event, pay particular attention to the currency and what the advertised offer covers. A US dollar amount entered with GBP as its currency is a different offer. Do not use a zero price to represent a pass whose price is still undecided. Where complimentary admission is restricted, make the eligibility conditions clear on the page and ask the implementer how the offer should be represented.
Give changes an owner
A cancellation can reach the email team before the website team. Add the public event page and its markup to the same change request as the attendee announcement. The person who closes the request should check both versions after the update.
Keep a record of the old and new details when moving an event. Google's documentation explains how event status and rescheduled dates should be represented. Follow the current instructions for the actual change; simply deleting the old date can remove information that visitors and search engines still need.
Test the published URL
Google recommends its Rich Results Test for validating structured data. Run it against the published page and deal with errors before treating the implementation as complete. Save the result with the URL and date so another person can reproduce the check.
Then read the page normally. A technically valid test will not tell you whether the programme sounds useful to the intended audience or whether the invitation promises the wrong pass. Summitrix's campaign preparation still needs the organiser's confirmed registration link, audience rules and offer. Structured data belongs in that wider page review.
Sources and further reading
- Google Search Central: Event structured data
- Google Search Central: structured data guidelines
- Google Rich Results Test
Sources checked 27 September 2026. Guidance can change. This article combines cited source information with Summitrix’s proposed working approach.