Lorixen.
EN

An events page for your pub or venue that stays current

Short answer: Keep every event in one place, either an events plugin in your website or a shared calendar, and let the website read from it so nothing is typed twice. Set up regular nights (quiz, open mic, live music Saturdays) as recurring events, give one-off gigs their own page with a ticket link, and make sure past events disappear from the main list automatically. Then spend ten minutes a week checking the next fortnight.

The fastest way to lose a punter's trust is a "What's on" page still advertising Halloween in November. It happens because the page is a typed list someone updates when they remember. The fix isn't more discipline; it's a setup where the page keeps itself current.

Setup checklist

1. Choose one source of truth

Pick where events are entered, and enter them nowhere else.

  • An events plugin on your website. On WordPress, The Events Calendar is one example. Events become proper pages with dates, venue details and images, and the plugin builds list and month views from them.
  • A shared calendar embedded on the site. Google Calendar can be embedded on a web page: its help page explains that the calendar must be public for visitors to see it, the embed code is copied from Settings → Integrate calendar on a computer, and visitors can subscribe from the embedded calendar. It's quick and staff already know it, but each event doesn't get its own page.

For a pub that runs a quiz and occasional bands, an embedded calendar may be enough. For a venue selling tickets to named acts, individual event pages work better, for sharing and for search.

2. Make past events drop off

The plugin route handles this by design. The Events Calendar's documentation on past events explains that the main calendar focuses on current and upcoming events by default, with past events available at a separate list view if you want an archive. Note that the month view shows the whole current month, including days that have passed.

If your page is hand-built, ask your developer to filter by date so anything finished simply isn't shown.

3. Set up recurring nights properly

Your weekly quiz shouldn't be 52 separate entries typed by hand. The Events Calendar's guide to recurring events describes daily, weekly, monthly and yearly patterns in Events Calendar Pro, exceptions for weeks you skip, and editing one occurrence without changing the series. Two limits it mentions: one recurrence pattern per event (group more complex schedules into a series), and tickets aren't currently supported on recurring events. That second point matters if you charge entry to a regular night.

In Google Calendar, a repeating event does the same job.

4. Give each event what people need

Every listing, at minimum:

  • Date, start time and finish time (or "late")
  • Event name and a one-line description
  • Price, or "free entry"
  • Age or dress restrictions, if any
  • A ticket or booking link, if relevant
  • An image that works as a square crop

For ticketed events, link straight to that event's ticket page, not the ticket seller's homepage.

5. Design for phones first

Plenty of people check what's on from their phone, often on the way out. On a small screen:

  • Use a list view as the default; month grids are cramped on phones.
  • Put the date and time first on each item, large and clear.
  • Make the ticket button easy to tap.
  • Keep images light so the page loads quickly on mobile data.
  • Add a "this week" section at the top for people deciding tonight.

6. Help people save and share

  • An add to calendar option on each event helps people actually turn up.
  • Give each one-off event its own URL so it can be shared in group chats and on social media.
  • Share new events to the places your regulars already follow, such as your Facebook page, linking back to the event page so details stay in one place.

7. Add event structured data where it fits

For individual event pages, Google's event structured data guide asks for each event to have its own URL with markup on that page, and recommends marking up event pages rather than pages listing several events. Most events plugins can output this; check with Google's Rich Results Test.

Weekly upkeep routine (about ten minutes)

Pick a fixed slot, say Monday morning before opening.

  1. Check the next 14 days. Is everything listed? Are times right?
  2. Add any new bookings from the past week: bands, private hire you're happy to advertise, sports fixtures you're showing.
  3. Mark changes clearly. If an event is cancelled, mark it cancelled rather than deleting it straight away, so people who saved the link see what happened.
  4. Test one ticket link to make sure it still goes to the right page.
  5. Check the recurring nights. Skipped quiz because of a bank holiday? Add the exception.
  6. Share what's coming up this week, linking back to the events page.

Once a month, look at the next three months and fill in anything already confirmed. A full future calendar makes the venue look busy and gives people a reason to plan ahead.

FAQ

Is an embedded Google Calendar good enough?

For simple listings, yes. It's free and easy to update. Its limits are that events don't get their own pages, and styling options are basic.

Should we keep past events visible?

Not on the main list. A separate archive can be nice for venues with a strong gig history, but keep it one click away.

Who should be allowed to add events?

Give access to two or three staff, and keep a short written guide covering image size, how to write the description and where ticket links go.

Do we need a plugin to show recurring events?

No. A shared calendar handles repeating events well. A plugin adds individual event pages, structured data and more control over layout.

Once you know which events you run every week and which are one-offs, we can set up a what's on page that keeps itself up to date.

Sources

WhatsAppLet’s talk