Something isn’t working. The usual response is to blame the design, swap a template, or hire someone to “fix it.” But the real problem often sits deeper than colour choices or fonts. The website was built for people who already belong. It was never built for people who don’t.

Think about what a typical church homepage tells you. It names the pastor. It lists committee meetings. It links to last Sunday’s bulletin. Every one of these items assumes the reader already understands what a bulletin is, who the pastor is, and why any of it matters.

For your congregation, that assumption works fine. They already know the service starts at 10:30. They already know where the nursery is. They already know Pastor Dave from Rotary or the grocery store. The website simply confirms what they know, like a family group chat confirms plans everyone already agreed to at dinner.

Consequently, the site becomes an internal memo dressed up as a public page. It reassures the people who are already coming. Meanwhile, it quietly fails the one person it should be working hardest for: someone who has never walked through your doors.

Picture a woman scrolling on her phone on a Tuesday night. Her marriage just ended, or her father just passed, or she simply woke up wondering if there’s more to life than her current routine. She searches “church near me” and lands on your site.

She doesn’t know your denomination’s shorthand. She doesn’t recognize the pastor’s name. She has no idea what “Fellowship Hall” means, or why there’s a photo of a chili cook-off on your homepage. Instead, she needs three things, quickly: Is this a safe place? What happens if I show up? What do I wear?

If your site can’t answer those questions within seconds, she’ll close the tab. Not because your church lacks warmth. Rather, because your website was never designed with her in mind. It was designed for people who already have the context she’s missing.

This gap forms honestly, not carelessly. Churches build websites the same way they build everything else: through committees. A volunteer with some tech skill puts pages together. Staff and elders review the drafts. Naturally, they write for the audience in the room, because that’s the audience they picture.

Additionally, most churches measure success by attendance, not by outside visibility. If Sunday numbers hold steady, the website rarely comes up for discussion. Only when growth stalls, or a younger family mentions they “couldn’t find much online,” does anyone question whether the site is doing its job.

By then, the site has years of internal language baked into it. Changing it feels like starting over, so most churches patch a photo here or a sermon link there, instead of asking the harder question: who is this actually for?

A website built only for current members carries a quiet cost. It signals, unintentionally, that outsiders are welcome once they arrive, but not particularly considered beforehand. That’s rarely the church’s heart. Still, it’s what the site communicates by omission.

Meanwhile, every week someone searches for a church nearby, reads two or three homepages, and picks the one that answers their questions fastest. Often, that isn’t the church with the deepest theology or the warmest greeters. It’s the church whose website made a stranger feel expected.

Over time, this pattern shapes who walks through the door. Congregations that write only for themselves tend to keep attracting people who already look and think like themselves. Newcomers, especially younger ones or people outside the existing social web, quietly drift toward whichever church made the first move easy.

Shifting the website’s audience doesn’t mean stripping out your congregation’s identity. It means leading with the questions a stranger actually has, before the internal details.

Service times and directions belong above the fold, written in plain language. “What to expect on your first visit” deserves its own page, covering dress code, parking, and what happens with kids during the service. Staff bios should explain roles in everyday terms, not just titles that only make sense to insiders.

Photos matter too. A picture of the actual room someone will sit in, taken at eye level, does more work than a stock image of hands raised in worship. Language matters as well; church jargon like “narthex” or “small group covenant” can wait until after someone already feels welcome enough to ask.

None of this requires abandoning your community’s culture. It simply means writing the front door of your website for the person who hasn’t opened it yet, then letting the deeper pages serve the people who already have.

Before your next redesign, sit down with your website open and ask a simple question of every page: would this make sense to someone who has never set foot in our building? If the honest answer is no, you’ve found where the work needs to start.

Your congregation doesn’t need convincing. They’re already here. The people your website should be working hardest for are the ones still deciding whether to come at all.

We build church websites for the visitor still deciding whether to walk in. Clear service details. Plain language. A first-visit page that answers the questions strangers actually ask. Built for Canadian churches, done for you, so your team can focus on ministry instead of maintaining a template.