Build a Church Website That Answers the Five Questions

Saturday night, deciding about tomorrow

Someone is thinking about visiting your church tomorrow. It's late, they're on their phone, and they have about thirty seconds of patience. What they're really asking is not "what is your doctrinal statement" — it's "will I feel stupid walking in?"

The Foundations module on finding your church online argued for a four-point minimum and a named owner. This module is the build itself: what to put on the page, in what order, and how to get it published this week rather than next quarter.

The five questions, in priority order

Where and when. Address and service times, above the fold, unmissable. If a visitor has to hunt, you have already lost some of them. Include the parking situation if it's not obvious — a surprising number of people skip a first visit over uncertainty about where to leave the car.

What is this church, in one sentence. Not a mission statement paragraph. One sentence a stranger could repeat to a friend.

What actually happens when I walk in. How long is the service, what do people wear, is there anything for my kids, will anyone make me stand up and introduce myself. Answering the last one honestly does more good than any photograph.

Who are you. A couple of real photos of actual people in your actual building beats stock photography every time. A visitor is trying to picture themselves in the room.

What do I do next. One clear action — come Sunday, email a person, plan a visit. One. Not six.

Write it like you'd say it

The most common church-website writing problem is not bad grammar; it's insider language. "Join us for worship as we gather in fellowship" tells a newcomer nothing. "We meet Sundays at 10am. It lasts about an hour" tells them everything.

A test that works: read a sentence aloud. If you would not say it to someone in a coffee shop, don't publish it. Cut adjectives before you cut facts.

Write the page for one specific person you can picture — a neighbour, a young family new to the area — rather than for everyone at once. Copy written for everyone reaches no one.

Ship it before it's finished

The failure mode here is not a bad website. It's the website that never launches because it isn't perfect yet. A live page with correct service times helps more people than a beautiful draft nobody can see.

Practical order of work: start from a template rather than a blank page, replace the placeholder text with your real details, delete every section you don't have real content for, and publish. Empty sections labelled "Coming soon" are worse than no section at all — to a visitor they signal a church that has lost interest in its own website.

Then put a fifteen-minute review on the calendar, monthly, attached to something that already happens. That habit, not the initial build, is what keeps the site honest.

Three real approaches, by budget

Free / DIY. A single well-built page — Google Sites, Carrd, a free builder tier. Costs nothing, does the job for a small church, and every update is manual.

Low-cost templated. Squarespace, Wix, GoDaddy. Real design control and a monthly bill in the range of an ordinary software subscription. Good if a website is genuinely all you need.

Bundled church platform. A website module inside a broader church-management tool — Breeze, Tithe.ly, Subsplash, and Faith Software's own myChelper all work this way, typically with starter templates and a drag-and-drop block editor, hosted on a subdomain with the option to connect a domain you already own. Worth it if you want the surrounding modules too; run the total-cost filter from the Foundations track before assuming bundled is automatically cheaper.

Your exercise

Write the five answers as five plain sentences, in a notes app, before you open any builder. Most churches discover here that they don't actually agree on the one-sentence answer — better to find that out now than halfway through building a page.

Then set a deadline this week to publish something with correct service times, however plain. Send it to one person outside the church and ask them to narrate their first impression out loud. That single piece of feedback is worth more than a month of internal discussion about fonts.