Thirteen Commandments for your website (church websites, part 1)

I spend a lot of time looking at congregation websites, between my work and my travel. It is not uncommon for me to be in a new city and to wonder about a Sunday or midweek service at a nearby church. And too often, I find that the websites are terrible. I mean really, really awful. This is not new, and I am not the first person to say this.

Until about two days ago, I’ve always figured there were others who are better equipped to speak on this topic (and that’s still true). But recently I was looking at a church website, for a church that shall remain nameless. Let’s call it St. Luke’s (but it wasn’t that). I saw some inbound traffic over on Lent Madness, and I was curious what they were saying about it. That part was fine. “St. Luke’s” also has lots of interesting info about current programs, staff, and worship opportunities. Then I got curious what diocese the church was in. After several minutes, I could not figure out in which city or even state the church is located. Seriously, I could find the physical location of this church nowhere on its website.

TEC website welcomeSo that pushed me a bit over the edge, and I ranted to myself for a good long while, and then to a few people who had the misfortune to be near me at the time. Then I decided I should mention a few things — that is, rant — about church websites here on my blog. It’s not that lots of other people haven’t mentioned this or that I have particularly insightful things to say. Still, maybe a few churches will see something here and decide to make their site better. And that’s a win, a win for the internet and for Jesus.

My first thought was to write a single post. Then I realized it would make even Crusty Old Dean look terse, so I’m breaking this into three posts. This one is Thirteen Commandments for Church Websites. Next up is Make Great Websites for Cheap! This will include some examples! And, finally, I’ll close with How to Kill Your Church By Misusing the Internet.

Here is a baker’s dozen of commandments in no particular order. So without further blahblah…

Thirteen Commandments for Church Websites

I. Remember that the website is first and foremost for guests and seekers. Every single thing about the website should be geared toward people who are looking for a church or who are new to your church. Current members are not well equipped to figure out the success here, so ask people who are legit newbies to look at your website and tell you how you’re doing. (Yes, you should put insider stuff on your website too, but tuck it away somewhere off to the side.)

II. Make sure your site looks great on a desktop, a tablet, and a phone. It’s quite likely that people are looking at your church website on a phone, and if it only works on a desktop, you’re doomed. There are lots of ways to fix this; the problem has gotten easier to solve in the last 2-3 years.

III. The full physical address and phone number of your church should be in the footer of every page on the site. If you can’t do that for some reason, these things belong on the home page. The address needs to include the ZIP code, and a link to Google Maps or Bing or something is a bonus. Twice in the last year I’ve looked at church websites that did not seem to say where they’re actually located.

IV. Use photos to show who you are. Be honest. It’s great to have Easter photos, but if your church looks a lot different on an average Sunday, show that, too. If you’re a very diverse congregation (which is sadly unlikely in the Episcopal Church or most mainline churches), show that. If you’re not diverse, ask hard questions about why. For your website, be careful in walking a line between showing who you hope to be and who you are now.

Your photos should be high quality, but you don’t need a pro for that. Nearly every congregation has someone with photo talent, so ask that person who take some snaps. Get photos of people — people worshiping, doing outreach work, enjoying fellowship, praying, whatever. It’s also a great idea to have a photo of the outside of your church on the front page of the website, because a first-time visitor will want reassurance they’re at the right place.

Do not use stock photos. Just don’t do it.

V. Make worship seem important! Worship is the thing, right? Service times should be on the home page, and a more complete description of the services (using language that an average non-Episcopalian will understand) can be tucked inside. “Rite II uses modern language” may not mean much to a seeker. In fact, only an Episcopalian who is searching for a church in a new town is likely to care. My experience — and I don’t think I’m alone here — is that seekers usually aren’t particularly interested in the language of the Eucharistic prayer (Rite I, Rite II, or EOW), but have different priorities. I’m not saying you shouldn’t provide that info, but I’m not sure it’s the most important thing. Maybe more useful is a sense of what kind of music to expect or how long the service lasts. Photos of worship are really helpful.

VI. Say something about your beliefs. If you’re an Episcopal Church, this should include mention of Jesus. I cannot believe how many churches have stuff like, “Bring your questions here, and we will accompany you on your spiritual journey.” Here’s a pro-tip. If your copy could be used for a yoga studio, a synagogue, or a coffee shop, there’s a serious problem. Yoga studios, synagogues, and coffee shops are totally awesome, and I hope they all thrive, but their purpose is different from a church, and your belief text should indicate why church matters.

If you’re talking about the Jesus Movement, say what that means or what it looks like in your congregation. Don’t assume that your average church-shopper has the faintest idea what the baptismal covenant is. But, also, don’t talk down to people. The person who has Googled your website probably already knows stuff and wants to learn more. Their presence on your website means they know how to use Google.

That said, it’s helpful to have some text about the Episcopal Church. Say something about what makes our flavor of Christianity (and your congregation, for that matter!) unique. Why would someone go to your church or to an Episcopal church instead of another? In doing this, there is no need to insult others or use platitudes about how friendly you are. Seriously, I am almost certain the nearest Chipotle is friendlier than a typical Episcopal church. So let’s not put our eggs in that basket…erm…taco.

VII. Show current events, but only if you can keep up your site. You don’t want to be like this church with outdated events info. If you aren’t going to keep up your site, just make it a static site. That’s not ideal, but it’s better than stale info. When I look at your website on December 15 and you’re telling me about Easter, I know that you just don’t care about guests. And you might not care that much about Jesus. Conversely, a “What’s on this Sunday?” note on your home page is awesome…if it’s for real.

There are some tricks to get a dynamic feel without much work. You can embed Episcopal News Service headlines or social media info or lectionary readings using widgets, so that they’re always fresh.

VIII. Show your social media connections. If you have a Facebook page (which you should), link to that. Since Facebook is easy to keep current, sending people there is a good way for them to find out what’s new.

IX. Worship times should be visible and current. This is redundant, but it’s incredibly important. So I’m mentioning again how it’s essential to list accurate service times on your website. If you change your service times on annual meeting Sunday (which is a terrible idea, but I digress), for the love of God, make sure that’s on the website well in advance of the Sunday. I cannot tell you how annoying it is to show up for a 10:30 a.m. service only to discover that the church had one service at 9:30 and I missed it. Did I mention that mucking around with service times is a lousy idea?

X. Introduce guests to your staff, and make them accessible for questions. Seekers are likely to be curious about clergy and program staff. What’s the priest like? How great is the music director? Pictures are important; videos are awesome if you can do it. This is not to say that clergy and program staff are more important than others, but the reality is that seekers want to see who leads the church. This should, of course, also include vestry and lay ministry leaders.

Listing actual email addresses for clergy is important. In my parish priest days, I would regularly get emails like “I am divorced, can I receive communion?” or “My three-year old is loud, will we be welcome?” or whatever. Ditch 1990s-era contact forms and show real email address. Whatever burden of spam that results is worth it. No one said it was easy to be a priest, so clergy need to do their jobs even if that means deleting spam.

XI. Say and show how children will be welcomed. A fair number of seekers will be parents of children. If children are really welcomed in worship services, say that (and photos are a plus). If your church is one of the many at which parents will be the recipient of withering glares, you probably don’t want to say that, but you should repent ASAP. Do children leave the liturgy for their own formation? Describe how that works. Show classrooms. Give some sense of what the programming or classes are like. Be honest, of course. It does no one any good to set false expectations. Oh, and assuming you’re doing background checks on volunteers & staff and that you are careful about Safe Church practices, say that too.

XII. Make it easy for people to give you money. You should have online donations, and perhaps it will make sense for people to be able to fill out a pledge card as well. If you’re thinking that everyone can write you a check, you are 20 years out of date. For lots of people, it’s online giving or nothing.

Don’t assume that guests won’t want to give. Seekers usually understand that churches rely on contributions, and most of them are ready to support you. On this topic, it’s a good idea to have current financial reports and annual reports available for folks to see, but they should be tucked off to the side somewhere.

XIII. Describe how to join the church. One of the silly reasons churches don’t grow is that they never ask people to become members of the church, nor do they make it easy to figure out the process. Tell people what to do to become members (including baptism or transfer) and what that means. If you don’t have online forms, it’s totally OK to give an email address, phone number, and staff or volunteer contact.


I’m sure you’ll think of other things that are essential for church websites. Please add your essentials in the comments. There are also about a billion of these lists floating around. My friend Malcolm French reminded me of Thom Ranier’s list of things to have and his list of mistakes. I liked Thom’s lists, but his context is not ours.

This is also a good place for me to confess what you already know, which is that some websites that I run do not pass all of these tests. For instance, Lent Madness is lousy on mobile, and our plans to fix that have been delayed again. Mea culpa.

Having an attractive, useful, and effective church website does not need to cost a fortune. In fact, for most congregations, it’s probably a mistake to spend a fortune. In the next blog post, we’ll look at some examples of good, inexpensive websites and how to get that done.

Please do leave comments. As I said at the top, I don’t want to pass myself off as an expert here. I’m just a passionate viewer of church websites, and I want us to put our best face forward, literally for the sake of the Gospel. My hope is to kindle a conversation and spur action that might help even a few congregations have better websites.

You may also like...

30 Responses

  1. Scott Knitter says:

    Great information! I just wonder how many parishes have exactly zero people (staff and parishioners) who have the skills (or time or willingness) to make and maintain an effective site. And what they can do if that’s the case. But if they have someone with the very basic skills, this article certainly helps with what they need to do in the site. And of course helps with making good sites much better. We’re at the point of needing (belatedly) to make our site responsive to various devices.

  2. normmorford says:

    Absolutely right and we are a “connectional” church and there
    ought to be one site which would give ready access to service
    times in every congregation in all fifty states!

  3. Joy Twelves says:

    Agree with all of this. I might add RE #13 (joining) that many folks especially millennials will attend, be active, give money but don’t really want to formally JOIN…any organization for that matter. So I guess what I’m saying is to make it clear that you don’t HAVE to join to be part of the community.

    • Scott Gunn says:

      I suspect that if membership is placed into the context of discipleship, then millennials and other non-joiners will be more likely to value it. The problem is that our church culture treats membership like a club, and folks quite rightly reject that.

  4. C. Wingate says:

    “It’s also a great idea to have a photo of the outside of your church on the front page of the website, because a first-time visitor will want reassurance they’re at the right place.” And there should be a picture of the sanctuary/worship space as well. I come across way too many church websites where all the pictures are candids shot at the church picnic.

  5. Darrell Brown says:

    The question of “Does your website?” should become even more specific as to does Each Episcopal church house ,within its Body, truly “Welcome” all people who truly seek the Lord? Or are they merely Trojan horses of hospitality with a form and fashion of holiness denying the Power Thereof?

  6. Michael Wachter says:

    Regarding VII (social media), if your church’s social media strategy relies solely on Facebook, you are seriously limiting the potential of online networks and are missing most people under the age of 40. At minimum, I would recommend have regularly updated (weekly minimum) accounts with Facebook, Twitter, and Instagram. Clergy and staff should have up-to-date profiles on LinkedIn. Those working with youth should strongly consider the use of Snapchat.

    Remember the operative word is “social” – your posts should attempt to engage readers and stimulate online conversations about you church and its mission. Please do not use the same content across social media platforms. There are a number of excellent online guides which can help you craft messages for each platform. Finally, including photos enhances readership over a plain text post (video is even better).

    • Scott Gunn says:

      That’s completely true for larger congregations, for sure. However, the median average Sunday attendance in the Episcopal Church is 59, and that median church might have no full-time staff. Couple that with demographics, and I’m not sure that maintaining a presence on several channels makes sense. Facebook and Pinterest skew toward TEC demographics, but Twitter and Instagram (and certainly Snapchat) skew younger and more urban than we’re likely to be. So my point is figure out the sweet spot(s) for your context, and do those well. Then if resources permit, spread out.

      • Michael Wachter says:

        While I can appreciate the challenges of small congregations, it is also important to consider the decline in median attendance was 65 in 2011. As I tell my marketing students, the use of marketing communications to build or foster relationships with the community requires the use of multiple channels and its associated channels to reach those we desire to reach. Smaller congregations will need t work smarter and adopt tools which allow them to broadcast their message across multiple platforms. For example, Instagram permits users to forward pics and videos to Facebook and Twitter simultaneously. Ideally, we should tailor the message to the platform, but this would be better than nothing.

        I enjoyed this piece and look forward to parts 2 and 3. An up-to-date, aesthetically pleasing, and easily navigated church website is a critical “cost of entry” these days. I hope your tips will get congregations on the right path.

        • Sarah Smith says:

          I’m 32, work with youth, college students, young families and young adults and think just Facebook is ok in a lot of contexts. Authentic is better than “trying too hard to be something you’re not”. Careful about categorizing everybody under 40…

  7. John Miller says:

    In my experence, any church that advertises themselves as “Friendly” and “Welcoming” as their primary characteristics is actually insular, inward-focused and dieing slowly of attrition. This is definitely an aspect of a church website where it is better to show then tell.

    • Scott Knitter says:

      I chuckle when I remember visiting a church long ago and reading their brochure; the big headline on it was “When we say ‘welcome,’ we MEAN ‘welcome’!” As opposed to all those other places that don’t mean it. Anyway, I agree that “friendly” and “welcoming” are adjectives best applied by newcomers who experience those aspects, not by the parish itself.

    • Scott Gunn says:

      Preach. Right there with you.

    • Heh. I just made this point in an article I have coming out for publication soon in which one of the things I note is that it’s more important to actually *be* welcoming than to tout being welcoming on your website. And that would not have to do with the number of different churches I’ve been to as an adult where I’ve seen various degrees of success on that front.

  8. Excellent! Where might a small church with one full time staff member find a good, inexpensive resource to get help in upgrading our site to show that we are followers of Jesus Christ, professional, welcoming and inviting-which we are?

  9. Peggy says:

    I have been church-hopping (not quite shopping) and one local church has 3 different sets of service times on their website. I haven’t been there yet.

    Also it is very important to mention, as Scott said, what kind of music to expect or whether there is no music at a service. If I visited your church and there was no music, I would not come back. Better that I visit at your OTHER service with choir, organ, and lots of hymns.

  10. Sarah Kelb says:

    One little trick I like to do with our church website is- if a link is going to take the visitor off of your website and on to another, I have the link open in a new tab.

    The html code looks like this:
    Lenten Madness

    The target=”_blank” is the key to having the link open in a new tab. If the link opens within your own website, this is not necessary.

  11. Trina Soltys says:

    Thank you for the list of tips. On review, I think that our church website is great! We developed it using

  12. Scott.
    Please,, would you look at our website if you have time. We are a small church in a community serving mostly retired members and visitors related to the retired members or looking for a place to retire.

  13. ambly says:

    This is marvelous and I’ve passed it on to Facebook. Just yesterday I was looking for the telephone number for a parish – a large and prominent one – and it did not appear anywhere on their website. But my pet peeve are churches that don’t update calendars or event for years – they might as well advertise they are out of business.

  14. deacondorothee says:

    Nice Scott, thanks for this!

  15. Jonathan Galliher says:

    I disagree on one point. You shouldn’t check how your website looks on *a* phone; you should check how it looks on a *variety of types* of phone. There are certainly hundreds and maybe thousands of variations, especially if you add in the different browsers, and they each have slight but critical differences. Fortunately, you don’t need to check all the types unless you’re expecting a lot of international visitors. I mean, how likely is it that someone from mainland China or the Indian subcontinent will be surfing to your site?

    Going along with checking your site with a variety of devices, you should also be collecting analytics so that you know how people are viewing your site. They’re particularly helpful for identifying the devices and browsers you need your website to work on.

    Don’t worry about the technical side of this too much. Practically everyone needs to do these things so there are a lot of good and inexpensive tools out there. The content side of things is much harder since you’ll have to come up with it yourselves. Oh and try not to listen to tech folks hype the latest hot new thing like SPAs (Single Page Apps) or Progressive Web Design. They probably won’t help you much, but will have issues that are harder to resolve unless you’re a professional web developer.

  16. Chaplain J.R.Bunyan says:

    This was all very useful, but when I attempted to print this article to share among some churches, I found the printer printing off over 70 pages of words shuffled about in such a way that even one page would have been of no use. THIS site needs fixing. (I don’t have Facebook, etc, etc).

    • Scott Gunn says:

      Thanks for your comment. Until your comment, I didn’t realize printing was broken. That must have happened with a recent theme update. I’ll see what I can do in terms of a workaround. Meanwhile, I’ll be glad to stick the post into a PDF that I can email you for you to print easily. Sorry about the problem!

  17. Jonathan Tallon says:

    Good article. One addition:

    14 Add accessibility information. Is it wheelchair accessible? Is there an induction loop? Are there wheelchair accessible toilets? Is the service signed? Etc.

  18. Rich Houser says:

    Great article. There are some great features that allow you to post one time and get that post automatically on the other social media platforms. Instagram has a feature where you can post to Twitter and Facebook at the same time. If you advertise on Facebook, which we do, it allows you to post to Instagram as well. Sounds like a lot, I know, but those three platforms actually attract very different audiences, ages, demos, etc.

    We. have not gone mobile on our website because the interfaces look really clunky. We will continue to look for sharper examples.

  19. Hey Scott, I’ve been helping churches with their websites through for 20 years. Your advice is spot on. The biggest challenge I see is that most churches don’t have a web developer on staff or the resources to hire a web developer to build a site for them. That’s why we created an easy to use DIY church website builder. If there’s anything we can do to help your readers with their church websites, please let me know.

%d bloggers like this: