Skip to content
Back to Blog
Church WebsitesJuly 13, 20265 min read

The Cousin Bob Problem: Why Your Church Website Went Stale (and What the Data Says)

A volunteer built the church website years ago and nobody can update it. Our directory data shows how common the problem is, and the fixes cost less than you think.

J

John Moelker

Founder, ChurchWiseAI

I have a name for the most common reason a church website dies. I call it the Cousin Bob Problem. A well-meaning volunteer, often a relative of someone on the board, builds the church a website. He does it for free, out of love, and it works for a while. Then Bob changes jobs, or moves, or just gets busy. Nobody else has the password. The service times on the site are from two pastors ago, and everyone at the church has quietly stopped mentioning it.

I spent 15 years as a software engineer and then 15 years pastoring in Reformed churches in Ontario, so I have seen this from both sides of the desk. I have been the pastor who did not want to bother Bob again, and I have been the engineer who knew exactly how small the fix actually was.

What our directory data shows

Here is the part that surprised even me. Our company runs PewSearch, a free directory of churches across the United States. When we counted this week, the directory held 221,848 visible church listings. Of those, 126,307 had no website on file at all. That is 57 percent.

Some of those churches surely have a website we have not found yet, so treat 57 percent as an upper bound on the true number. But even discounted heavily, the picture is clear: a huge share of North American churches are effectively invisible to anyone who searches online, and an even larger share have a site that exists but has gone stale under the Cousin Bob pattern.

Why this matters more than it used to

A church website used to be a brochure. Now it is the front door. When a family moves to town, the first visit happens on a phone screen days before it happens in a pew. If the site is missing, or shows last year's Easter schedule, that family draws a conclusion about whether the church has room for them. They are usually wrong about the church, but they never find that out.

And it is no longer just Google. People now ask AI assistants questions like "what churches near me have a children's program" and the assistant answers from whatever it can read online. A church with no site, or a stale one, simply does not exist in that answer.

What I tell churches

When a pastor asks me what to do about the website, here is what I actually say, in order:

  1. Get the basics right before anything fancy. Name, address, service times, phone number, one photo of real people. A one-page site with accurate service times beats a beautiful ten-page site that is wrong.
  2. Make sure someone on staff, not a volunteer, can edit it in under a minute. The Cousin Bob Problem is not a skills problem, it is an access problem. If updating the service time requires a phone call to someone outside the building, the site will go stale again.
  3. Claim your directory listings. PewSearch listings are free, and so is a Google Business Profile. These are what AI assistants and search engines read first.
  4. Only then think about extras like online giving links or a chat widget.

Where our product fits, honestly

This is the part where a vendor usually pretends the product is the only answer. It is not. Plenty of churches will be fine with a volunteer and a free page builder, and I tell them so.

We built ChurchWiseAI Pro Website for the churches that are not fine: a hosted church site with denomination-aware templates that a church secretary can edit herself, at $14.95 a month, or $19.95 with an AI chat assistant that answers visitor questions around the clock. The chat assistant follows our bridge rule: it answers logistics and connects people to a real human at the church, it does not play pastor. If that is useful to you, it exists. If Bob is reliable and the site is current, you do not need us.

Sources

  • PewSearch church directory, live database count, July 13, 2026 (221,848 visible listings; 126,307 with no website on file). pewsearch.com

Frequently asked questions

Does a small church really need a website?

If your church wants new people to find it, yes. The majority of first contact with a church now happens online before anyone walks through the door. A single accurate page with service times, address, and phone number is enough to start.

How many churches have no website?

In the PewSearch directory of 221,848 visible church listings, 126,307 (57 percent) have no website on file as of July 2026. The true number of churches with no site is likely lower, since some sites are simply not in our data, but it remains a large minority at minimum.

What should a church website include at minimum?

Service times, physical address, phone number, a short description of the congregation, and at least one recent photo. Accuracy matters more than design: an out-of-date site actively costs visitors.

What does a church website cost?

Free options exist through page builders and denominational programs. Managed church-specific options like ChurchWiseAI Pro Website run $14.95 to $19.95 per month. Custom agency builds typically run into the thousands up front.

Share
J

John Moelker

Founder, ChurchWiseAI

Software Engineer (15 years) and pastor (15 years), founder of ChurchWiseAI.

Ready to Add AI to Your Church?

See how ChurchWiseAI helps churches never miss a call, engage every visitor, and free their staff for real ministry.