A church website has two audiences at the same time. A first-time visitor wants to know when you meet, where to park and what to expect. An existing member wants sermons, events, ministries, giving and contact details without digging through a complicated menu. Build those jobs first, then add extras only when someone will maintain them.
TL;DR
Build a church website with WordPress around four practical jobs: help newcomers plan a visit, keep events current, make sermons easy to find, and provide a secure giving path. Use The Events Calendar for events, GiveWP for donations, and Seriously Simple Podcasting when sermon audio needs its own searchable archive and feed. Launch only after service times, directions, giving, events and a mobile sermon page all work end to end.
Start with the visitor journey
Before installing plugins, write the path for someone who has never attended. They should be able to answer five questions quickly: What kind of church is this? When are services? Where is it? What should I expect? How do I contact someone? Put service times, location and a clear Plan Your Visit path above the fold or close to it.
Member features come next. Sermons, ministries, groups, events and giving matter, but they should not bury the first-visit information.
Essential plugin stack
| Job | Plugin | Why |
|---|---|---|
| Events and service calendar | The Events Calendar | Structured upcoming events and recurring church activities. |
| Online giving | GiveWP | Donation forms, donor flow and giving records. |
| Sermon audio / podcast feed | Seriously Simple Podcasting | Structured sermon episodes and podcast distribution when audio is central. |
Build the church website step by step
Step 01: Create the minimum public pages
Create Home, Plan Your Visit, About/Beliefs, Ministries, Sermons, Events, Give and Contact. Do not create separate pages for every internal committee before the core navigation works.
Check: A visitor can find service time, address and contact information in two clicks or fewer.
Step 02: Make Plan Your Visit genuinely useful
Include service length, parking, entrance, accessibility information, children’s check-in, what people usually wear if that question comes up, and a contact path. Keep sensitive safeguarding details out of public operational pages while still explaining the public process clearly.
Check: Ask someone unfamiliar with the church to explain where they would go on Sunday using only the page.
Step 03: Add ministries with an owner
Create ministry pages only for active ministries. Each should have a short purpose, schedule, audience, contact person or shared contact route, and how to participate. Avoid publishing personal phone numbers unless the church intentionally uses them publicly.
Check: Every ministry page has a named content owner responsible for schedule changes.
Step 04: Configure the events calendar
There are several event tools in our WordPress event calendar roundup. For this guide, use The Events Calendar for services, groups, classes and special events. Add location, start/end time, organizer details and registration link where needed.
Check: An event changed in WordPress is correct on both the event page and calendar view.
Step 05: Build a sermon archive that can grow
If sermon audio is a core part of the site, use Seriously Simple Podcasting rather than uploading random MP3 links into blog posts. Keep a consistent title, speaker, date, series, Scripture/topic and media source. For video, embedding from a dedicated video host is usually easier on WordPress performance than serving large video files from ordinary web hosting.
Check: A visitor can find last week’s sermon and play it on mobile without downloading a raw file first.
Step 06: Set up giving as a separate trusted flow
Our WordPress donation plugins roundup covers the category. For this guide, use GiveWP. Create only the funds the church actually uses, explain whether gifts are one-time or recurring, and keep financial language consistent with the church’s policies.
Check: Complete a test donation using the configured test/sandbox process and confirm the donor confirmation and admin record are correct.
Step 07: Decide what stays public and what stays private
Do not turn the public website into a member database by accident. Attendance, pastoral-care notes, children’s information, prayer requests marked private, and internal rosters need stronger access rules than public ministry pages.
Check: Review the site logged out and confirm no private member information is reachable through direct URLs or search.
Step 08: Make updates easy for volunteers and staff
Assign ownership for events, sermons, ministry pages and giving notices. Use simple editorial rules: update an event once, archive obsolete notices, and remove staff/ministry details when they change.
Check: A nontechnical editor can publish an event and sermon without changing templates or layout code.
Step 09: Test the Sunday mobile experience
On a phone, test directions, service times, children’s information, the latest event, latest sermon and giving form. Slow galleries or oversized video embeds should not block those tasks.
Check: The main Sunday tasks work without zooming, horizontal scrolling or opening desktop-only controls.
Step 10: Run a newcomer-to-member test
Start as a first-time visitor, plan a visit, find a ministry, open an event, play a sermon, submit a contact request and reach the giving page. Then repeat as a returning member looking for this week’s information.
Check: Both journeys work without relying on insider knowledge of church terminology.
Keep the site current or keep it small
An outdated church calendar is worse than a smaller accurate one. The same is true for staff lists, service times and ministries. If nobody owns a section, remove or simplify it. Make seasonal pages expire intentionally instead of letting Easter, Christmas or conference information sit live for years.
Giving and pastoral care need different trust boundaries
Payment records belong in the donation system. Pastoral conversations and sensitive prayer requests should not be stored casually in public form entries. Decide who can access each type of information and how long it is retained.
Plan livestreams and urgent updates separately
If the church streams services, embed from a dedicated video platform rather than making ordinary WordPress hosting carry the live stream. Keep service times and directions visible even if the stream fails. For weather closures, venue changes or emergency notices, assign one person who can publish a short site-wide update quickly and remove it when the situation ends.
Holiday services also need one authoritative schedule. Christmas, Easter, conferences and special services often create temporary times that conflict with the normal weekly pattern. Update the source schedule first, then the homepage and announcements from that confirmed information.
Conclusion
A useful church website is not the one with the most ministry features. It is the one a newcomer can understand and the congregation can trust to stay current. Build the visitor path first, then add events, sermons and giving with clear ownership.
FAQs
What pages does a church website need first?
Start with Home, Plan Your Visit, About/Beliefs, Sermons, Events, Give and Contact. Add ministry-specific pages only when there is real content to maintain.
Should a church host sermon video directly in WordPress?
Usually it is cleaner to embed video from a dedicated video platform and use WordPress for the sermon page, metadata and discovery.
Can WordPress accept church donations?
Yes. Donation plugins such as GiveWP can provide dedicated giving forms and donor records.
Do I need a church management system inside WordPress?
Not necessarily. A public church website can stay focused on visitors, events, sermons and giving while private member operations remain in a separate system.
How often should church website content be reviewed?
Review service times and contact details whenever they change, events weekly during active seasons, and ministry/staff pages on a scheduled recurring basis.
