How to Add an Event Calendar to WordPress: Blocks and Views

To add an event calendar to WordPress, install an events plugin, publish your events, then place the plugin’s calendar block (or its shortcode) on a page. WordPress does not ship with one: posts and pages have no idea what a start time, a venue or an RSVP is. The work is closer to adding a contact form than to editing a theme, and a working calendar can be live in an afternoon.

This guide follows the order you will hit the decisions: what kind of calendar you need, the install, your first event, block or shortcode, which view to show, filtering, phones, recurring dates, RSVPs, subscribe feeds, big calendars, theme fit and a last check before you announce it. We use Eventonomy for the specifics, and say so wherever a detail belongs to it rather than to every plugin.

Do I need a plugin to add an event calendar to WordPress?

Yes. Before installing anything, get clear on three questions. Skipping this step is how sites end up migrating plugins six months in.

Are these single events or a recurring schedule? A monthly board meeting, a weekly class or a regular meetup needs a plugin that treats recurrence as a core feature. Some popular plugins put recurring events behind a paid add-on, which turns a five-minute setup into an unplanned purchase the first time you schedule a weekly session.

Do you need to know who is coming? If the event is informational, a calendar of dates is enough. If you need a headcount, guest numbers or a waitlist once a room fills, you need RSVPs or registration, not only a display of dates.

Will anyone besides you add events? A single-admin site can create events in wp-admin. A community, a meetup group with several organizers or a membership site usually needs frontend submission, so members can post their own listings without a backend login.

Write the answers down. They decide which plugin fits and save you from re-platforming later. If you are still narrowing it down, the WordPress event plugin overview covers what a complete plugin needs before you shortlist one, and the best WordPress calendar plugins comparison lines several up side by side.

One cost point belongs here, because it shapes the shortlist. Eventonomy is a plugin that runs on your own site, so there is no per-user fee, no per-ticket platform fee and no commission. The calendar, recurring events, RSVPs and the ICS feed described below all come with the free plugin.

How do I install an event calendar plugin?

From wp-admin, go to Plugins, then Add New, and search for the plugin by name. Click Install, then Activate. That is the whole installation for almost every WordPress plugin, and it takes under a minute.

After activation you will see an Events menu with submenus for events, settings and, depending on the plugin, venues and organizers. Eventonomy also creates the pages it needs on activation, including an Events page that already holds a search and filter bar, an events list and a month calendar. That means you can open /events/ straight away and see something real, then rearrange it later.

Before creating anything, open the settings screen and check:

• Your site’s timezone, under Settings > General. Event times inherit it, and a wrong timezone silently shifts every event you create.
• The default view visitors land on. A list is easier to scan on a phone; a month grid reads better on a desktop.
• Permalink structure for events, if the plugin lets you change it. /events/your-event-name/ is the readable default most plugins ship.

If your host runs WordPress with scheduled jobs switched off or starved, reminders and background tasks will lag. Eventonomy has a Setup and Health screen that warns you when scheduled jobs look stalled, which is worth a glance on day one.

How do I create my first event?

Open Events > Add New. The form looks like the standard WordPress editor with event fields added:

1. Title and description. The title shows in every calendar view, so keep it specific. “Monthly Book Club” reads better in a list than “Meeting.”
2. Start and end date and time. Check the timezone here too if the plugin lets you override it per event, which helps for a virtual event drawing people from several regions.
3. Venue. Save a venue once (name, address, map) and reuse it on every event held there instead of retyping the address.
4. Organizer. The same idea: save the organizer’s details once and attach them to as many events as needed.
5. Categories and tags, once you run more than a handful of events. A “Workshops” category lets visitors narrow the calendar instead of scrolling through everything.
6. Featured image. Grid and card layouts pull this in, so an event without one looks plainer next to the others.

Publish it the way you publish a post. It should appear on your calendar view straight away.

Should I use a calendar block or a shortcode?

Use the block if your site runs the block editor, and the shortcode if it does not. Both put the same calendar on the page, so the choice is about your editor, not about features.

In the block editor, click the plus button, search for Eventonomy and insert one of these:

• Calendar shows a month grid where each day cell lists that day’s events.
• Events List shows a grid, list or date-grouped agenda with a Load more button.
• Upcoming is a compact teaser of the next few events, meant for a home page or sidebar.
• Search and Filter adds the search box, category chips and date range, and it is also the block that draws the view switcher.

If you use the Classic Editor, or a page builder that does not offer WordPress blocks, the shortcode equivalents do the same job:

[eventonomy_calendar view="month"]
[eventonomy_events per_page="6" view="list" category="music"]
[eventonomy_search]

Placement matters more than the syntax. Put Search and Filter at the top, an Events List below it and the Calendar below that. That is the layout Eventonomy builds for you on activation. Without Search and Filter on the page, visitors have no way to flip between views, because the switcher lives in that block and not in the list. You can also drop a single block onto any other page, such as a landing page, when you want the calendar inside a layout rather than on its own page. The docs walk through the same steps in How to add an events calendar to any page.

Which calendar view should I show, and which are Pro?

Eventonomy ships four views in the free plugin. Each one is its own address, so a visitor can bookmark or share the view they like:

• Month (/events/month/) is the traditional grid. It is familiar at a glance but gets cramped when several events land on one day, so the plugin truncates a busy day with a “+N more” link. The default cut-off is three events per day, and you can change it in settings.
• List (/events/list/) is a compact row per event without images. It scans quickly, so it suits a busy calendar.
• Grid (/events/grid/) shows event cards with the cover image, date and venue, closer to a portfolio than a calendar.
• Upcoming (/events/upcoming/) groups events under headings such as Today, Tomorrow, This week and This weekend. It reads like a what’s-on page.

Week and Day hour-grid calendars are Pro. They suit a venue with many timed sessions in one day, and they appear as extra tabs in the view switcher once Pro is active. A map view is Pro too, and it is a block you place rather than a tab. Pro is from $99 a year, and nothing in this guide needs it.

There is no universally correct choice. A conference with dozens of concurrent sessions benefits from a month grid or, with Pro, a day grid. A meetup group posting one event every few weeks reads better as a simple upcoming list. Under Eventonomy, Settings, Appearance, you choose the default view and tick which views visitors can switch between. Turning a view off does not break its address: an old link lands on your default view instead of an error.

By default the archive shows only upcoming events. If you want past events visible, there is a setting for that, plus a field for how many days of history to include.

How do visitors filter the calendar by category?

Add the Search and Filter block above the calendar or list. It gives visitors a keyword box, one-tap category chips (an All chip, then one per category) and a From and To date range. The list below updates in place as they type, and every filter is reflected in the address bar, so a filtered view is a link someone can send to a friend.

Categories only help if they exist before people start using them. Create the handful of groupings your programme is actually organised by, such as Workshops, Talks and Socials, under Categories and Tags. Until at least one category exists, the category picker stays hidden in the event editor, so members who submit events cannot choose one. Keep the list short: a category list nobody can hold in their head stops being a filter and becomes a second search box.

Two more options are worth knowing. A category can have a colour and an icon, which colour the events on the calendar, and a category can have a parent, so filtering by Music also lists events in Jazz. If you want a page that always shows one slice, give the Events List block a category in its settings, or add category="music" to the shortcode.

Tags are different: members type them freely, and a new one appears the first time it is used. Use tags for loose detail such as “beginner” or “outdoor”, and categories for the buckets you would put in your site navigation.

How does the calendar behave on a phone?

A month grid is hard to read at phone width, so the calendar block does not force one. On a phone it shows a day-by-day agenda instead of the grid. Each day lists its first few events with a “+N more” link to that day’s list, using the same cut-off you set for the month view.

Even so, a list is often the safer default for mobile visitors, because it is the shortest path from opening the page to reading an event title. Switching to the List or Upcoming view as your default costs desktop visitors nothing, since they can still use the view switcher to reach the month grid.

The sidebar version, the Mini Calendar, is a small month with dots on days that have events. Tapping a day lists that day’s events underneath. It fits a 240 pixel column, so it works in a widget area. Whatever you choose, open the page on a real phone before you announce it. Our checklist at the end includes that step.

How do I set up recurring events?

Recurring events are where the setup step matters most, because this is the feature several competing plugins hold back for a paid tier. On the event form, find the Recurrence panel. In Eventonomy, the free editor gives you two controls:

• Repeats: None, Daily, Weekly or Monthly. A Yearly option appears too, but expanding a yearly rule needs Pro.
• Every: the interval. 1 means every time, 2 means every other.

That covers every day, every second week, every month and similar. Anything more specific is Pro: particular weekdays in one event, “the second Saturday of the month”, a fixed day of the month, an end-after count or end-on date, and skip dates.

Once saved, the plugin writes a real entry for each date up to a horizon (12 months ahead by default, adjustable from 1 to 60), and a daily background job keeps extending it. A weekly Tuesday class shows up on every Tuesday without you touching the admin again.

You can cancel a single date without touching the series. Open the event, find Upcoming dates under Date and Time, and press Cancel this date. A cancelled date leaves the calendar and the event page, and you can restore it later. What you cannot do is move one date to a new time or day. For that, cancel the date and create a one-off event. Editing a recurring event edits the whole series, so test a change on a spare event first. We cover the traps in why recurring events are where plugins break.

Can visitors RSVP from the calendar?

A calendar tells people when something is happening. RSVPs tell you who is actually coming. On each event you choose how people register: here on the site, on another site through a Register button, or not at all. When registration happens on your site, you can configure:

• Capacity, if the venue has a hard limit.
• A waitlist, so people can still join once capacity is full and are promoted when a spot opens.
• Custom questions, if you need more than a name and email, such as dietary needs.
• Guest counts, so one RSVP can cover a person and the people they bring.

Free RSVP waitlists promote the oldest person automatically when someone drops out. Paid ticket events work differently, as we explain on the RSVP page. Selling tickets is a separate step involving a payment gateway, tax handling and order records, and it is a Pro feature.

One setting changes who can register: Do attendees need an account. You can offer an account at registration, take guest sign-ups with no account at all, or require a login. Guests manage their RSVP through a link in their confirmation email.

Can visitors add events to their own calendar or subscribe?

Yes, and both are in the free plugin. An ICS file is the standard calendar format that Google Calendar, Outlook and Apple Calendar all read.

Each event page has an Add to calendar row with three choices: Google, Outlook, and an Apple or .ics download. That puts one event in a visitor’s calendar.

For a live subscription, the plugin publishes one site-wide feed at /wp-json/eventonomy/v1/calendar.ics. A visitor subscribes once, using a webcal:// address or, in Google Calendar, Other calendars, From URL, and new events appear as the app refreshes. The feed holds published, public events that still have an upcoming date, and cancelled dates are left out. Two limits are worth stating. There is no category-scoped or per-member feed, only the one for the whole site. And for very large sites the feed stops after 5,000 upcoming dates, nearest first.

A subscribed calendar app polls on its own schedule, so a change on your site can take a while to show up there. Tell people the website is the place that is always right. Turn the feature on under Settings, Connections, Calendar feed, then test it: add one event to your own calendar app and confirm the time, timezone and location arrived correctly. Do not confuse this with Pro calendar sync, which pulls events in from an ICS address or Eventbrite rather than publishing yours out.

Will an event calendar slow down my site?

A calendar view queries events the way a blog archive queries posts, so it carries a similar cost, and the main lever is how much you show at once. Eventonomy defaults to 10 events per page with a Load more button that appends the next batch without reloading, so a calendar with hundreds of events does not print them all on first load. The setting is Events per page, under Settings, Appearance, Event views. Grid view rounds the number up to fill rows of three, so a setting of 10 fetches 12.

Past events are hidden by default, which keeps the working set to what is coming. The month view caps each day at a few entries, and the feed caps at 5,000 dates. The recurrence horizon keeps long series from generating dates years ahead of time.

Some practical habits help on a large calendar:

• Keep Events per page modest and let visitors load more.
• Show the Upcoming view as your default rather than a year of month grids.
• Leave past events off unless you need an archive.
• Use compressed featured images, since grid cards load them.
• Make sure scheduled jobs run, so background work does not pile up.

We have not published a benchmark of events per second, so test your own site: seed a few hundred dummy events and watch how the archive behaves on your hosting before you rely on it.

How do I make the calendar match my theme?

Blocks inherit your theme’s fonts and colours, so there is no separate style panel to fight. The one thing Eventonomy keeps for itself is its accent colour, a green used on buttons, links and active states, so a Register button is never left unreadable by an unlucky theme.

If you want your brand colour instead, go to Settings, Appearance and find Brand colour. Choose Custom colour and pick one, or choose Match my theme so buttons and links follow your theme’s own accent. Eventonomy looks for the accent in BuddyX, then Reign, then the WordPress primary preset, and keeps its green if none is found. After choosing Match my theme, open an event and check the Register button is readable. Dark themes are detected automatically, so the calendar switches to its dark colours on a dark page.

For finer control, four CSS variables set the accent, its hover shade, the label colour and the active tint. The brand colours how-to lists them. If something still looks off, the styling and theme conflicts page covers the usual causes.

If community and events are both part of what you are building, look at how a calendar sits inside a broader setup rather than as a standalone page. The for communities and for meetups pages cover that context, and the free versus Pro breakdown shows exactly where a free calendar setup ends and paid ticketing begins.

What should I check before I announce the calendar?

Before linking the calendar from your homepage or sending it out, walk through these:

• Open the calendar on a phone. Confirm the day-by-day agenda reads well, and decide whether List should be your default view.
• Submit a test RSVP yourself, end to end, including the confirmation email.
• Check the timezone on a published event against what you intended. This is the most common setup mistake, and nobody notices until someone shows up at the wrong hour.
• Verify the recurring series past the first two or three dates, and cancel one date to see it leave the calendar.
• Filter by a category and check the address bar carries the filter.
• Confirm the ICS feed opens cleanly in at least one calendar app, and that Add to calendar sends the right time.
• Look at the venue and organizer pages, if the plugin generates them, to make sure the address and map render.
• Page through a long list and press Load more to confirm the next batch arrives.
• Check the Register button’s contrast against your theme.
• Turn on updates for the events plugin, or put a monthly check in the diary. Events plugins sit on public pages and take input from visitors, so a known flaw left unpatched is a real risk, as the The Events Calendar SQL injection showed.