Event Schema

Event is a schema.org type with a name, startDate, and location. An Offer can hold ticket price and currency. The image is a URL. Dates in the script should match the dates printed on the page.

What you get from Event Schema is concrete. Start and end are part of the event object. A price becomes an Offer when you enter one. The script is not submitted to a calendar for you. Read those results before you paste them into a template, a file, or a ticket. A copied mistake is harder to see later than a mistake still on this page.

A careful pass on Event Schema looks like this. Start with real input, not a placeholder you do not understand. Enter the event name, description, and image URL. Then check the middle of the form, because that is where optional fields change the output. Set the start and end, plus the location. Finish by reading the whole result, not only the first line. Copy the JSON-LD into the event page.

The limit is the part people skip on Event Schema. Match the output to the input you actually typed, then decide whether it belongs on the live site. When the page shows a ticket price. Pick the same currency. A price becomes an Offer when you enter one.

A second reading of Event Schema is worth it because the first pass is easy to rush. Say out loud what the output is claiming. Start and end are part of the event object. A price becomes an Offer when you enter one. The script is not submitted to a calendar for you. Then say what it is not claiming. No. It writes JSON-LD you paste into the event page. When the page shows a ticket price. Pick the same currency. Fill the start and end fields the form shows so the script matches the page. If those two speeches disagree, change the input or pick a different tool. Event Schema will not resolve the disagreement for you.

Read Event Schema once more as a single job. Part 1: Enter the event name, description, and image URL. Part 2: Set the start and end, plus the location. Part 3: Add a ticket price and currency only if the page shows that offer. Part 4: Copy the JSON-LD into the event page. You should be able to point at this in the result: Start and end are part of the event object. You should be able to point at this in the result: A price becomes an Offer when you enter one. You should be able to point at this in the result: The script is not submitted to a calendar for you. Does the event form post the event to a calendar? No. It writes JSON-LD you paste into the event page. When should I add a price? When the page shows a ticket price. Pick the same currency. Are the dates required on the form? Fill the start and end fields the form shows so the script matches the page. Who is Event Schema for? Event Schema is for someone already doing schema tools work who needs create Event schema to rank for concerts, webinars, and meetups. Event is a schema.org type with a name, startDate, and location. An Offer can hold ticket price and currency. The image is a URL. Dates in the script should match the dates printed on the page. The first field was filled with a real value: Enter the event name, description, and image URL. The result was read: Start and end are part of the event object. Optional fields were either filled or left empty on purpose. The copy went into the place the last step names. The boundary in the guide was respected before anything was published.

Keep Event Schema as this step only. When the job moves on, the Local Business Schema is the next page: Local Business Schema writes JSON-LD for a generic local business or a more specific type such as a restaurant or store. The FAQ Schema Generator covers a different piece of the same work: FAQ Schema Generator writes FAQPage JSON-LD from questions and answers you type.