Church Website Design Your Volunteers Can Keep Up With

A visitor lands on your church’s homepage at 9:40 on a Saturday night. They are deciding whether to bring their kids tomorrow. They want three things: what time, where to park, and what happens with the kids. If those take more than one tap to find, a lot of them just stay home.

Most church website design starts somewhere else. It starts with the mission statement, a welcome video from the pastor, and a slider of photos from last summer’s picnic. None of that is wrong. It just isn’t what the Saturday-night visitor came for.

This post is for the people who will keep the site running after launch: the office manager, the volunteer who “knows computers,” the board member holding the budget. We’ll go through giving, sermons, events, accessibility and money. You’ll get real platform names and the fees those platforms publish, so you can make choices you can live with a year from now.

What visitors look for first (it isn’t your mission statement)

A first-time guest is making a small, slightly nervous decision. Every extra click is a chance for them to talk themselves out of it. So the top of your homepage should answer the plain questions: service times, the address with a map link, parking, what to wear, and what the kids will do.

Your regulars want different things. They come for the giving button, last week’s sermon, and the calendar. A good homepage serves both groups without making either one hunt: a clear “Plan your visit” path for guests, and three obvious buttons for members.

Riverwood, the church I attend in Waverly, is a good example of the split. Newcomers get a “Plan your visit” page. The giving button, the sermon series and the events page sit right in the main menu for the people who show up every week. We rebuilt that site after the old one had become a chore for its volunteers. The story of how the Riverwood site came together covers what changed for the people running it.

The mission statement still belongs on the site. Put it on the About page, where people who care about it will read it.

Online giving: picking a platform and knowing what it costs

Giving is the one feature where a bad setup costs real money every week. Two things decide most of it. The first is what the platform takes from each gift. The second is how easy it is to set up a gift that repeats on its own.

When we build a church site, our first recommendation for giving is GiveWP. It’s a donation plugin, meaning an add-on that runs inside your own WordPress site instead of on another company’s platform. The giving form sits on your church’s page, and every gift and giver record is stored in your site too.

That last part is why it’s our pick. It’s the difference between owning your building and renting space in someone else’s. If you change web hosts later, your giving history moves with you.

GiveWP keeps one profile per giver showing every gift they’ve made. Staff can add notes and tags, so the office can see who gives and send a thank-you without logging into another company’s dashboard.

It covers the day-to-day needs too. Donors can choose a weekly, monthly, quarterly or yearly gift, then update their card or pause it themselves without calling the office. Tax receipts go out by email automatically. Givers can use Apple Pay or Google Pay on a phone, and you can offer them the option to cover the processing fee.

Two costs to plan for. Recurring giving is part of GiveWP’s paid plans, so the license belongs in the budget. And the per-gift card fee comes from the payment company you connect (Stripe, PayPal or Square), so check that company’s published rate.

Hosted giving platforms are the main alternative. These are the rates three common ones publish on their pricing pages (checked October 2026):

Run the numbers on a $100 gift. On a card, that’s $3.20 with Tithely or Givelify and $2.45 with Planning Center. From a bank account it’s $1.30 with Tithely and 30 cents with Planning Center. On a church budget that runs mostly on regular weekly gifts, nudging people toward bank transfers matters more than which logo is on the form.

There is a fair argument for these platforms. A small church with modest online giving may do fine on a free plan, and Tithely’s free tier includes recurring gifts and year-end tax statements. Planning Center makes sense when you already use its other tools for people, check-in or the calendar, because giving then lives with the rest of your records.

Riverwood went the Planning Center route. Its giving button opens a Planning Center giving form in a pop-up right on the church site. The trade-off with any hosted platform is that your giver records live on their system, under their terms. Leaving later means counting on their export to bring your history along.

Whichever you choose, set it up so recurring giving is offered on the first screen of the form, where people see it before they type a card number. Turn on the option that lets donors cover the processing fee. And keep the form on your own site so givers never wonder whether they’ve left the church’s page. GiveWP does that by default, and some hosted platforms allow it. We cover more of the setup side on our page about websites and donation tools for nonprofits.

Sermons: audio, video, and the archive nobody uses

Most people who click on sermons want one thing: the one they missed. The recent message should be one tap from the homepage. The deep archive matters far less to your members than to search engines and the occasional visitor checking what your church teaches.

That changes how much effort the archive deserves. You don’t need a custom sermon library with filters for speaker, book, topic and date. Group messages by series and list the Bible passage on each one. That covers nearly every real search.

For the files themselves, don’t upload video to your website. Video files are huge, and your web host is not built to stream them. Stream and store video on YouTube, where it’s free. Put audio on a podcast host so the same recording shows up in Apple Podcasts and Spotify without anyone uploading it twice. Then each sermon page on your site embeds both players and adds a short summary.

That’s how Riverwood runs it. Services stream on YouTube, each sermon has its own page inside its series, and the audio plays from a Transistor podcast player embedded on that page. The weekly job comes down to pasting two links and writing a short summary, which one person can learn in a single sitting.

Events and calendars a volunteer can keep current

An out-of-date calendar does more damage than no calendar. When a visitor sees an Easter breakfast listed in October, they assume the rest of the site is stale too, service times included.

The fix is to have one calendar and one person responsible for it. If your church manages events somewhere else, show that calendar on the website instead of retyping events into a second system. Planning Center’s Calendar is free for unlimited events, per its pricing page, and Tithely’s All-Access plan includes a calendar. Google Calendar embeds are free too and most volunteers already know how to use one.

Keep each event short: the date, the time, where, who it’s for, and how to sign up. If an event needs registration, use a single sign-up form instead of “email Pam.” Pam will appreciate it.

Then put a recurring reminder on someone’s phone for the first Monday of every month: delete past events and check the next eight weeks. You can browse sites we’ve built for small organizations to see how a simple events page looks in practice.

Accessibility is about your own people

Start with the legal side, because it gets blurred a lot. The ADA’s public accommodation rules, Title III, exempt religious organizations, including places of worship. ADA.gov states it plainly. A church is not in the same lawsuit position as a restaurant or a retail store. (State and local laws can still apply, so check yours.)

That doesn’t make accessibility optional in any sense that matters to a congregation. The older member reading your site on a phone with the text zoomed in is your people. So is the deaf teenager trying to follow a sermon video, or the visitor who uses a screen reader to find your service times.

The fixes that help them most are small and cheap:

• Captions on sermon videos. YouTube creates them automatically; someone should skim and correct names and Bible books, which it often gets wrong.
• Text you can read: dark text on a light background, and a body font size that doesn’t need zooming.
• Service times and announcements as plain text on a page. A PDF bulletin is fine as a download, but it shouldn’t be the only place that information lives.
• Photos with a short description attached (alt text), so a screen reader can say what the picture shows.
• Buttons big enough to tap with a thumb.

We publish where our own site stands in our accessibility statement, including what still needs work. A church can do the same in one paragraph on its contact page.

Who updates this in six months?

This is the question I’d ask before any other. The church sites that go stale usually go stale for one reason: the volunteer who built them moved to Cedar Rapids and nobody else knows the password.

Volunteer turnover is like staff turnover in a small business, except nobody gives two weeks’ notice. Plan for it the same way. Before launch, write a one-page handoff sheet. It should say where the site is hosted, who owns the web address, and which accounts run giving, the podcast and YouTube. Then list the weekly tasks with a sentence on how to do each.

A few rules save churches a lot of grief:

• Every account belongs to a church email address, never a volunteer’s personal Gmail.
• At least two people have admin access to each system, and they each have their own login.
• The web address renews automatically on a church card, with the renewal email going to the office.
• Weekly updates are limited to tasks someone can learn in one sitting: sermon page, calendar, homepage announcement.

The design should make that last one easy. Ask for the weekly pieces, like a sermon or an event, to be set up as fill-in-the-blank entries with their own fields. The parts that rarely change, like the header and the page structure, should sit where a well-meaning volunteer can’t break them by accident.

A realistic budget for a church site

A church website budget has three parts, and most boards only plan for the first one.

The first is the build. A small church can get a lot from a template, and I’ll say that plainly. Say your congregation is small and the site’s job is to show service times, take gifts and host sermons. Tithely’s All-Access plan bundles a website, app and calendar with giving for $119 a month at its listed price, and that can be the right call. A custom site earns its cost when it has to work with tools you already use. It also makes sense when several ministries need their own pages, or when a template keeps fighting how your church operates. Our breakdown of what websites cost at each price tier in the Midwest walks through what each level buys.

The second is the running cost: hosting, the web address renewal, and any paid plugins, including a GiveWP license if you take our advice on giving. If you use a hosted giving platform with a monthly plan, add that too. Put these on the annual budget as their own line item so nobody is surprised in March.

The third is time, and it’s the one churches undercount. Someone has to spend part of every week on sermons, events and announcements. If no one has that time, budget for a support plan, or choose a simpler site that needs less of it.

On timing, a small site usually takes us about a month, as long as content and decisions come back on schedule. The slow part tends to be waiting on photos, staff bios and a final answer on which giving platform to use.

Where to start

Pick one thing from this list to fix this month. Usually that’s the Saturday-night visitor’s path, or getting every account onto a church email address. If you’d rather talk through the whole picture, book a church website consultation with us. We meet people in Waterloo and Cedar Falls, and you’re welcome to walk into our Waverly office. We’ll start with how your volunteers work now and what they can keep up with.