# Event Structured Data For Town Centre Events: A Plain-English Guide

URL: https://www.starien.com/blog/event-structured-data-for-town-centre-events
Published: 2026-10-10
Author: Geoffrey Moffett
Topics: business improvement districts, AEO, structured data, events, town centres

> A plain-English guide for BIDs to event structured data: what it is, why it helps search engines and AI assistants find your events, an example, and how to test it.

## Quick answer

Event structured data is a small block of code on an event page that tells search engines and AI tools exactly what the event is, when and where it happens, and how to attend. For BIDs, adding it to every town centre event page makes your events easier for machines to read accurately, which supports visibility in search and AI answers.

## Key takeaways

- Structured data labels the key facts of an event so machines don't have to guess.
- Every event needs its own page before structured data can help.
- The essentials are name, start date and time, location, description and status.
- Test every page and update the data when events change or are cancelled.

Your Christmas lights switch-on is the biggest night of the year. The poster is gorgeous, the social posts are flying, and someone asks an AI assistant "what's on in town this weekend?" Nothing. Or worse, last year's date. Event structured data is one of the simplest technical fixes that helps prevent this, and it's far less scary than it sounds.

## What Event Structured Data Actually Is

Search engines and AI tools read web pages, but they're not always sure which bit is the date, which is the venue and which is just a sentence about mince pies. Structured data is a small, invisible block of code on the page that labels these facts clearly.

It uses a shared vocabulary called Schema.org, which the major search engines support. For events, there's a type simply called Event, with properties like name, start date, location and price.

The most common format is JSON-LD, a tidy block of code that sits in the page and doesn't change how it looks to visitors.

## Why Event Structured Data Matters For Towns

Town centre events are exactly the kind of thing people search for and ask AI about. "What's on in [town] this weekend?" "When is the farmers' market?" "Is the Easter trail free?"

Structured data helps by:

- making key facts unambiguous for search engines;
- making your events eligible for event features in search where they're offered;
- giving AI tools reliable facts to draw on;
- reducing mix-ups between this year's event and last year's.

It's not magic. It works alongside a clear, well-written event page.

## Before You Start: One Event, One Page

Structured data needs a home. If all your events live on a single "What's On" page as a long list, start by giving each event its own page with:

- the event name;
- date and start and end times;
- the location, with full address;
- a description of what happens;
- price, or "free";
- how to book, if needed;
- accessibility information.

Your "What's On" page then becomes a list linking to each one.

## A Simple Example

Here's a simplified example for a free Christmas market. Your developer or website platform would place something like this in the page.

```json
{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "Town Square Christmas Market",
  "startDate": "2026-12-12T10:00:00+00:00",
  "endDate": "2026-12-12T17:00:00+00:00",
  "eventStatus": "https://schema.org/EventScheduled",
  "eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
  "location": {
    "@type": "Place",
    "name": "Town Square",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "Town Square",
      "addressLocality": "Your Town",
      "postalCode": "AB1 2CD",
      "addressCountry": "GB"
    }
  },
  "description": "Local makers, food stalls and festive music in the town square.",
  "isAccessibleForFree": true,
  "organizer": {
    "@type": "Organization",
    "name": "Your Town BID",
    "url": "https://www.example.com"
  }
}
```

### The Fields That Matter Most

- **name:** the event's actual name, not "Event 4".
- **startDate and endDate:** full dates and times, with the time zone offset. Remember British Summer Time.
- **location:** a named place with a full address.
- **description:** a sentence or two in plain English.
- **eventStatus:** scheduled, postponed, cancelled or rescheduled.

### Useful Extras

- **offers:** price, currency and booking link for ticketed events.
- **image:** a good photo of the event or venue.
- **organizer:** the BID or the business running it.

## Step By Step For BIDs

### Step 1: Check What You Have

Many website platforms and event plugins already output event structured data. Test an existing event page before doing anything else.

### Step 2: Fix The Template, Not Each Page

If your site doesn't add it, ask your developer to build it into the event template, so every new event gets it automatically from the fields you fill in.

### Step 3: Test

Use Google's Rich Results Test or the Schema.org validator. Paste in the page address, check for errors and warnings, fix and test again.

### Step 4: Keep It Updated

If an event is cancelled because of weather, update the page and set the status to cancelled. Don't just delete the page; people may still be looking for it.

### Step 5: Tidy Past Events

Mark past events clearly or move them to an archive. Old events that look current confuse visitors and machines alike.

## Don't Forget Your Levy Payers' Events

Many town centre events are run by businesses: a bookshop author night, a café's live music, a gallery opening. Encourage them to list these on your town website too, using the same template. It's a lovely member benefit, and it makes your town look as lively as it really is.

## Pitfalls To Avoid

- **Mismatched information.** The structured data must match what's visible on the page.
- **Wrong time zones.** A one-hour error is a classic during the clocks changing.
- **Recurring events as one page.** A weekly market needs clear dates; follow your platform's approach to recurring events.
- **Set and forget.** Changes to times or venues need updating in both places.

## A Quick Checklist

- Each event has its own page.
- Structured data added through the template.
- Tested with no errors.
- Cancelled events marked, not deleted.
- Past events archived.

Event data is one part of a wider approach to [AEO for town centres](/blog/aeo-for-town-centres-get-your-town-recommended-by-ai/), and it pairs nicely with good event promotion. Our [AEO Scanner](/aeo-scanner/) will help you spot gaps on your own site.

## How Starien Can Help

We build and improve town websites for BIDs, including event templates with structured data built in, as part of Digital For BIDs. If you'd like your events to be easier to find for people and machines alike, [get in touch](/contact/).

## Frequently asked questions

### What is event structured data?

It's code, usually in a format called JSON-LD, that uses the shared Schema.org vocabulary to describe an event's name, dates, location, price and organiser in a way search engines and other tools can read reliably.

### Does structured data guarantee our events appear in Google?

No. It helps search engines understand your events and makes them eligible for some enhanced displays, but it doesn't guarantee placement. Clear, accurate event pages matter just as much.

### Do we need a developer to add event structured data?

Not always. Many website platforms and event plugins add it automatically or let you fill in fields. If your site doesn't, a developer can usually set up a template so it's added to every event page.

### How do we test our event structured data?

Use Google's Rich Results Test or the Schema.org validator. Paste in the page address and check for errors or missing fields, then fix and test again.
