Build Course schema markup with provider, description, cost, and schedule. Generate JSON-LD for education rich results.
The markup Google reads about a course is separate from the page a human reads. Enter the enrollment facts - course title, description, provider name and URL, price and currency, mode, start and end dates - and the tool assembles them into a JSON-LD object following schema.org's Course and CourseInstance types, with the provider nested as an Organization and the cost nested as an Offer. The surprise most users hit: Google's Course rich result only qualifies for courses with clear enrollment information, so name and description alone do not qualify; the markup needs a price, a location, or a start date.
A concrete input and expected output from the current implementation.
Input
Course name: Intro to Python Programming Description: A four-week online course covering Python fundamentals. Provider: Northwind Academy, https://northwind.example.com Price: 49.00 USD (Paid) Course mode: online Start date: 2026-09-01 End date: 2026-09-28
Expected output
{
"@context": "https://schema.org",
"@type": "Course",
"name": "Intro to Python Programming",
"description": "A four-week online course covering Python fundamentals.",
"provider": {
"@type": "Organization",
"name": "Northwind Academy",
"sameAs": "https://northwind.example.com"
},
"hasCourseInstance": {
"@type": "CourseInstance",
"courseMode": "online",
"startDate": "2026-09-01",
"endDate": "2026-09-28",
"offers": {
"@type": "Offer",
"category": "Paid",
"price": "49.00",
"priceCurrency": "USD"
}
}
} Each entered value lands where schema.org expects it: the provider becomes a nested Organization, and mode, dates, and cost sit on a nested CourseInstance with an Offer, which is the structure Google's Course rich result reads. The output contains nothing beyond the entered values reorganized into that nesting.
Every input maps to a schema.org property: name, description, and provider sit on Course itself; courseMode, startDate, and endDate belong to a nested CourseInstance; price, priceCurrency, and category belong to a nested Offer. The tool emits the finished object as JSON-LD, which you paste into a <script type="application/ld+json"> element in the page head.
Google's Course rich result demands more than a title: the markup must carry enrollment information. The tool keeps track of the three accepted signals - an offer with price and currency, a location, or a start date - and flags the output when none of them is present, since such a record cannot qualify no matter how well formed it is.
Yes, if you want rich results for each course. Google reads the markup on each course's own page, so a template that emits the same name and price on every course is wrong for all but one of them. Generate per-course values, then test a sample with Google's Rich Results Test before treating the markup as live.
Not necessarily. A start date or a physical location satisfies the enrollment requirement on its own, so a free in-person course can use its venue. For an online free course, the standard pattern is an offer with price 0, a currency, and category Free, which keeps the markup eligible and unambiguous.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Shorten URLs with local redirect tracking via localStorage. See click counts and generate a QR code for each link.
Build UTM-tagged URLs for campaign tracking with source, medium, campaign, term, and content parameters.
Enter 2+ headlines and see simulated previews in Google results, email subject lines, and social posts side-by-side.
Count characters for Twitter/X, LinkedIn, Facebook, and Instagram with platform-specific limits and warnings.
Calculate click-through rates from impressions and clicks with industry benchmarks and trend analysis.
Check email subject line length against best practices for desktop and mobile with preview text optimization.