Your events live on a Facebook Page. Five ways to bring the calendar home without losing the crowd

A small venue, a running club, a church hall, a volunteer group that hosts a quiz night every month. A lot of them have the same setup: the Facebook Page is the calendar. Every show gets a post, every ticket link sits in a comment, and the "Events" tab does the job a website was supposed to do.

That works until the platform changes the deal. Reports keep surfacing from Page managers that some Pages are now capped on how many posts with outside links they can publish unless they pay for a plan. For a venue that posts a ticket link for every show, that is not a minor tweak. It is the box office.

Across the communities we follow, the reaction splits in a familiar way. A venue owner said plainly that their whole calendar runs on a Page and they had never thought of it as rented. A Page manager warned others to check their own limits before the next busy month. Organisers who keep events on Instagram described the same trap from another angle: people see the flyer, then cannot find a date, a time or a link that still works a week later. A community organiser pointed out that a Facebook group cannot email its own members, so when the group went quiet, the people went with it. A tiny nonprofit just wanted a calendar on its own site that the volunteers could update without a developer.

Nobody in those conversations said "quit social media". What they wanted was simpler: the event should live somewhere you control, and social posts should point to it. Here are five ways people do that, from lightest to heaviest.

Option 1: A plain "What's on" page you update by hand

One page on your site, a list of upcoming dates, each with a short description and a ticket or RSVP link. Social posts link to this one page, not to each event.

Good for: a handful of events a month, one person in charge.
Watch out for: past events piling up at the top, and nobody updating it when the person in charge goes on holiday.

Option 2: A shared calendar embedded on your site

A shared online calendar that volunteers can edit, embedded on a page, with a public link people can subscribe to from their phone.

Good for: groups where several people add dates, and members who live in their own calendar app.
Watch out for: no tickets, no RSVP list, and the embed rarely looks like part of your site. It also does not collect anyone's email.

Option 3: An events plugin or module on your own site

Most CMSs have a proper events add-on: event pages with dates, venue, map, recurring series, a list and month view, and a subscribe link. On WordPress, The Events Calendar, Events Manager and Eventonomy all do this (Eventonomy is ours, so weigh that). Each event gets its own URL, so a single social post with one link still works when you hit a cap.

Good for: venues and clubs with a regular programme.
Watch out for: what is free and what needs a paid add-on, especially for tickets and recurring events. Check before you build around a feature.

Option 4: Owned calendar, ticketing on a dedicated service

Keep the calendar and event pages on your site, but send the "Buy tickets" button to a ticketing service you already trust. You keep the public listing and the search traffic; they handle the payment and the door scan.

Good for: venues that already have a ticketing contract or need assigned seating.
Watch out for: two places to update, fees on each ticket, and the buyer list sitting with someone else. Ask what you can export after each event.

Option 5: Everything on your own site, including tickets and the list

Event pages, RSVPs or paid tickets through your own payment account, a check-in list for the door, and a mailing list that grows with every booking.

Good for: organisers who want to email past attendees directly and stop depending on any one feed.
Watch out for: you now own the support questions, the refund emails and the person at the door with a phone. That is real work. Do not pick this because it sounds independent; pick it because you are ready to run it.

A checklist before you switch

• Count what you post. How many link posts does the Page make in a typical month? If you are near a cap, plan the change before your busiest season, not during it.
• Make one link do the work. Your bio, Page button and pinned post should all point to a single "What's on" URL that never changes.
• Collect contact details at every booking. An RSVP that only lives as a click on someone else's platform cannot be emailed later.
• Keep the social posts, change their job. Photos, recaps and reminders still belong on social. The post says "full programme on our site" instead of hosting the programme.
• Give past events a home. A short archive of past shows or meetups is proof the group is alive, and it is what new people check first.
• Name an owner. One person updates the calendar each week, and one backup knows how. Volunteer groups fail here more than anywhere else.
• Test the phone view. Most people tap through from a post on a phone. If the date and the button are not visible without scrolling, fix that first.
• Run both for a while. Keep posting on the Page while the site calendar beds in. Watch which link people actually use before you stop.

What usually goes wrong

The most common mistake we see is rebuilding the calendar and forgetting the list. The site looks great, but the only way to reach last season's crowd is still a feed you do not control. The second is over-building: a club that runs four events a year does not need ticketing, seat maps and check-in apps. Option 1 or 2 is fine, and moving up later is easy.

Your turn

1. If your events run from a social page, how many link posts do you actually make in a busy month?
2. Has anyone moved a venue or club calendar onto their own site and kept the same turnout? What made people follow you?
3. For volunteer-run groups: who updates the calendar, and what happens when that person steps away?
4. Which option above would you pick for a group that runs one event a month and has no budget, and why?