What good church websites have in common
Good church websites share four traits: service time and address visible without scrolling, photographs of the actual congregation, a clear answer to what a first visit is like, and content that was updated this month. Design style varies enormously; these four do not.
What does a good church website put first?
Service time and address, visible without scrolling and without opening a menu. This is the single most common difference between church websites that work and ones that do not.
It looks unambitious next to a large photograph and a welcome message. It serves the most common visitor on their first click, which no welcome message does.
Why do photographs matter so much?
Because the visitor deciding whether to attend is asking one question: will I feel out of place. Photographs of the actual congregation answer it in a second.
Stock photography answers it badly. Visitors recognise stock images, and a church using them appears to be hiding what it looks like, which is precisely the opposite of the intended effect.
What do the best church websites explain that others skip?
What actually happens at a service. How long it lasts, what people wear, whether there is childcare, where to park, and what a newcomer should expect to be asked.
Almost no church website answers these plainly, and they are what a nervous first-time visitor most wants to know. A page that does is unusually persuasive at almost no cost.
How do you tell a maintained site from a neglected one?
Look for dates. An event calendar whose most recent entry is from last year, a sermon archive stopping in March, a staff page listing someone who left: each says the congregation stopped paying attention.
This is why smaller sites often outperform larger ones. Three current pages read as a living church; twelve pages with stale corners read as a dormant one.
How can we check our own site?
Open it on a phone, on mobile data rather than church wifi. Time how long until something appears. Then, without scrolling, look for the service time and address.
Then ask someone who has never attended to find out what a first visit is like, and watch where they get stuck. Ten minutes of this finds more than any audit report.
| Check | Pass | Common failure |
|---|---|---|
| Service time without scrolling | Visible immediately | Buried on a subpage |
| Address without scrolling | Visible immediately | Only in the footer |
| Photographs | Real congregation | Stock imagery |
| First-visit information | Its own page | Not addressed |
| Most recent date on the site | This month | Over a year old |
| Loads on mobile data | Under 2.5 seconds | Over 5 seconds |
Work in this area
Frequently asked questions
Should we copy a church website we like?
Copy the structure, never the text. What works is the order information appears in; copied text describes another congregation and reads that way.
Do we need a modern design?
Less than you think. A plain, current, fast site outperforms a stylish one that is out of date. Style is the least important of the four traits.
How many pages should a church website have?
As many as the congregation will keep current. For most that is three to six. Empty sections do more harm than missing ones.
Should we show our statement of faith?
Yes, on its own page rather than the homepage. People looking for it will find it; people deciding whether to visit are asking a different question first.
Is a sermon archive worth having?
Yes if sermons are recorded consistently. It is often the largest body of unique content a church owns and it accumulates search visibility over years. An archive that stops is worse than none.
Talk it through first
A short call costs nothing and usually clarifies whether this is the right next step for your organisation.
Get in touch