How to Add an Event Calendar to WordPress

WordPress does not ship with an event calendar. Posts and pages cover articles and static content well, but neither one understands a start time, a venue, or an RSVP, so a calendar of any kind needs a plugin underneath it. The good news is that setting one up is closer to installing a contact form than customizing a theme: no code, no template editing, and the calendar is live within an afternoon.

This walkthrough covers the decisions that actually matter, in the order you will hit them: what kind of calendar you need, installing the plugin, creating your first event, choosing where the calendar lives on your site, handling events that repeat, letting people RSVP, giving visitors a way to save the date to their own calendar, and what to check before you tell anyone about it.

Decide what you actually need first

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 recurring meetup needs a plugin that treats recurrence as a core feature, not an afterthought. 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 try to schedule a weekly session.

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

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

Write the answers down. They decide which plugin fits and save you from re-platforming later. If you are still narrowing this down, the WordPress event plugin overview covers what a complete plugin actually needs to include before you shortlist one.

Install the plugin

From wp-admin, go to Plugins, then Add New, and search for an events plugin by name. Click Install, then Activate. That is the entire installation step for almost every WordPress plugin, events included, and it takes under a minute once you know which plugin you want.

After activation you will see a new admin menu item, usually called Events, with submenus for adding events, settings, and (depending on the plugin) venues and organizers. Before creating anything, open the settings screen and set:

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

Create your first event

Open Events > Add New. The form looks like a standard WordPress post editor with event-specific fields added:

1. Title and description. The title is what shows in every calendar view, so keep it specific: “Monthly Book Club” reads better in a list than “Meeting.”
2. Start date and time, end date and time. Get the timezone right here too if the plugin lets you override it per event, useful for a virtual event drawing attendees across regions.
3. Venue. Most plugins let you save a venue once (name, address, map) and reuse it across every event held there, rather than retyping the address each time.
4. Organizer. Same idea: save the organizer’s name and contact details once, attach them to as many events as needed.
5. Categories and tags, if you plan to run more than a handful of events. A “Workshops” category or a “Free” tag lets visitors filter the calendar instead of scrolling through everything.
6. Featured image. Calendar and list views usually pull this in as a thumbnail, so an event without one looks noticeably plainer next to the others.

Publish the event the same way you publish a post. It should now appear on whatever calendar view you configured.

Choose a view and place the calendar

Most event plugins support several ways to display the same underlying events:

• Month view looks like a traditional calendar grid, familiar at a glance but cramped once several events land on the same day.
• List view shows events as a scrollable, chronological list, generally the easiest to read on a phone.
• Grid view shows event cards with images, closer to a portfolio layout than a calendar.
• Upcoming view is a compact widget-sized list, useful in a sidebar or footer rather than as the main events page.

There is no universally correct choice. A conference with dozens of concurrent sessions benefits from a month grid; a meetup group posting one event every few weeks reads better as a simple upcoming list.

Placing the calendar is usually one of two routes. The plugin auto-generates an events archive page, commonly at /events/, which you can link to from your main navigation menu with no setup beyond that. Or, if you use the block editor, drop the calendar block onto any existing page, which is the route to take if you want the calendar embedded inside a landing page rather than living on its own.

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, look for a “Recurrence” or “Repeat” section. A properly built one lets you set:

• Frequency: daily, weekly, monthly, or yearly.
• Interval: every week versus every second week, for example.
• End condition: a fixed end date, a number of occurrences, or no end date at all for an ongoing weekly class.
• Exceptions: the ability to skip or reschedule a single occurrence (a holiday week, say) without breaking the rest of the series.

Once saved, the plugin generates the individual occurrences automatically, so a weekly Tuesday class shows up correctly on every Tuesday going forward without you touching the admin again. Confirm you can edit or cancel a single occurrence independently of the series before you rely on this for anything ongoing. Some plugins only let you edit or delete the whole series at once, which becomes a real limitation the first time one date needs to move.

Worth checking before you settle on a plugin: Eventonomy keeps recurring events in its free tier rather than gating them behind an upgrade, along with the RSVPs, calendar views and ICS feed covered in the rest of this guide. That is not true of every events plugin, so if a weekly or monthly series is central to what you are building, confirm it is actually free in whatever plugin you land on before you build a schedule around it.

Let people RSVP

A calendar tells people when something is happening. RSVPs tell you who is actually coming. On the event edit screen, enable RSVPs or registration if the plugin supports it, then configure:

• Capacity, if the venue has a hard limit.
• A waitlist, so people can still register once capacity is full and get notified if a spot opens up, rather than the event simply closing to registration.
• Custom questions, if you need more than a name and email, dietary restrictions or a t-shirt size, for example.
• Guest counts, so one RSVP can cover a person plus the people they are bringing.

RSVPs are the right tool for events that do not charge money. If you need to sell tickets instead, that is a separate step involving a payment gateway, tax handling and order records, which is a heavier setup than a free RSVP and usually lives in a paid tier of whatever plugin you chose.

Add the ICS feed so events land in people’s own calendars

An ICS feed is a standard calendar file format that Google Calendar, Outlook, and Apple Calendar all read. Publishing one means a visitor can click “Add to calendar” on a single event, or subscribe to your whole events feed once and have new events appear automatically without visiting your site again.

Look for an “Add to calendar” button on the single event page, and a feed URL in the plugin’s settings for the subscribe option. If both exist, test them yourself: add one event to your own calendar app and confirm the time, timezone and location arrived correctly before you trust it for other people’s calendars.

What to check before you announce it

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

• Open the calendar on a phone. Month grids in particular can compress badly on a small screen; a list view is often the safer default for mobile visitors.
• Submit a test RSVP yourself, end to end, including whatever confirmation email the plugin sends.
• Check the timezone on a published event against what you actually intended. This is the single most common setup mistake, and it is invisible until someone shows up at the wrong hour.
• Verify the recurring series generated correctly past the first two or three occurrences, not just the initial one.
• Confirm the ICS feed produces a file that opens cleanly in at least one calendar app.
• Look at the venue and organizer pages, if the plugin generates them, to make sure the address and map render as expected.

None of this takes long, but each one is the kind of gap that only surfaces once a real visitor hits it, which is a worse time to find out than now.

If community and events are both part of what you are building, it is worth looking at how a calendar sits inside a broader community or meetup setup rather than as a standalone page. The for communities and for meetups pages cover that context, and the free versus Pro breakdown lays out exactly where a free calendar setup like this one ends and paid ticketing begins.