
Visit my
SundayResources.net website
for more New and Improved "Building a Better Church Website" tips, and my blog
about church issues, improving the church/staff/meetings, "Green Jesus" (church
& eco/energy issues) and books I recommend.
Over the years I've severely revised this original article. But try as I might, it continues to be long (it used to be a lot longer), and rambling (I keep adding ideas). As always, your feedback and questions welcome. neil@sundaysoftware.com
BEST ADVICE: I'm now recommending that many churches take a SERIOUS LOOK at creating their church site in WORDPRESS. See my article about this subject at www.sundaysoftware.com/wordpress.htm Wordpress has a lot of the features that help churches communicate on the web effectively, without all the pitfalls described in this article below, and also in the Wordpress article. My article also has a lot of Wordpress Tips for church websites in it, including how to see up a free email church newsletter at your site.
Why Wordpress for your Church Website?
Wordpress is a great way to quickly and inexpensively create a professional-looking website that can have several advanced features.
Wordpress allows you experiment for free, and it's incredibly cheap from there on out.
Wordpress can be accessed by any computer, from home or office.
Wordpress allows multiple volunteers to work on the site.
Wordpress allows you to easily integrate some of the most IMPORTANT FEATURES any church website could ever have: a site that alerts members to new content.Read my full article about creating a church website in Wordpress over at www.sundaysoftware.com/wordpress.htm
WARNING: SOME "web techies" will turn their nose up at this suggestion. They would rather build you a custom website using their favorite web tool, which of course, puts them in control and puts all the files on their computer. The problem is that over time, they will quit working on the site, and then what? If there's one single common problem with church websites, that's it.
Wordpress, and other similar web-based, site-building solutions, allow access by multiple contributors to the tools and content. The tools are at the website, not on somebody's computer. And they are easy to use. This helps your website "SURVIVE" the inevitable demise of the original web-techie's enthusiasm. This is real advice from not only myself, but from many of the church techies and pastors I've been talking with for over a decade about their websites. Ignore it and you're probably a dope.
The Old Idea: Our Church Website is a Billboard for Visitors on the Information Superhighway
The Better Idea: Our Church Website is a place to learn, get announcements, and connect with each other members.
Back when most people weren't on the internet, churches were pleased to put up Billboards for visitors saying "here we are." Now that nearly EVERYONE is on the internet, church websites can now function like church newsletters, and as a way for members to get in touch with each other.
Visitors will be attracted by fresh content that shows off a vibrant community. "Message to Visitors" pages are ok, but it's the rest of your site that's the real message. And most visitors are looking for a community that looks welcoming and like a place they will fit in. Show that by posting lots of good photos.
Your site doesn't need to be a one person effort, or one-way conversation these days either. Creating your software using a web-tool like Wordpress allows multiple authors to keep the news flowing, and the conversation going. Wordpress was originally a "blog" software, so it has many features which allow people to "talk back" to your postings and to each other. Learn how to build your site in Wordpress at www.sundaysoftware.com/wordpress.htm
Ultimately, you want people to come back to your site. Thus, adding an email newsletter subscription or "feedburner.com"-like service (for free) at your website gives YOU a tremendous tool for ALERTING people about new content. I can't stress enough the importance of these features to bringing people BACK to your website. I discuss how to add a feedburner service or email newsletter to your site -over at www.sundaysoftware.com/wordpress.htm
|
Neil's Definition of a Good Church Website:
Neil's Definition of a Bad Church Website:
|
Here are some Tips for Building a Good Church Website:
Design your site for your members, especially those who surf. Design a page they can use as their "start" page or "home page" that pops up every time they turn on their browser. Put a button on your main page that says "make this website your homepage." It's an easy button to code. Every browser is designed to open up to some webpage. Make your church's site the first thing your members see when they start surfing the net. (Notice this is my top suggestion. Create and coding the habit of coming to the church's page is important IF you are creating a site that will stay fresh.)
Design your site ABOUT your members. Show visitors who you are, what you're like, and it will also remind members why they are members! This requires plenty of PHOTOS. They are word a thousand words.
Keep it simple. Don't create so many pages that the work of updating becomes tedious. 5 or 6 well done up to date pages are better than 10 pages that look amateurish and are out of date. One or two "updates" a month will suffice for most members (see my discussion above for this reasoning).
Friendly photos + photos that are friendly + photos of friends!
Make sure you have excellent server-provided web statistics. Cheapie "counters" like you see on some sites are useless. Stats will help you build your case for a better site, more staff input, or keep your creative work under control. Share these stats with church leaders. Many will be surprised. It will also get them to use the site!
Instead of boring mission statements and 10 second downloads of the church steeple, give them a brief reminder of a coming event and a pithy verse, quote or recent sermon one-liner to start their day (or evening) on the Internet. Keep it fresh.
Watch your language. Many church websites read like they were written by computer geeks. Write them from a P.R. angle. Give your website personality!
Provide links right on the main page to major search engines like Yahoo! which is probably where they will go next.
Maintain a "links" page of Internet sites suggested by fellow members, such as websites for parenting issues. One of my favorite sites to recommend is a family movie review site (you can link to it at my software page). List the local movie theater. A lot of web surfers check the web for movie times and reviews.
Create opportunities for members to share with each other. Talk to a website designer or your Internet Service Provider about list-serv discussion possibilities for bible studies and discussion groups -or do these through a message board right on your website.
Create an email newsletter members can subscribe to for free. The e-news can alert them to upcoming events, changes and new resources at the website.
Create a message board page or have a comments feature that allows your members to respond to each other's needs, ideas, and can conduct a running bible study. If your church is large enough, you may find that it fills a need for a small percentage of your members, and will grow with time. A message board can also provide you with an email newsletter function. You can also build your site using WORDPRESS to allow people to leave comments to posts and talkback to each. For more on building a church website using Wordpress, go to www.sundaysoftware.com/wordpress.htm
Don't use pale colors and small text which make it hard to read for older people.
Work with a committee.
Make sure somebody other than yourself believes the website should look good and be functional, -and knows how to make it so! ...otherwise there will come a day when you move on and your work ends up a wasted effort.
More Church Website Tips....
A boring "Welcome from the Pastor" is of dubious value. Instead, provide a happy picture of the pastor having fun at a church event. Include three or four sentences from the pastor, MAX. This can change every month.
Spare us the two page TEXT description of the youth program. Instead, post two recent youth photos, coming events and contact info, and a page to print containing the standard medical release form they have lost. Post a page of links for youth submitted by youth.
Mission pages are a must. Give us a list of the projects you support along with two or three pictures of members in action (small file size please).
I lose about two softball schedules a year, give me a page where I can print out a new one.
Create a page new-comers can print out that has critical info they can post on their refrigerator: Sunday schedule, phone, staff names, map to the church.
Keep your content brief, well organized and fresh. Make it look nice but don't over do it.
Change/Add something new about every two to three weeks. This can be as simple as worship updates and a "favorite photo" of the month.
Change a significant design element on your main page every couple of months. Keeping it fresh with "site of the month" type of stuff will keep folks coming back.
Save us from poor web design, sites designed by automatic "free web page" offers, and sites hosting by providers like Geocities that place advertisements on every screen.
Neil's Rules for deciding the church's web address:
(also known as "domain name")1. Easy to spell
2. Easy to remember
3. Easy to say
4. Easy to understand when heard
5. Rolls off the tongue
6. No hyphens, extra 'dots' or underscores
7. Relatively short
8. Reasonably descriptive of what the site is
9. .org, not .com (A surprising number of church list themselves as commercial sites)
10. Will wear well over the years.Good: www.secondchurch.org
Bad: www.second-presbyterian-online.comWhy is this bad? Too long. People will misspell Presbyterian, and churches should be dot-org, not dot-com.
Good: www.First--Indianapolis.org
Bad: www.1stChurch-Indy.org
Why is this bad? Try speaking the url outloud to yourself. "First as in the number 1, stchurch dash indy".
Everybody likes to get email.. Create opportunities for members-to-member and member-to-staff email.
Post council minutes for officers (especially for those who travel). You can set these up in password protected folders.
Post sermons, newsletter articles and pictures of recent events.
Learn how to optimize your photos and graphics for quick download.
Create a section on your main page that has changing pictures/graphics. There are several Java scripts that do this automatically --with no management needed other than posting new photos to a file. These scripts can be found for free on the Internet.
Still more good tips...
Put your church's website address on absolutely everything: your lawn sign, your letterhead, and in your bulletin. Purchase refrigerator magnets with the address printed on them. Publish your website URL in the newspaper with an article about how you designed it. Having a site nobody knows about doesn't work.
Spend the money to get a "domain name" such as "www.firstlutheran.com." Do not cheap it out and create a site at "www.firstlutheran.freewebpages.com." Eventually you will want to move your site to a new provider and all your literature will have the old web address. By purchasing a domain name, you can switch service providers and never have to change your published web address. If you create your site in Wordpress, you can pay a small fee to have them register it to the domain name of your choice.
Take GOOD photographs, and make sure you process them correctly for the web. I've seen many church websites with good text and graphics, but lousy photographs, or photos whose file sizes are so big, the page bogs down on slow connections. One church recently asked me to review their website. They must have had 30 photos in a nice online album. But I kid you not --almost every person in every photo looked like they had just swallowed a Bible, -sideways. Members like to see themselves, but nobody likes to see themselves look bad. Visitors are trying to imagine "if that congregation looks friendly, and will I fit in." Take good photos, but also know how to process good photos for the web.
Your photos must be compressed and processed for the web. No photo should be over 60kb. Most photos need cropped. Most photos need lightened and their colors slightly boosted. Compressing photos for the web makes them a bit dark. This all takes a good software program. I recommend Photoshop Elements 2.0. It's under $80 and will make your web photos look great.
Yes, you can use photos of Members and their Children on your Website without permission. -an article spelling out your rights and theirs.
A Few Hard Lessons from Real Experience
My personal cautions to the techies responsible for building the church's website.I have created 9 different websites and consulted on several more. Each has taught me something about website management, design and usability. I've worked on sites and let others take them over too. You can learn a lot about churches and websites when YOU are no longer driving them. There's no experience like real experience.
Having rebuilt my own church's website TWICE, trained staff and volunteers to update it portions of it, watched the statistics closely (real stats provided by the server, not those hokey "749 visitors since 1903" counters), and then watched what happened to the site AFTER I was no longer at the church... I have concluded three things:
1) "What a church or staff says it wants, isn't necessarily what it will support or use."
2) A Modest but well-done website can attract a surprising number of visitors
3) After you're gone, if the staff didn't really care about it, it can become a wasteland faster than you can say "Death Valley."
1) "What a church or staff says it wants, isn't necessarily what it will support or use."
I have to regularly remind my church's staff to keep things updated, even though we made it VERY easy for them to update it themselves. There's nothing wrong with that. All leaders need helpers, ...and I'm willing to help. But what this means is IF you build a website for your church, you need to plan on working on it over the long haul. You know that old proverb, "raise up a child in the way they should go" ? You have to train your church and staff to use the website too. To put it another way, build it, and they still may take a while to come.
If you're the pastor reading this, you need to know that pastors often lament to me about the person who volunteered to build the website. They didn't know what they were doing, and/or didn't stick around for the long haul to keep improving things. Others lament having a website that's impossible for the next volunteer to change because the first one created the website with special web codes and databases which not every web volunteer understands or has the tools to update.
Some churches hire someone to do the heavy-lifting of building the website, then use a volunteer to provide updates. This means that if you hire someone to build your church website, you will need to budget "update" money. It's not a bad idea. But make sure you're hiring someone who knows how to build a website. I run across church websites all the time that are poorly designed by companies.
2) A Modest but well-done website can attract a surprising number of visitors
I was at a small suburban church for 10 years, and helped them with their site for 6 years. The site wasn't fancy, but it was colorful and happy, and utilized many of the extra special techniques mentioned in this article. Our main page had a button that says "make us your home page. We also had links to the weather forecast and religious news headlines to run on our main page, along with putting a Google Search BOX on the page. These aren't just links, they were part of the page. All these "feeds" from other websites are free. (Note: I'm not at that church anymore and they have since put up a different site that is not good.)
How we kept it fresh.... The center column of our webpage was text which the church staff could update without having to know HTML or upload a new page. With a little bit of code wizardry, we made them their own "update" webform on a special webpage they can access. You can learn about how we did that by visiting www.sundaysoftware.com/resources/htmlarea.htm. When they filled in the web form and click 'update' it puts their text into the main page of our website. Pretty slick.
We also put up a message board. It was free software that came from our ISP. They even set it up for free. Very easy to use. They used it to store certain documents, post schedules, and share email addresses. The message board was used mainly to archive schedules and meeting notes.
When you have an internet service provider host your website, a good one will also give you an 'online control panel' which includes server statistics about your visitors and pages viewed. Below are the webstats for the first five months of 2004 at my former church's site. It had been up for 7 months and advertised modestly during that time to the church members. (212 members)
"Unique" visitors tells us how many different visitors came that month. You only get counted once a month for that number. So we had 1165 different visitors make a grand total of 1330 visits last month. As you can tell in the next graphic below, only about 15% of our visitors in May stayed more than 2 minutes. Based on these numbers and some experience, and by excluding those who visited for less than 30 seconds (accidental visitors and web robots), I can guesstimate that most of our "more than 2 minute visitors" visited on average TWICE in the same month. So, for example, making weekly changes makes no sense. At least not now for us.
2007 Update on numbers: That site had 2037 visitors in May of 2007. Compared to 1330 in all of 2004. Church membership remained the same. I left that church in the summer of 2007.
The most helpful interpretation comes when we compare year to year statistics. In general, healthy percentage increases are a good general indication of overall traffic and importance to the members.
Yes, your web server and server stats can tell one visitor from another because each person who comes to a website has a number assigned by the referring server. You just can't tell who the visitor is. For example, my webstats tell me that "adsl-68-75-17-163.dsl.wotnoh.ameritech.net" viewed X total number of pages last month and created X amount of megabyte transfer (bandwidth) last month. The "number of visits" tells us how many visits those unique visitors made to the website. So let's say I visited on April 1, 5 and 10th. That would be a total of 1 unique visitors making 3 different visits. "Pages" shows how many different pages were viewed. "Hits" is often quote but very misleading stat. If I view this page, that's one hit, plus I get additional hits for every graphic/image on the page which are also considered hits. Thus one webpage can account for several "hits."
Our webstats also tell us HOW LONG each visitor stayed at our website, and which webpages they viewed. In May of 2004, 86.5% of all visitors accidentally step into our website and stayed less than 30 seconds. But 14.5% stayed longer, and 127 visitors STAYED at our website for over 2 minutes. I'm always wondering who those "15 and 30 minute visitors" are, God bless them.

127 visitors who stayed for over 2 minutes --that's good. Our stats also tell us the time of day they came to the site. HALF of those visits were "after hours." In fact, my pastor chuckled when he saw the visitors coming to the church website while he was asleep at home. It's a surprising world these stats have revealed to us. We've also seen a spike in "visits" toward the end of the week. Could that be folks looking for Sunday info? Could be.
Update: The number of visitors who stayed less than 30 seconds DROPPED to 59% in May 2007. We're making progress! The biggest reason was probably our message board. Since we added it 7 months ago, it has become our #1 destination on the site. And even more happily... our Visitors Page is now our 6th most viewed page. Up from 11th last year.
What do our visitors VISIT at our site? Consistently our staff, photos and worship pages get hit the most. Mission and CE are a distant second. Why staff? My guess is that members are looking for staff email addresses. We also put our full contact info on the staff page, things like our fax number. These stats made me go back and make sure our Staff webpage looked great. So many church staff webpages look terrible, beginning with lousy pictures of staff, or cheesy glam/Olan Mills photos. Go for the natural friendly photos, please!
We do NOT know how many of those visitors were church members, but what these numbers DO tell us is that our website is useful to a large group of people each month at a cost of only $16.95 a month to maintain.
One recent Sunday over two-thirds of the members in worship raised their hand when asked if they had visited the website in the last month.
3) After you're gone, if the staff didn't really care, the site can become a wasteland faster than you can say "Death Valley."
The site I have described above was one I worked on for a church where I used to attend. They had been enthusiastic about the website we had built. A Tech Committee was formed and embraced it. Pastor said how much he appreciated it. Then I decided to leave. Curious, I visited their site every month to see how they were keeping it up. The first couple of months they didn't change anything except the easy-to-change main page text about upcoming events. (Even that didn't look so good, as they no longer had me there to spell check, center text, and adjust a few things, -but hey, they were trying.)
Then about six months later they nuked virtually everything we had created. In it's place was a website I can only describe as "something that someone with NO web experience had posted." It was awful. Actually... it was beyond awful. It was amateurish, unkempt, and lifeless. It became one of those sites that this article was written to combat. Their awful new site says one of two things: 1) They didn't really care about their website. or 2) They didn't really care about doing things well. Update: 2 years later and it's still pretty bad.
And now you know why we moved-on from that church. What they did to the site, and what they accepted as a website prior to building them a better one, was an example in microcosm of the problems within that church. I originally wrote this previous sentence during Holy Week -viewing the site and seeing no mention of when special Holy Week Services are to be held. There was also no mention of the building project they have started, and only one poor photo on the CE page. There are new pictures of the church leaders, however. Bottom line: you can lead a horse to water, but you can't make them drink, -especially if they're not thirsty, or don't know how.
In retrospect, I should have helped the church identify people within the congregation who could maintain the website -other than me. Having a committee that cheered me on and offered suggestions -- didn't help. I should have also trained someone to understand how to put graphics on the website. The problem was this: as long as I was there to do it, they didn't need anyone else to do it. Of course, without me there, they should have found someone else who knew how to maintain and/or improve on what was there. That it looks 1995-ish and abandoned is a metaphor for church problems in general.
Taking over a site from somebody can be difficult as well, especially if they didn't know what they were doing and have lost things like the username and password to the domain name's registration. Been there.... have the stripes! Read my blog notes on "Domain Name & Voluntech Blues" at http://sundayresources.net/neil/2009/04/28/domain-name-voluntech-blues/
In my current church, I was led to create them a website in Wordpress for a number of reasons related to the discussion above.
Wordpress allowed me to create a good looking site very quickly.
Wordpress let's other collaborators easily contribute content.
Wordpress will always be there evolving and improving long after I'm no longer in charge of the site.
Read me complete article about Creating a church website in Wordpress at www.sundaysoftware.com/wordpress.htm
If you have questions or suggestions on this topic, feel free to email me, Neil MacQueen, neil@sundaysoftware.com
Neil MacQueen is a Presbyterian minister, interactive software and web designer, and President of Sunday Software Ministries.
Copyright 2004, 2007,
2009 Neil MacQueen. This
article may be copied for non-commercial purposes provided that
the author and this website remain with the article.