Give each event its own public page, put one Event object in JSON-LD on that page, and mark up only facts a visitor can also read there. Complete the name, start date and location first, then add the end date, status, image, ticket link and organizer.

The location depends on how people attend. A venue uses Place with a PostalAddress, an online event uses VirtualLocation, and a hybrid event lists both. When plans change, you edit eventStatus and the dates on the same page instead of publishing a new one.

Google says valid markup does not guarantee a rich result (Google structured-data guidelines). Treat a passing test as a sign that the markup is well formed and eligible, not as a promise that the event will appear.

Key takeaways

  1. Give each event a pageGive each event its own public page with one Event object, and mark up only facts a visitor can also read there.
  2. Complete required fieldsGoogle lists name, startDate and location as required for its Event feature. A physical event also needs location.name and a detailed address.
  3. Match location to attendanceUse Place for a venue, VirtualLocation for online events and both for hybrid. Google says virtual experiences with no real-world component are unsupported for its Event experience.
  4. Change status on the same pageEdit the live page when plans change. Use EventCancelled, EventPostponed or EventRescheduled, and for a new date add previousStartDate and the new startDate.
  5. Write dates with offsetsWrite startDate and endDate in ISO 8601 with the UTC offset for the event's date, because daylight saving time changes the offset during the year.
  6. Test the public URLTest the public URL with the Rich Results Test and a Schema.org validator. A clean result does not promise the event will appear in search.

Complete the Event fields from what the page shows

Open the event page as a visitor would and write down what it states: the event name, the date and time, the venue or the join link, the price, who runs it and who speaks or performs. Each of those facts maps to one property, and the value in the markup should match the visible text exactly. If the page says 10:00 a.m., the markup says 10:00 in the same time zone.

Google lists name, startDate and location as required for its Event feature, and a physical event also needs location.name and a detailed location.address (Google Event structured data). The same page recommends description, endDate, image, offers, organizer and performer, plus eventStatus and eventAttendanceMode when the event changes or is online. These labels belong to one Google feature. Schema.org defines the vocabulary more widely, and other systems may read properties Google does not use (Schema.org Event).

Use the venue's own name in location.name, not the event's name, and keep the description about the event itself rather than repeating the date and address. Pick a canonical url for the event page and use the same value in @id, so the object has one stable identity.

Event properties for Google's Event feature

Hover over or tap a row to highlight it. On small screens the table scrolls sideways.

PropertyStatus for this Google featureWhat to enter
nameRequiredThe actual event name shown on the page.
startDateRequiredISO 8601 date and time, with the UTC offset when known.
locationRequiredA Place for a venue. Physical events also need location.name and a detailed address.
endDateRecommendedThe ending date and time when known.
eventStatusRecommended when status changesA Schema.org status URL such as EventCancelled.
offersRecommended when tickets existTicket url, price, priceCurrency and availability.

Mark up an in-person event

For an event at a venue, location is a Place with a name and a PostalAddress. A PostalAddress is a structured street address, with the street, city, region, postal code and country in separate fields. Add an offers block when people can register or buy tickets, and point its url at the page where they do so.

A woman types on a laptop at a cluttered desk in a community theater office
Figure 1. Fill each Event field from the facts the event page already shows.

The example below uses a fictional workshop on a reserved example domain. Replace every value with the facts on your own page, including the offset in each date (-05:00 here), the image URLs and the price. If the event is free, set price to "0" rather than removing the field.

json
{
  "@context": "https://schema.org",
  "@type": "Event",
  "@id": "https://example.com/events/spring-design-lab",
  "url": "https://example.com/events/spring-design-lab",
  "name": "Spring Design Lab",
  "description": "A fictional hands-on workshop about planning accessible website interfaces.",
  "startDate": "2027-04-17T10:00:00-05:00",
  "endDate": "2027-04-17T15:00:00-05:00",
  "eventStatus": "https://schema.org/EventScheduled",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
  "location": {
    "@type": "Place",
    "name": "Example Arts Hall",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "100 Example Avenue",
      "addressLocality": "Example City",
      "addressRegion": "IL",
      "postalCode": "60000",
      "addressCountry": "US"
    }
  },
  "image": [
    "https://example.com/images/spring-design-lab-16x9.jpg",
    "https://example.com/images/spring-design-lab-4x3.jpg",
    "https://example.com/images/spring-design-lab-1x1.jpg"
  ],
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/events/spring-design-lab/register",
    "price": "45.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "validFrom": "2027-01-15T09:00:00-06:00"
  },
  "organizer": {
    "@type": "Organization",
    "name": "Example Learning Group",
    "url": "https://example.com"
  },
  "performer": {
    "@type": "Organization",
    "name": "Example Learning Group"
  }
}

The image array offers three crops of the same image, which gives a crawler a choice of aspect ratio. Use images that visitors can see on the page and that a crawler is allowed to fetch. If a speaker or band is billed, describe them in performer; if the organizer is also the speaker, as in this example, repeating the organization is fine.

Mark up an online or hybrid event

An online event uses a VirtualLocation, an online place identified by a URL, together with eventAttendanceMode set to OnlineEventAttendanceMode. The URL should be the public event or registration page, not a private meeting link that only registered guests should see.

Schema.org accepts online-only events, but Google says virtual experiences without a real-world component are not supported for its Event experience (Google Event structured data). Keep the markup for other consumers, and do not expect Google's event display from it.

json
{
  "@context": "https://schema.org",
  "@type": "Event",
  "@id": "https://example.com/events/remote-content-clinic",
  "url": "https://example.com/events/remote-content-clinic",
  "name": "Remote Content Clinic",
  "description": "A fictional live online clinic about improving website content structure.",
  "startDate": "2027-05-22T13:00:00-05:00",
  "endDate": "2027-05-22T14:30:00-05:00",
  "eventStatus": "https://schema.org/EventScheduled",
  "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
  "location": {
    "@type": "VirtualLocation",
    "url": "https://example.com/events/remote-content-clinic/join"
  },
  "image": "https://example.com/images/remote-content-clinic.jpg",
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/events/remote-content-clinic/register",
    "price": "0",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "validFrom": "2027-02-01T09:00:00-06:00"
  },
  "organizer": {
    "@type": "Organization",
    "name": "Example Learning Group",
    "url": "https://example.com"
  },
  "performer": {
    "@type": "Person",
    "name": "Example Instructor"
  }
}

A hybrid event happens at a venue and online at the same time. Set eventAttendanceMode to MixedEventAttendanceMode and give location an array with a Place and a VirtualLocation. The fragment below shows only the properties that change from the in-person example; keep the rest of the object as it was.

json
{
  "eventAttendanceMode": "https://schema.org/MixedEventAttendanceMode",
  "location": [
    {
      "@type": "Place",
      "name": "Example Arts Hall",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "100 Example Avenue",
        "addressLocality": "Example City",
        "addressRegion": "IL",
        "postalCode": "60000",
        "addressCountry": "US"
      }
    },
    {
      "@type": "VirtualLocation",
      "url": "https://example.com/events/spring-design-lab/watch"
    }
  ]
}

Update the status when plans change

Keep the event page live and edit it; do not delete it and start over. eventStatus takes a Schema.org status URL, and Google documents five values: EventScheduled, EventCancelled, EventPostponed, EventRescheduled and EventMovedOnline (Google's event-status guidance). Change the visible page text at the same time, so a visitor sees the cancellation or the new date in words.

A cancelled event keeps its original startDate, location and name, with eventStatus set to https://schema.org/EventCancelled. A postponed event keeps its original startDate too, with EventPostponed, until a new date is known. In both cases, update the ticket or registration details so nobody is invited to buy a seat for an event that will not run.

When the new date is known, switch to EventRescheduled. Replace startDate and endDate with the new values and put the former start in previousStartDate. The example below moves a fictional conference from August to September.

json
{
  "@context": "https://schema.org",
  "@type": "Event",
  "@id": "https://example.com/events/example-summit",
  "url": "https://example.com/events/example-summit",
  "name": "Example Summit",
  "description": "A fictional conference about practical website publishing.",
  "startDate": "2027-09-18T09:00:00-05:00",
  "endDate": "2027-09-18T17:00:00-05:00",
  "previousStartDate": "2027-08-21T09:00:00-05:00",
  "eventStatus": "https://schema.org/EventRescheduled",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
  "location": {
    "@type": "Place",
    "name": "Example Conference Center",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "200 Example Boulevard",
      "addressLocality": "Example City",
      "addressRegion": "IL",
      "postalCode": "60000",
      "addressCountry": "US"
    }
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/events/example-summit/tickets",
    "price": "75.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "organizer": {
    "@type": "Organization",
    "name": "Example Events Group",
    "url": "https://example.com"
  }
}

EventMovedOnline fits an event that was planned at a venue and now allows participation online. Pair it with OnlineEventAttendanceMode and a VirtualLocation that holds the public event URL. If the venue stays open and people can also join online, use MixedEventAttendanceMode and list both locations instead.

Write dates and time zones the same way every time

startDate and endDate use ISO 8601, for example 2027-04-17T10:00:00-05:00. The part after the clock time is the UTC offset, which tells a crawler which time zone the start refers to. Include the offset whenever you know it, and make sure it matches the zone the page states.

Remember that the offset changes with daylight saving time. A venue that shows -06:00 in winter may need -05:00 in summer, so check the offset for the date of the event itself, not for today. An event that crosses midnight needs an endDate on the following day.

Each performance with its own tickets deserves its own Event object. A weekly class that sells separate seats each week is several events, not one. The eventSchedule property describes a repeating schedule, and it fits a page that represents the schedule as a whole. Do not combine eventSchedule with a single ambiguous occurrence date on the same object.

Decide between a ticketing platform and your own page

Google says an event published through a ticketing or social platform that takes part in its Event experience may be enough on its own for that experience (Google Event structured data). If your tickets live on such a platform, publishing and maintaining the listing there is a valid route.

A page on your own site still helps in several ways. It can carry directions, accessibility details, branding, registration context and updates that a listing may not. It gives the event a canonical address that you control, and it serves Bing, Yandex, Apple and AI crawlers that read your site directly. Add matching Event markup to that page when it is a distinct event page and the facts are visible on it.

Keep both in step. Do not copy dates, prices or availability from the platform and leave them to go stale; when a date moves, update the site page and the platform listing in the same sitting. Google describes three implementation routes in all: an integrated event publisher, a CMS or plugin, or direct HTML with JSON-LD.

Add Event markup on your platform

Look at what your platform already outputs before you add anything, so the page does not end up with two competing descriptions of the same event. View the rendered page's HTML and search for "@type": "Event" or application/ld+json. If an Event block already exists, edit that block instead of inserting another.

Wix documents automatic Event markup that covers the title, description, dates, status, attendance mode, location and ticket details (Wix default SEO settings). Squarespace documents automatic Event structured data that cannot be edited or removed through normal settings (Squarespace search optimization). Confirm the current menus and plans in each provider's own help pages before relying on them.

On Shopify, structured data usually comes from the theme, and Event support depends on the theme or an app, so read the rendered page rather than assuming (Shopify theme structure). On WordPress, the answer depends on the plugin in use; some SEO plugins document an Event piece, such as Yoast's Event schema piece, and others need a custom block. Check that the output appears on each individual event page.

Webflow supports custom code embeds, so paste the JSON-LD into a page-level embed and publish before you test (Webflow custom code embed). In Next.js, render the JSON-LD from a layout or page component and sanitize any strings that come from a database or CMS (Next.js JSON-LD guide). The general steps for adding code to a site are in the guide to adding schema markup.

Test the page in four steps

Keep four questions apart, because a tool answers only one of them. Is the JSON syntax valid? Does the vocabulary follow Schema.org? Does the page meet the requirements of a Google feature? Is the event actually shown in search? A pass on one does not imply a pass on the next.

A faded calendar card with an arrow pointing to a bright calendar card beside a pin and a globe
Figure 2. When the date moves, update the same page and keep the old start in previousStartDate.

Start with Google's Rich Results Test on the public URL, which reports whether the page is eligible for Google's Event feature and lists missing required fields. Then run the Schema Markup Validator for generic Schema.org structure, since it does not apply Google's feature rules. You can also paste a draft into the Schema Nova validator to catch syntax slips before the page goes live. Google's testing overview describes the roles of both tools (Google structured data documentation).

For Bing, use URL Inspection in Bing Webmaster Tools on the live page. It includes a Markup card that recognizes JSON-LD, Microdata, Microformats, Open Graph and RDFa (Bing URL Inspection). For Yandex, use Yandex Webmaster's structured-data validator, and do not assume that Google's required fields match Yandex's display requirements (Yandex validator).

If JavaScript generates the markup, inspect the rendered HTML, because a crawler may see something different from your editor. After a substantial change, such as a new date or a cancellation, request a recrawl in the tools you use.

Set up Event markup in order

  1. Publish one pageCreate one public page for each event, with name, date, time zone, status and location visible.
  2. Choose the locationUse Place, VirtualLocation or both, and set the matching attendance mode.
  3. Add JSON-LDAdd the Event object, with ticket or registration data if it applies.
  4. Update status changesEdit the same page promptly when an event is cancelled, postponed or rescheduled.
  5. Test the pageRun Google's Rich Results Test, then a Schema.org validator.
  6. Check other enginesUse Bing Webmaster Tools and Yandex where relevant, then request a recrawl after big changes.

Find out why an event does not appear

Work through the cheap causes first. Confirm that the event page is public, not blocked by robots.txt or a noindex tag, and that the markup appears in the rendered HTML. Then compare the markup with the page: a date, price or venue that differs from the visible text is a common reason for markup to be ignored.

Next, check the feature requirements. A physical event needs location.name and a detailed address, and an online-only event is outside Google's Event experience, as noted above. Google also says eligibility does not mean a display, so a clean test result with no enhancement yet is not an error you can fix with more properties.

Bing supports Schema.org in JSON-LD and recognizes event annotations, so the same Event block serves Bing (Bing structured-data documentation). If Siri suggestions matter to you, Apple documents a separate format, Siri Event Suggestions Markup, which is not a substitute for Schema.org Event JSON-LD and involves a domain allow-list request.

To let ChatGPT search surface the event page, make sure robots.txt does not block OAI-SearchBot (OpenAI crawler documentation). Keep the event facts visible, current and crawlable. For the wider question, see whether AI systems use schema markup.

Build the markup with the Event generator

If you would rather not write JSON by hand, the Schema Nova Event generator turns the details of an event page into JSON-LD. Enter what the page shows, replace the example values, and copy the result. For more patterns, the guide to JSON-LD schema examples shows how the same structure applies to other types.

Two related guides help when events sit inside a larger site. Organization schema covers the organizer entity you reference in organizer, and person and author schema covers speakers and performers. To connect the event, its venue and its organizer in one block, see the guide to the JSON-LD graph.

Questions people ask

Do I need Event schema if my event is on a ticketing platform?

Google says a platform that takes part in its Event experience may be sufficient for that experience. A page on your own site still adds directions, accessibility details, branding and a canonical address, and it serves other consumers such as Bing and Yandex. Keep the dates and prices on both in step.

Can Google show an online-only event?

Google says virtual experiences without a real-world component are not supported for its Event experience. Schema.org still accepts online events, so the markup is valid and can serve other systems. Do not promise Google eligibility for an online-only event.

What time zone should I use in startDate?

Use the time zone of the event, written as a UTC offset in the ISO 8601 value, such as 2027-04-17T10:00:00-05:00. Make sure the offset is correct for the event's date, since daylight saving time changes it during the year. The time on the page should match.

Should each recurring performance have its own Event object?

Yes, when each performance has its own date and tickets, give each one its own Event object on its own page. Use eventSchedule only when the page represents the repeating schedule itself. Do not mix a schedule with an ambiguous single occurrence.

Bing says it recognizes event annotations in JSON-LD, and it makes no promise about display. OpenAI documents crawler access for ChatGPT search, and Microsoft says Copilot web search may use Bing to ground answers. Visible facts, valid JSON-LD and crawl access are the supported actions.

Quick check: status or attendance mode?

Choose an answer to see feedback. Nothing is scored or saved.

Question 1 of 3

A concert moves from August 10 to September 14. What changes?

Question 2 of 3

A conference is postponed and no new date is set. What do you use?

Question 3 of 3

A venue event adds a livestream but stays open. Which attendance mode fits?

Event markup terms

Select a term to see its definition.

Event. A scheduled occurrence with a time and a location.