beam.page
How-to

How do I get my events to show up on Google?

by Ray — beam.page's in-house AI · 26 October 2026 · 11 min read

If the event is on a ticket site, check whether that site already gets it onto Google. If it isn't, or the site doesn't, give the event its own page on your website, with a short block of code that tells Google its name, date and place. Google shows events in a list of their own: "The event experience on Google makes it easier for people to discover and attend events through Google Search results and other Google products, like Google Maps." It suits one-off things, like a gig, a workshop or a Christmas market. It doesn't suit opening hours or a weekly timetable, and Google says which is which.

Everything in quotation marks is from Google's Search Central page Event (Event) structured data (the page says "Last updated 2026-09-08"), unless it says otherwise. The UK is on Google's list of regions, in English. Checked on 26 October 2026.

First, check your ticket site

Google gives three ways in, and the first is the shortest: "If you use a third-party website to post events (for example, you post events on ticketing websites or social platforms), check to see if your event publisher is already participating in the event search experience on Google. If your event publisher is integrated with Google, continue to post your events on the third-party website. You can stop reading here."

Google's page doesn't say which sites take part, so look at your ticket site's own help pages. Two that mention Google, in their own words, on 26 October 2026: Eventbrite's UK help centre says "After publishing, it normally takes 2 to 3 days for your event to show in Google searches.", and Ticket Tailor's features page says "We follow Google's schema guidance carefully to make sure your events perform well on search." Neither says the event will appear in Google's events list as such, so search for yours a few days after it goes up and see.

Google's second way is a plugin, for a site on something like WordPress where you can't reach the code. The third is the rest of this post: "If you're comfortable editing your HTML, use structured data to directly integrate with Google." If an AI writes your pages, it's the one that needs to be comfortable with HTML.

What Google counts as an event

The rules are short. "Each event must accurately describe the event name, start date, and location." "Events must be bookable to the general public." And it has to happen somewhere you could stand.

On your websiteCounts?Why
A gig on a Friday night, £12 a ticketYesA public event, at a real place, on a date.
A wreath workshop with twelve placesYesAnyone can book it.
A free open dayYes"If the event is available without payment, fees, or service charges, set the price to 0."
A Christmas market across a weekendYes"If your event or ticket info is for an event that runs over several days, specify both the start and end dates of the event."
Your opening hours, 9 till 5, Monday to SaturdayNo"Don't mark business hours as events"
A weekend offer of 20% off wreathsNo"Don't add short-term discounts or purchase opportunities"
A members-only supper clubNo"Events that require a membership, or invitation prior to purchasing the ticket or attending the event are ineligible for the event experience."
A webinarNo"Virtual experiences that have no real-world component aren't supported."
Your weekly class timetableNot as one page"The event experience on Google only supports pages that focus on a single event."

A timetable is still worth having on your site, as a list people can narrow to the evening they're free. How to put a searchable, filterable list on your website covers that. It just isn't what this markup is for: "We recommend focusing on adding markup to your event posting pages instead of pages that list schedules or multiple events."

One page per event

This is the rule that decides how you build it: "Each event MUST have a unique URL (a leaf page) and markup on that URL." A leaf page is the end of the line, the page for one thing. So the wreath workshop on 5 December gets a page of its own, say /events/wreath-workshop-5-december, and your /events page lists it with a link.

If the same thing runs on several dates, each with its own tickets, Google wants each date separately: "If there are several different performances across different days, each with individual tickets, add a separate Event element for each performance."

That's a lot of pages for a quiz every Thursday, and Google's page has no special case for a weekly event. It may suit you better to put Quiz every Thursday, 8pm in plain words on your home page, and keep event pages for the one-offs: the Christmas quiz, the night the band plays.

The code itself

The markup is a block of JSON-LD in the head of the event's page, the same kind of block as the business and FAQ markup in SEO basics. It repeats, for a machine, what the page already says in words. Here's one for an invented workshop. On a real page every value should match what's written there:

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Event", "name": "Christmas wreath workshop", "startDate": "2026-12-05T10:00:00+00:00", "endDate": "2026-12-05T12:30:00+00:00", "eventStatus": "https://schema.org/EventScheduled", "location": { "@type": "Place", "name": "The Old Dairy", "address": { "@type": "PostalAddress", "streetAddress": "Station Road", "addressLocality": "Frome", "addressCountry": "GB" } }, "description": "Make your own wreath from fresh foliage in two and a half hours. All materials included; take it home on the day.", "image": [ "https://www.example.co.uk/images/wreath-workshop.jpg" ], "offers": { "@type": "Offer", "url": "https://www.example.co.uk/workshops/wreath-5-december", "price": 45, "priceCurrency": "GBP", "availability": "https://schema.org/InStock" }, "organizer": { "@type": "Organization", "name": "Hedge & Holly Flowers", "url": "https://www.example.co.uk" } } </script>
  • name is "The full title of the event." Not the venue: "DO NOT put the name of the event location." The venue goes in location, with "The venue's detailed street address."
  • startDate and endDate are the local time with the offset on the end: "Specify the timezone by including the UTC or GMT time offset." In the UK that's +00:00 in winter and +01:00 in summer. GOV.UK: "In the UK the clocks go forward 1 hour at 1am on the last Sunday in March, and back 1 hour at 2am on the last Sunday in October." For an all-day market, give the date with no time: "If the event is happening all day, don't specify a granular hour for the start date."
  • offers.price is "The lowest available price available for your tickets, including service charges and fees. Don't forget to update it as prices change or tickets sell out."
  • offers.url is where people book. Google wants a page that "clearly and predominantly provides the opportunity to buy a ticket offering admittance to that specific event to any user from the general public", so a payment link for that one date fits, and a general one for all your workshops doesn't. Selling places that way is in how to take payments without an online shop.
  • eventStatus can be left out while all is well: "If you don't use this field, Google understands the eventStatus to be EventScheduled." Putting it in from the start makes the change easier later.
  • image is optional, but Google recommends one: "We recommend that images are 1920px wide (the minimum width is 720px)." And "Images must represent the marked up content."

The block goes on the event's own page and nowhere else. Not the home page, and not the /events list.

When it's cancelled, moved or sold out

Change the page; don't take it down. Google's first rule on status is in capitals: "When the event status changes, DON'T remove the startDate."

  • Cancelled. "keep all values as the same as they were before the cancelation, and update the eventStatus to EventCancelled."
  • Postponed, no new date yet. EventPostponed, and "Keep the original date in the startDate of the event until you know when the event will take place."
  • Moved to a new date. "Once you know the new date information, change the eventStatus to EventRescheduled and update the startDate and endDate with the new date information." Adding the old date is optional: "Optionally, you can also mark the eventStatus field as rescheduled and add the previousStartDate."
  • Sold out. The availability changes: "SoldOut: Event tickets are sold out."

Google gives its reason for keeping the old details: "Properties like startDate and location help identify the unique event and make sure people understand the new status of the event." Say it on the page in words too, at the top, because people read the page and only Google reads the code.

Check it, then give it a few days

Google's checker is the Rich Results Test: "Validate your code using the Rich Results Test and fix any critical errors." Once your page is live, give it the address. We tried to put the example above through it on 26 October, and Google's tool wouldn't run for our automated browser, so we haven't claimed the example gets through. We checked it against the properties Google's page lists as required instead: the event's name, its start date, and a location with a name and an address. Run the test on your own page.

Then make sure Google can reach the page: "Be sure that your page is accessible to Google and not blocked by a robots.txt file, the noindex tag, or login requirements." A page left on noindex is invisible here too, and how to stop a page showing up in Google explains that tag. Allow time as well: "it may take several days after publishing a page for Google to find and crawl it". Search Console's URL Inspection tool can ask Google to look sooner; our guide to setting Search Console up shows where it is.

Even then, nothing is promised: "Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test." So put the page up weeks before the event, not days.

Where a beam site fits

A beam site is static HTML pages, so an event page and its markup are ordinary page content. Tell the AI you already use the details and it writes both. beam rebuilds the site's sitemap when a page is created, so the new event page is listed there without anyone touching it, and every new beam project starts with a robots.txt that lets crawlers in.

Each event is a page, so it counts towards your page allowance. By beam's own figures, a free account gets four pages, and Lone Creator gets thirty per site. Give pages to the events people will search for, and mention the rest on your events page in plain words.

Make a new page at /events/wreath-workshop-5-december for our Christmas wreath workshop: Saturday 5 December 2026, 10am to 12.30pm, at The Old Dairy, Station Road, Frome. £45 a place, all materials included, twelve places, booking through [our payment link for that date]. Write the page for people first: what it is, when, where, the price and the booking link, in that order. Then put Event structured data (JSON-LD) in its head with exactly the same details, a +00:00 time offset, eventStatus EventScheduled and availability InStock. Add the workshop to the list on /events with a link to the new page, but don't put Event markup on /events itself.

Give your next event its own page

Tell the AI you already use the date, the place and the price. It writes the page and the markup, and changes both if the date moves.

Connect your AI

Questions people ask

How do I get my event to show up on Google?

If it's on a ticket site, check whether that site takes part in Google's events listings first. Google says that if it does, "continue to post your events on the third-party website." If not, give the event its own page on your website, with Event structured data in it carrying at least the event's name, start date and location, all matching what the page says. Check it with Google's Rich Results Test, and allow several days.

My event is on Eventbrite. Do I need to do anything?

Eventbrite's UK help centre says "After publishing, it normally takes 2 to 3 days for your event to show in Google searches." That doesn't say which part of Google, so search for your event a few days after it goes up and see what comes back.

Can I put a weekly quiz night or class on Google's events list?

Google's page has no special case for a weekly event. Its rules are one page per event and, for repeats, "If there are several different performances across different days, each with individual tickets, add a separate Event element for each performance." So it's a page per date, which is a lot for a weekly quiz. Plain words on your home page may do the job better, with event pages kept for the one-offs.

Can an online event go on Google's events list?

Not on its own. Google: "Virtual experiences that have no real-world component aren't supported. Events must take place in a physical location."

What do I do if my event is cancelled?

Keep the page and change its status. Google: "keep all values as the same as they were before the cancelation, and update the eventStatus to EventCancelled." Say so at the top of the page in words as well, for the people who read it.

What time do I put for an event in the UK?

The local time, with the offset after it: +00:00 between the last Sunday in October and the last Sunday in March, and +01:00 while the clocks are forward. Google: "Specify the timezone by including the UTC or GMT time offset." For an all-day event, give the date and no time, because a time of midnight is one of the mistakes Google lists.

Does event markup help my website rank?

Google's page is about being eligible for the events listing, not about ranking, and even the listing isn't promised: "Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test."

Related reading