Finding Your Church Online

The lobby that never closes

Someone searches your church's name on a Saturday night, deciding whether to visit tomorrow. They find a site with last year's service times, a broken "Give" link, and a browser security warning. They don't complain — they just don't come. That's the entire stakes of this lesson: your website is a first conversation that happens whether or not anyone's in the room to have it.

Most church sites don't fail from a lack of effort. They fail because "launch" got treated as something that requires being finished, so nothing ever ships — or because the site did launch, once, and then nobody touched it again.

Why sites stall or decay

Both failure modes come from the same root cause: no one person owns it. "The church" doesn't update a page; a named person does. Without a name attached, a site either never launches (because it's not anyone's job to finish it) or launches and then quietly rots (because it's not anyone's job to maintain it either).

Borrowed from software: the idea of a "minimum viable product" — ship the smallest useful version, then iterate. You can't improve something that doesn't exist yet, and a live, imperfect site helps more people than a perfect one that's still being built.

What good looks like — a 4-point minimum

True regardless of platform, budget, or who's building it. A visitor should be able to find, in under thirty seconds: a one-sentence answer to "what is this church" — not a mission-statement paragraph; the service time and address, unmissable, above the fold; a short "what to expect" note aimed at someone nervous about a first visit — parking, kids' programming, dress code; and one clear way to reach an actual human.

That's the whole checklist. Everything else — a sermon archive, a giving page, a staff directory — is worth having eventually, but none of it matters if the four basics aren't there.

The maintenance habits that matter more than the platform

A recurring 15-minute review, once a month, anchored to something that already happens (a staff meeting, a board call) so it actually gets done. Test your own site specifically on a phone, since that's most of your traffic. Personally test your own donate flow the way a stranger would — a broken giving link that sits unnoticed for two months is a real, ongoing cost, not a minor bug. And a named owner, even one who only touches the site monthly, beats no owner at all.

Three real approaches, by budget

Free / DIY. A single well-built page on a general-purpose free builder — Google Sites, Carrd, or a free tier of a mainstream builder. Near-zero cost. Upkeep is entirely manual and lands on whoever owns it.

Low-cost templated. A paid template builder — Squarespace, Wix, GoDaddy — typically in the range of an ordinary monthly software bill. These do include event listings and donation blocks; what they don't include is a full church-management system behind the site — a member directory, check-in, group messaging. If you only need a website, that's not a gap. If you'll want those other pieces too, it's worth knowing before you build.

Bundled church platform. A website module folded into a broader church-management tool — Breeze, Tithe.ly, Subsplash, and Faith Software's own myChelper all take this approach. Worth it only if you actually want the other modules too; run the total-cost-of-ownership filter before assuming "bundled" is automatically cheaper than it looks.

Your exercise

Open your homepage on your phone right now. Time yourself: can a stranger find service time, address, and a way to contact a person in under thirty seconds? If not, that's the fix that matters most this week — before anything else on this list.

If you have a site already, send the link to one honest friend outside the church and ask them to narrate their first impression out loud. It's more instructive than any internal committee meeting about branding.