Course Schema Generator: Build Valid JSON-LD for Course Pages

Course structured data tells Google exactly what a page is offering: the name and description of the course, who provides it, and practical details like delivery mode, dates and price. Done well, it gives search engines a clean, machine-readable version of information a visitor would otherwise have to read the whole page to find.

What Google actually requires

Google's documentation lists only name and description as required on the Course type itself. provider is marked recommended rather than required, but skipping it leaves out a basic piece of context, who is actually running this course, so it is worth including on every real page. Everything past that is optional detail that makes the markup more useful without being strictly necessary for validity.

Why hasCourseInstance is worth adding

A CourseInstance nested under hasCourseInstance is where the practical scheduling and pricing information lives: courseMode, startDate, endDate, and a nested offers object for price. A Course entry without any instance data is technically valid but tells a search engine almost nothing beyond a name and a description, which limits how useful the markup actually is for someone comparing options in search results.

Valid courseMode values

Use Online, Onsite or Blended depending on how the course is actually delivered, matching Google's documented guidance for this property. If the same course runs in more than one format, publish a separate CourseInstance entry for each mode rather than trying to combine them into a single instance.