Skip to main content

Event Schema Markup: Which Details to Include and How to Check the JSON-LD on a Live Page

admin10 min read
Event schema markup concept showing a calendar, venue pin and JSON-LD code block

You have a page for a workshop, concert or webinar, and you want event schema markup that tells search engines the right name, date and place without contradicting what visitors read. The short answer: describe one specific event with schema.org/Event JSON-LD, copy every fact from the visible page, then check the published HTML instead of trusting your template.

This guide covers which details to include, a simple single-event pattern, what to change when plans shift, and how to check the live page with AllEasySEO’s View Page Source and Spider Simulator tools. I make no promise of rich results. Markup helps machines read a page; it does not replace a good page.

Event poster and laptop representing event schema markup for one specific event

What Event Schema Markup Describes and When to Use It

Event schema markup is structured data that uses the schema.org Event type. It is usually written as JSON-LD (JavaScript Object Notation for Linked Data), a block inside a script tag that states facts such as the event name, dates, location, attendance format and organizer in a form crawlers can read without guessing from your layout.

Use it on a page about a specific event: a dated class, a ticketed concert, a one-off conference or a single webinar session. Google Search Central recommends a distinct URL focused on each event or each separately ticketed performance. Skip it on a general events archive, on a page that mentions an event in passing, or for vague schedules such as “every Tuesday” with no real dates.

The schema markup benefits are modest but real. You give crawlers explicit labels, and you create a second copy of your key facts that you can audit against the page. Google says it may use event structured data in its event experiences when its guidelines are met, and its general guidelines are clear that correctly marked-up pages are not guaranteed a rich result.

Cards representing the event details that must match the visible page

Which Details to Include and Keep Consistent With the Page

Google’s Event documentation (last updated September 8, 2026) lists name, startDate and a physical Place location as required properties for its event experience. Other details, including endDate, description, organizer, offers and eventStatus, add useful context when they apply. Do not invent fields just to complete a form. Every value should match something a visitor can read on that page.

  • name: the real event title as shown on the page, not the site name or a tab title.
  • startDate: an ISO 8601 date and time with the local UTC offset, such as 2027-05-16T10:00:00-04:00. If only the day is known, use the date alone instead of inventing a midnight start.
  • endDate: only if the page states an end.
  • location: a Place with the venue name and a postal address. The venue name must be the venue, not a repeat of the event name.
  • eventAttendanceMode and eventStatus: in-person, online or mixed, and scheduled, cancelled, postponed or rescheduled.
  • organizer: the person or organization running it. If you already describe the host elsewhere, the guide to organization schema markup shows what to include there.
  • offers: price, currency and ticket URL, only when tickets or registration are visible on the page.

If you prefer a form to hand-written code, the Event Schema Generator builds JSON-LD from fields for dates, venue, status and ticket price. Check its output before publishing: it prints times as you pick them, so add the correct UTC offset yourself, then compare every value with the page.

A Simple Single-Event JSON-LD Pattern

Here is a minimal pattern for one in-person, ticketed event. Every name, address, price and URL is a made-up placeholder on a reserved example domain. Replace each one with true information that is visible on your page; do not publish it unchanged.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "Community Garden Workshop",
  "description": "A two-hour hands-on workshop on starting a vegetable bed.",
  "startDate": "2027-05-16T10:00:00-04:00",
  "endDate": "2027-05-16T12:00:00-04:00",
  "eventStatus": "https://schema.org/EventScheduled",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
  "image": ["https://example.com/photos/garden-workshop.jpg"],
  "location": {
    "@type": "Place",
    "name": "Harbor Community Hall",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "100 Example Street",
      "addressLocality": "Springfield",
      "addressRegion": "NY",
      "postalCode": "12345",
      "addressCountry": "US"
    }
  },
  "organizer": {
    "@type": "Organization",
    "name": "Example Garden Club",
    "url": "https://example.com"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/workshop/tickets",
    "price": "15.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}
</script>

Paste the block once into the page for that event. The offset -04:00 must be the real offset at the venue on that date. If the page says 10:00 AM Eastern, the markup should describe the same moment. For help writing addresses and places consistently, the article on local schema markup covers the same Place and PostalAddress patterns for business locations.

Online Events, Eligibility and What the Markup Can and Cannot Do

Schema.org can describe online events with OnlineEventAttendanceMode and a VirtualLocation that holds a URL, and mixed events with both a virtual and a physical location. That is a statement about vocabulary, not about eligibility. Google Search Central recorded a June 5, 2025 documentation change stating that events eligible for its event experience must be bookable by the general public and held at a physical location. So a valid online-only Event object can be accurate and still not qualify for that Google feature.

Here is what the markup can and cannot do:

  • It can label your facts clearly and give you a record to compare against the visible page.
  • It can make a valid, accurate description available to any consumer of schema.org data.
  • It cannot guarantee a rich result, a ranking or extra traffic.
  • It cannot rescue a page whose visible text is missing, vague or in conflict with the markup.

Treat “valid”, “eligible” and “shown” as three separate outcomes.

Cancelled, Postponed and Rescheduled Events

Plans change, and the markup must change with them. Google’s instructions for event status say the visible page and the structured data should be updated together, and the event page should stay available so the status is not lost.

  1. Cancelled: announce the cancellation visibly on the page and set eventStatus to https://schema.org/EventCancelled. Keep the original startDate and location so the event stays identifiable.
  2. Postponed with no new date: use https://schema.org/EventPostponed and keep the original startDate until a new date is known.
  3. Rescheduled with a new date: publish the new startDate (and endDate if you supply one), set https://schema.org/EventRescheduled and optionally add previousStartDate. When you use previousStartDate, Google says eventStatus must be EventRescheduled.
  4. Update both together: change the headline, date text and notice on the page in the same edit as the JSON-LD, then re-check the published page.

A common slip is changing the page text but leaving the old status in a theme template or plugin field. That is why the live-page check below matters.

Check Event Schema Markup on the Published Page

Checking the published page tells you what a visitor and a crawler fetch, which can differ from what you typed in the editor. Follow these steps.

  1. Read the page first. Open the public event URL and note the visible name, date, time zone, venue or online details, organizer, status and ticket information.
  2. Fetch the HTML. Enter that exact URL in the View Page Source tool, then search the returned HTML for application/ld+json. Find the Event object and compare each value with your notes.
  3. Look for duplicates and stale values. Confirm there is one Event block, not two from a plugin and a theme, and that the status matches any announcement. If you use WordPress, the article on checking a schema markup WordPress setup explains how plugin, theme and manual output can overlap.
  4. Compare the readable text. Submit the same URL to the Spider Simulator. Check that the date, venue and status also appear in the readable-text view, and use its source view to recheck the JSON-LD.

These tools show what their fetch of the HTML contains. The simulator is not Googlebot, and a block missing from the initial source does not prove Google cannot see markup added later by JavaScript. Likewise, a block present in the source does not prove Google has processed it. For JavaScript-injected markup, use Search Console URL Inspection where available to see Google’s fetched or rendered view.

Validate the JSON-LD and Know What a Pass Means

Validation answers narrower questions than most people expect. Paste your code into the Schema Markup Validator, or fetch the live URL, to check JSON-LD syntax and key properties such as name, start date and location. It reports blocks, errors and warnings, so it is a good first pass for a missing comma or an empty field.

Then test the published URL with Google’s Rich Results Test for Google-specific Event issues, and use Search Console URL Inspection where available to investigate what Google fetched or rendered. Keep these checks separate:

  • Syntax: the JSON parses and the types are recognized.
  • Validator pass: the expected properties are present and not empty.
  • Eligibility: the page meets Google’s event guidelines, including a physical location and public booking for its event experience.

Concrete mistakes to look for:

  • A start date or time zone that disagrees with the visible page.
  • A missing or incomplete physical location.
  • A venue name replaced by the event name.
  • A status that still says scheduled after an announcement of cancellation.
  • The example block published with its placeholder values.

Frequently asked questions

When should I use event schema markup?

Use it on a page dedicated to a specific event with a real date and place, such as a workshop, concert or conference. Google recommends a distinct URL for each event or separately ticketed performance. Do not use it on archive pages or for events with no concrete dates.

Can I use event schema markup for an online-only event?

Schema.org lets you describe it with OnlineEventAttendanceMode and a VirtualLocation URL, so the markup can be valid. But Google Search Central says events eligible for its event experience must be bookable by the general public and held at a physical location, so an online-only event should not expect that feature.

How do I mark up a cancelled event?

Announce the cancellation on the page and set eventStatus to https://schema.org/EventCancelled. Google’s instructions say to keep the original startDate and location so the event remains identifiable. Do not delete the page or the markup.

What should I do when an event is postponed or rescheduled?

If there is no new date, use EventPostponed and keep the original startDate. Once a new date is set, publish the new startDate and endDate, use EventRescheduled and optionally add previousStartDate. When previousStartDate is used, Google says eventStatus must be EventRescheduled.

How do I validate event JSON-LD?

Paste the code into the Schema Markup Validator or fetch the live URL to check syntax and key properties. Then run Google’s Rich Results Test on the published URL for Google-specific Event issues, and use Search Console URL Inspection where available to see what Google fetched.

Does valid event schema markup guarantee a rich result?

No. Google’s general structured data guidelines say that even correctly marked-up pages are not guaranteed a rich result. Valid syntax, a validator pass and eligibility are separate checks, and the markup does not promise rankings or traffic.

Is it a problem if the JSON-LD does not appear in View Page Source?

It can be. If the markup is added by JavaScript after load, the initial source may not contain it, though Google may still see it. Check with the Rich Results Test or Search Console URL Inspection, and consider placing the block in the server-delivered HTML so every check agrees.

Next steps

Good event schema markup is plain: one page per event, a real name, an accurate start date with the right offset, a true venue or attendance format, and a status you update the moment plans change. Compare the published HTML with what visitors read, validate it, and treat any rich result as a possibility, not a promise. If you want to see how your block is structured, the Structured Data Visualizer shows pasted JSON-LD as a tree and checks required fields for several schema types.

Related tools and resources on AllEasySEO:

Sources and further reading

Try these free SEO tools

Free, browser-based and no signup needed.

See all free SEO tools