Most "best church websites" lists are galleries. Somebody screenshots a dozen megachurch homepages with cinematic photography and enormous type, and a pastor of a hundred and forty in a forty-year-old building scrolls through it and feels worse than when he started.
That is not useful, so this is not that.
What follows are twelve things the good ones do, each with a live site you can open in another tab and check. I should say plainly that most of the examples are sites I built, because those are the ones whose decisions I can explain honestly rather than guess at. You should discount for that. The traits themselves do not care who built anything — run them against your own site, and against mine, and against whoever else you are considering.
1. Service times and address are visible before you scroll
This is the whole ballgame and most churches lose it.
Someone finds your church at 9:40 on a Sunday morning, on a phone, in a car. They have one question and about eight seconds. If the answer requires a scroll, a click on "About," or a hunt through a hamburger menu, a meaningful share of those people are gone — and they were the ones who were already coming.
Put the time and the street address in the top screen. Not "Sundays at 10:30" alone — the address too, spelled out, and tappable so their phone offers directions.
Look at: Knotty Oak Baptist Church, Coventry, Rhode Island. Time, place, and the way in, before anything else.
2. It is fast on a phone on bad signal
Over two-thirds of the people who visit your website are on a phone, and a real portion of them are on two bars in a parking lot.
The usual culprit is not code. It is a single photograph exported straight from a camera at eight megabytes, sitting at the top of the homepage. Compress your images and you will fix most of it. If your homepage takes more than about two and a half seconds to show something meaningful on cellular data, that is the first thing to fix, before any redesign.
3. The photographs are of the actual church
Every pastor knows the feeling of opening a church website and seeing four attractive strangers laughing over coffee. Visitors know it too. Stock photography does not read as professional; it reads as this is not about us.
The counterintuitive part: a slightly imperfect photograph of your real sanctuary, with your real people in it, is more persuasive than a technically superior stock image. It answers the question the visitor is actually asking, which is not "is this church tasteful" but "what will it be like when I walk in, and will I be the only one who looks like me."
Look at: Gideon Baptist Church, Warren, Michigan — every face on it attends the church.
4. There is one obvious next step for a stranger
A church website serves two audiences with opposite needs. Members want the calendar, the giving link, and the bulletin. Strangers want to know whether they will be welcome and what will happen to them.
The good sites do not make the stranger compete with the member. They give the stranger one clearly marked path — "Plan a visit," "What to expect," "New here" — and let the members go find the calendar, which they will, because they know where it is.
Write the what-to-expect page as though answering the questions people are too polite to ask. How long is the service. What do people wear. Where do I park. Will someone make me stand up. What happens to my four-year-old. Answer those in plain sentences and you will have done more for your visitors than a redesign.
5. Sermons are actually browsable
Nearly every church site has a sermons page. Very few have one you can use.
The difference is search and structure: can I find a message on a passage, by a date, or by a title, without scrolling through two hundred YouTube embeds? A church with a decade of preaching has a genuine archive, and it is often the most valuable thing on the site — for members who missed a Sunday, for people who are considering visiting and want to hear the pastor first, and for search engines, which will index a sermon page with real text on it and send you people you will never otherwise meet.
Look at: Independent Baptist Church of Keeseville, New York — a full archive that updates itself as new messages are posted, rather than waiting on somebody to remember.
6. Giving takes about four taps
Whatever platform you use, count the taps from your homepage to a completed gift. If it is more than about four, you are losing money to friction.
Two specific things to watch. First, embedded giving forms from some providers hijack the page's scrolling on a phone, so a visitor gets stuck in a small box and cannot get out. Load the giving form on a tap instead of automatically, and that problem disappears. Second, if you accept online gifts, know your rate — 2 to 3 percent plus about thirty cents per gift is normal, and on a church of any size that is the largest ongoing cost attached to your website.
7. The events page is not a graveyard
An events page whose most recent entry is from last October does more damage than no events page at all. To a visitor, it does not read as "they have been busy." It reads as possibly closed.
The structural fix is to give every event an end date and let it remove itself. A church website should never be able to display a stale event, because the person who would have caught it is the person who is already too busy — which is exactly why it is stale.
If you cannot automate it, delete the page. An honest absence beats a visible sign of neglect.
8. It works for the people you are actually trying to reach
Generic best-practice lists miss this one entirely, and it is often the difference between a site that works and one that does not.
If a meaningful part of your community speaks Spanish, the site should. If your congregation skews older, the type should be larger than a design blog would recommend and the contrast higher. If you have a deaf ministry, the sermon videos need captions, and that is not a nicety.
Look at: Encuentro Church in Houston, built in Spanish because that is the language of the people it is for.
9. Somebody can change it without calling somebody
Here is the trait that predicts, better than any other, whether a church website will still be good in three years.
Every site on this page will be wrong about something within six months. A time changes, a staff member leaves, a special service gets scheduled. The question is not whether that happens. It is what stands between the person who notices and the fix.
If the answer is "email the guy who built it and wait," the site will drift, because the guy gets busy and the pastor gets busier. Whatever platform you choose, the test is whether a non-technical person on your staff can make a small change on a Tuesday afternoon without dread.
This is the problem I have spent the most time on in my own work — the sites I build connect to ChatGPT or Claude so a pastor can type "move Wednesday service to 6:30" and the live site updates. You do not have to solve it my way. You do have to solve it.
10. The church's own character is on the page
The great weakness of templated church sites is that they all end up feeling like the same nondenominational church plant — the same warm gradient, the same three-column ministry grid, the same stock phrase about "doing life together."
A church that has been on the same corner since 1911 should not look like a church that started in a school gym last spring. Both are good; they are not the same, and a visitor is trying to find out which one you are.
Look at: Bow Baptist Church in Vermont and Victory Community of Faith in Wichita. Different congregations, different centuries of feel, neither one trying to be the other.
11. It can be found
A beautiful website nobody finds is a tract in a drawer.
Most of the "church near me" battle is not on your website at all — it is your Google Business Profile, and it is free. Claim it, get the hours and the address exactly right, add photos, and ask a few members to leave an honest review. That single afternoon of work moves more people toward your door than a redesign will.
On the site itself, the basics are enough: your church name, city, and denomination in the page title; a real address in the footer; and pages with actual sentences on them rather than text baked into images.
12. Everything on it is true
This is the last one and the only one that is non-negotiable.
Correct service times. Correct address. A phone number somebody answers. Staff who still attend. A statement of faith that matches what is preached.
I have looked at the websites of more than thirty thousand churches while building my own work, and the most common failure by a very wide margin is not ugliness. It is abandonment — a site built with real love in 2013, still up, still listing a pastor who moved away in 2019. The visitor who lands there does not think "outdated." They think "I wonder if they're still open," and they go somewhere else, and nobody at the church ever learns that it happened.
The ten-minute test
Open your church's website on your phone — your phone, not the office computer, and off wifi. Answer these honestly.
- Can I see the service time and street address without scrolling?
- Did something meaningful appear within about three seconds?
- Is the first photograph of people who actually attend here?
- Is there one obvious thing for a first-time visitor to click?
- Can I get from the homepage to a completed gift in four taps?
- Is the most recent item on the events page in the future?
- Does tapping the address open maps, and the phone number start a call?
- Are the staff listed still here?
- Is every service time correct today?
- If I found one thing wrong, do I know who would fix it, and how long it would take?
Six or better and your site is doing its job. Below that, you do not necessarily need a redesign — you may need an afternoon.
If you would rather have it checked for you, the free church website score runs the technical half of this list automatically. If you are weighing who to hire, I compared fourteen church website companies and wrote up what a church website actually costs — both written to be useful whether or not you ever call me.