Event Schema for Local Businesses and Venues: A Plain-English Guide

# Event Schema for Local Businesses and Venues: A Plain-English Guide

If you run a yoga studio, a wine bar with weekly tastings, a community theater, or a farmers market, you have something most websites do not: real-world events with dates, times, and places. That is gold for Google — but only if you describe it in a language it understands.

That language is structured data. Specifically, Event schema. Done right, your Saturday workshop, Friday night gig, or end-of-season sale can show up directly in Google Search with its date, location, and a link to buy tickets or RSVP. Done wrong, you get nothing, or worse, a warning in Search Console.

This guide walks through what Event schema is, when it actually helps, how to add it without hiring a developer, and the small mistakes that quietly disqualify your listings.

What Event schema actually does

Schema markup is invisible code you add to a page that describes what is on it. Google reads it and decides whether to display a "rich result" — a fancier search listing with extra details like a date, venue, or price.

For events, that can mean:

• Your event appearing in Google's event search filters
• A more detailed listing in regular search results with date and venue
• Eligibility for Google's event experience on mobile, which often pushes plain blue links down the page

There is no guarantee Google will show a rich result. But you cannot get one without the markup. Think of it as a ticket to the lottery — required, but not sufficient.

When Event schema is the right fit

This is the part most guides skip. Schema is only helpful when the page genuinely matches what users search for. Adding Event schema to a generic "Classes" landing page is a waste at best and a manual action at worst.

Use Event schema when the page is about one specific scheduled occurrence with:

• A name (like "Sunset Yoga at Riverside Park")
• A start date and time
• A clear location (physical address or a virtual URL)
• An organizer
• Optionally: ticket info, performer, price, end date

If your page is "Our weekly classes" with a rotating list, that is not one event. You either need a separate page per event, or you need to mark up each event as a separate Event item on the same page.

Examples that fit cleanly:

• A concert at a music venue
• A pop-up dinner on a specific Friday
• A guided wine tasting at 7pm on a known date
• A community 5K race
• A live author reading at a bookstore
• A grand opening or anniversary sale with a defined window

Examples that do not fit:

• "Yoga classes Monday through Friday" with no specific instance page
• A permanent menu launch
• A general "Events" calendar page (the calendar itself is not an Event)

The minimum required fields

Google's documentation is specific about what an Event needs to qualify for rich results. The required fields are short:

• name — the event name
• startDate — in ISO 8601 format (2026-06-14T19:00:00-04:00)
• location — either a Place with an address, or a VirtualLocation with a URL

That is the floor. To actually be useful and competitive, you also want:

• endDate
• eventStatus — EventScheduled, EventPostponed, EventCancelled, EventRescheduled, or EventMovedOnline
• eventAttendanceMode — OfflineEventAttendanceMode, OnlineEventAttendanceMode, or MixedEventAttendanceMode
• image — a high-quality image URL
• description — what the event is
• offers — price, currency, availability, ticket URL
• performer or organizer — name of the act, speaker, or host

The status and attendance mode fields became important during 2020 and never went away. Skip them and you will see "missing field" warnings in Search Console, even if your listing still shows.

A working example you can copy

Here is a clean JSON-LD block for a real-world local event. Drop it on the event page inside a