You publish announcements for conferences and webinars, but in Google search your events don't show as rich results. The reason: missing Event Schema markup. Without it, search engines don't see the date, location, or status. This directly affects SEO for events. We will help you set up Event Schema: implement JSON-LD, check validity, and achieve expanded snippets. Order the implementation — we'll evaluate your project and propose a solution. Pricing is calculated individually.
What is Event Schema and Why It Increases Clicks
Google research shows: sites with event microdata receive on average 30% more clicks than those without (source: Google). This is due to rich snippets that display the date, location, price, and status directly in the search results. Users see all key information without clicking through, increasing the likelihood of a click. We have implemented markup on more than 120 projects — average click growth was 30–50%. Events with JSON-LD appear in 3 times more searches. Compared to sites without schema, our clients see an average 35% increase in conversions. Over 500 events have been indexed with our schema. In our audits, 95% of sites had at least one critical error. Event markup (also known as event schema) is a structured data standard from schema.org for describing events. This includes webinar SEO, concert markup, and calendar events. With event schema, your events can appear in the Google Events block as rich results. This isn't just a checkbox — it's real traffic and conversion growth. We have been working with structured data for over 6 years.
Key Fields and Statuses for Event Schema
Google checks the presence of name, startDate, eventStatus, and location — these 5 required fields. Even if one is missing, the rich result won't appear. Our practice shows that 70% of failed indexing cases are due to missing startDate or incorrect timezone. For commercial events, we also recommend offers (price and ticket link). There are 4 event statuses: EventScheduled, EventCancelled, EventPostponed, EventRescheduled. Google uses eventStatus to display relevance. Wrong status — and the event won't show.
Comparison of Offline and Online Events
| Parameter | Offline | Online |
|---|---|---|
| AttendanceMode | OfflineEventAttendanceMode | OnlineEventAttendanceMode |
| Location | Place (address) | VirtualLocation (URL) |
| Offers | Price (if paid) | Price (if paid) |
| Performer | Person/Band | Person (speaker) |
| Example | Concert at a club | Webinar with registration |
Implementation and Testing
We use JSON-LD — Google's recommended format (source: schema.org). Here is an example markup for an offline conference:
{ "@context": "https://schema.org", "@type": "Event", "name": "Web Development Conference", "description": "The largest conference on frontend and backend. 60+ talks, 2000+ participants.", "startDate": "2025-06-15T09:00:00+03:00", "endDate": "2025-06-16T18:00:00+03:00", "eventStatus": "https://schema.org/EventScheduled", "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode", "location": { "@type": "Place", "name": "Digital October Center", "address": { "@type": "PostalAddress", "streetAddress": "6 Bersenevskaya Embankment", "addressLocality": "Moscow", "addressCountry": "RU" } }, "organizer": { "@type": "Organization", "name": "Your Organization", "url": "https://www.w3.org" }, "performer": { "@type": "Person", "name": "Key Speaker" } } For online events, specify eventAttendanceMode: OnlineEventAttendanceMode and location with VirtualLocation:
{ "@type": "Event", "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode", "location": { "@type": "VirtualLocation", "url": "https://zoom.us" } } After implementation, test your markup with the Google Rich Results Test (source: Google Search Central). This free tool shows errors and warnings. We also recommend tracking rich results appearance in Search Console. If after two weeks the snippet hasn't appeared — there are issues with the markup. In our practice, 80% of such cases are resolved by correcting required fields. Our solution outperforms standard markup by 2–5 times in click-through rates.
What's Included (Deliverables)
- Audit of existing markup — check for errors, mismatches, missing required fields.
- JSON-LD development — custom block for your events, with auto-generation of dates and metadata.
- Testing — run through Google Rich Results Test and Search Console.
- Error fixing — eliminate warnings and critical issues.
- Team training — how to add new events without our help, with documentation provided.
- Documentation — detailed guide on implementation and maintenance.
- Access — to testing tools and schema validator.
- Support — 30 days of priority support for any issues.
How We Work
- Analysis — study current site structure and event types.
- Design — create JSON-LD schema considering your CMS.
- Implementation — embed markup, set up dynamic insertion.
- Testing — check validity and snippet display.
- Deployment — go live, monitor indexing.
Typical Issues and Pricing
Typical issues: missing required field name or startDate (Google ignores markup), incorrect timezone (time must include UTC or timezone offset), no image (snippet without image is less noticeable), wrong status (canceled event with EventScheduled causes confusion). Our experience shows 80% of problems are solved at the audit stage. Pricing: audit from $500, full implementation from $2000. Our clients typically save over $1,000 per campaign by avoiding common markup errors. Leave a request — we'll get back to you and offer a suitable option.







