EducationEvent

Minimal valid version

The smallest markup that still produces a valid EducationEvent entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "EducationEvent",
  "name": "Hands-On Schema Markup Workshop",
  "startDate": "2026-08-15T09:00:00-04:00",
  "eventStatus": "https://schema.org/EventScheduled",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
  "location": {
    "@type": "Place",
    "name": "Xoo Code Shop Dunmore",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "355 Eagle Butte Ave",
      "addressLocality": "Dunmore",
      "addressRegion": "AB",
      "addressCountry": "CA"
    }
  },
  "teaches": "JSON-LD structured data for Google rich results",
  "educationalLevel": "Beginner",
  "image": "https://xoocode.com/workshops/schema-markup-2026-08/photo-16x9.jpg",
  "description": "Full-day workshop on implementing JSON-LD structured data. Bring a laptop."
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

• Event rich resultprimary

  Google docs

Common EducationEvent mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

1. 01

   Using Event instead of EducationEvent for a workshop

   Wrong

   "@type": "Event" for a training workshop or seminar

   Right

   "@type": "EducationEvent"

   EducationEvent gives you teaches, assesses, and educationalLevel. Generic Event has none of these. Without the subtype, you cannot express what the workshop covers or who it is for. Educational aggregators filter on EducationEvent specifically.

2. 02

   teaches as a vague paragraph

   Wrong

   "teaches": "This workshop will cover various aspects of web development and SEO best practices"

   Right

   "teaches": ["JSON-LD structured data syntax", "Schema.org vocabulary for common types", "Google rich result requirements"]

   teaches should list specific competencies or learning outcomes, not vague descriptions. An array of focused topics is more useful than a sentence. Google and course aggregators match these against skill-based search queries, so specificity matters.

3. 03

   Confusing EducationEvent with Course

   Wrong

   "@type": "EducationEvent" for a 12-week evening class

   Right

   "@type": "Course" with CourseInstances for each session

   EducationEvent is a single event with a date. Course is a structured curriculum that may span multiple sessions. A one-off Saturday workshop is an EducationEvent. A progressive series where each session builds on the previous one is a Course. The distinction matters because Course supports hasCourseInstance, coursePrerequisites, and educational credential properties that EducationEvent does not.

4. 04

   Looking for an instructor property on EducationEvent

   Wrong

   "instructor": { "@type": "Person", "name": "Tomás Herrera" }

   Right

   "performer": { "@type": "Person", "name": "Tomás Herrera", "jobTitle": "Developer Advocate" }

   EducationEvent inherits from Event, not CourseInstance. The instructor property belongs to CourseInstance. On EducationEvent, the instructor goes in performer, which schema.org defines as a presenter or performer at an event. This includes lecturers and workshop leaders. Using instructor on an EducationEvent is not technically wrong (schema.org is lenient), but performer is the canonical property.

Schema properties in this example