A practical approach to wordpress event schema guide.
Publish Event structured data that matches the visible page and helps search systems understand dates, locations, organisers and offers.
Use the correct event identity
Keep the name, description, canonical URL and organiser consistent with the visible listing.
ExploreDescribe time and place precisely
Include valid start and end dates, time zones, venue or online location, and attendance mode.
ExploreRepresent offers honestly
Only include ticket or offer data that is visible and available. Native paid ticketing is a Pro capability.
Put this guidance into practice.
Validate one complete event
Choose a representative listing and compare every structured property with what a visitor can see.
Test edge cases
Check cancelled, postponed, online, free, sold-out and recurring events where those states apply.
Scale the template carefully
Fix warnings and errors on the representative event before applying the pattern across the archive.
Common questions.
Should hidden fields appear in schema?
No. Structured data should describe the visible event accurately, not expose private or contradictory information.
How should free events be marked?
Use a visible zero price or clearly free offer where the page and schema vocabulary support it. Do not invent a ticket object for a simple RSVP.
Does Pro change the schema rules?
No. Pro paid ticket and offer data must still match the visible checkout and availability.