Choosing a WordPress Theme for a Church Website

Two people use a church website and they want opposite things. A stranger wants to know when the service starts, where to park, and what will happen to their children. A member wants last Sunday's sermon and the rota. Almost every church theme demo is designed for a third person who does not exist.

Judge candidates on those two jobs, and on who is going to keep the site running afterwards.

The information a visitor needs is embarrassingly small

Service times, address with parking, what to expect, and whether there is something for children. That is the entire first-visit decision, and it should be visible without scrolling and without a menu click, on a phone, on a Saturday night.

A large number of church themes put a rotating hero image where that information belongs. If the demo's homepage does not have a place for a plain block of times and address, you will be fighting it forever.

The sermon archive is the asset

Ten years of sermons is usually the most valuable thing a church has published. It also carries fields ordinary posts do not have: series, speaker, Bible passage, date preached, audio file, video embed, notes as a PDF, and sometimes a transcript.

That structure buys you real things — an archive browsable by series or by book, a speaker page, a podcast feed generated automatically, and "the sermon on Sunday" appearing on the homepage without anyone editing the homepage.

Get it from a sermon plugin, not from the theme. This matters more for churches than for most organisations because of who maintains the site: a volunteer, who will eventually hand over to another volunteer, who will want to redesign. If the theme registered the sermon post type, that redesign silently 404s a decade of teaching. If a plugin owns it, the redesign is just a redesign.

The same rule covers events, small groups and staff profiles. Content that matters belongs to a plugin; the theme styles it.

Recurring events are where generic themes fail

Church calendars are almost entirely recurring: a service every Sunday, a midweek group in term time, a monthly prayer meeting. What you need is the ability to edit a single occurrence — Christmas Day falls on a Sunday, the youth group skips half-term — without touching the series.

A basic events display in a theme will not do this. Choose the events layer deliberately; adding events to a WordPress calendar covers what the display side looks like once the data is right.

The editor is a volunteer with forty minutes

This is the constraint that should decide between two otherwise equal themes. Whoever updates the site is doing it between other commitments and will not read documentation.

• Editing must not require a page builder they have to learn. A block theme with a few prepared patterns — a service-times block, an announcement banner — is easier to hand over than a builder with a hundred widgets.
• Give people the narrowest role that works. The person who posts sermons does not need to install plugins; see WordPress user roles explained.
• Fewer settings is a feature. A theme with two hundred customiser options is a theme in which someone will eventually change something nobody can undo.

Accessibility is a congregational issue, not a checkbox

Church congregations skew older than most audiences. Small light-grey type on a white background, low-contrast buttons and tiny tap targets exclude the people most likely to be looking for the service time.

Prefer themes that declare accessibility support, then verify: real contrast, keyboard-reachable navigation, readable default type sizes, captions on sermon video. Accessibility plugins help with auditing but cannot rescue a theme built on pale grey text.

Two related habits: never autoplay music or video, and compress the photography, because image weight is what makes church sites slow.

Giving, and the things nobody warns you about

Handle giving through a dedicated donations plugin or a hosted giving platform. Recurring gifts, gift-aid style tax declarations and donor records are not theme territory, and a theme that offers a donation form is offering you a compliance problem.

Two more practical constraints, both specific to churches: photographs of children need consent before they go on a public site, so agree a policy before someone uploads the holiday club album — and safeguarding, leadership and complaints information should be findable in two clicks, not buried under "about".

Where to start

A free WordPress theme for church sites is not a compromise here, it is the sensible default. Install a maintained free block theme, add a sermon plugin and an events plugin, and build the service-times block first. If the site does that much well, it is already better than most church websites. The design can improve later; the archive underneath it should never have to move again.