Skip to main content

9 THINGS THAT A CHURCH WEBSITE SHOULD HAVE


THINGS THAT A CHURCH WEBSITE SHOULD HAVE
There so many church website round the internet so am not going to tell you where to find a church website for any church but in this article am going to explain the basic things a church website should have which are outline below:

A DESIGN THAT REFLECTS “PEOPLE”, NOT BUILDINGS. People are searching for others whom they can relate to in order to establish a relationship. Buildings represent “institution”, not one on one fellowship.

ANNOUNCEMENTS AND CALENDAR OF EVENTS. The page that gets the most visits on any church site is the events page. Surveys on many church websites have revealed as high as 60% of visitors are looking for information about what, where, and when. A website can be a cost saving advertisement medium.


A WAY FOR PEOPLE TO FIND OUT HOW TO GET INVOLVED. This is for someone who is new to your church and really wants to get plugged in. All churches need volunteers, but most do not have an easy way for someone to learn about the need, or how and w ho to contact to get involved.

A WAY FOR USERS TO REGISTER ONLINE. Whether it’s just registering for a newsletter, registering for events, or having an entire section of your site for registered users, you need to get people to tell you who they are. A good website program will have this option as a standard.

A WAY FOR USERS TO CONTACT YOU FROM THE WEBSITE. A simple email link will not do. You need to provide as much contact information as possible, including address, phone, email address, and an online form so site visitors can submit an email directly from the website. Directions, service times, and office schedule. It’s easy to provide a link from Map quest, but much more


A WELL KEPT “RESOURCE DOWNLOAD” AREA. Whether it’s a download area for bulletins, sermon notes, or audio and video downloads, you need something to keep people coming back. Think “Web Ministry”!

ONLINE GIVING. This can be as simple as you want, or it can be integrated into church accounting software. But it is a must! Many people will setup automated recurring giving because that is how they pay bills, and make purchases online. Many people do not even carry a checkbook anymore. And the old-school thought about “paying tithes with a credit card is a sin” is out the door since most bank check cards come directly out of the individual’s checking account.

AN IN DEPTH LISTING OF MINISTRIES IN YOUR CHURCH. Be sure to have them in an order that makes sense, with a full listing of ministry meeting times, and leaders contact information. Keep in mind that “children’s ministries” are what many young families search for first. If you are going to really showcase any ministry in your church, you may want to start with kids.

FRESH - UP TO DATE – CONTENT. There is no worse reflection on your church than if your website is outdated and stale. Many large churches do not realize the importance of a good web ministry, while most small churches do. The problem is that the small churches cannot afford a full-time web person, and the large churches can “not” afford to “not” have one. Look for a website company that provides you with a simple way to edit and update your site. Most database driven website software allows for easy updates with only a few minutes of training. Don’t get caught in a situation where you cannot afford to update your site after the initial build.

Above are the list of things a church website should, what do you think a church website should have that is not listed here, Please feel free to comment it for others to learn.






Comments

  1. thanks very much. it is a wonderful post, i have been searching for it

    ReplyDelete

Post a Comment

Popular posts from this blog

Create a nigerian news blog -4- Homepage Customization Finalized

Laravel one to one relationship with example

  Laravel one to one relationship with example “Laravel eloquent one to one relationship with example”: A one-to-one relationship is a very basic, fundamental Laravel eloquent relationship. Following our  complete guide to Laravel relationships , it simply relates one entity to another. For instance, in our voting application, a User is associated with one Vote. If we were to describe this relationship, we could say: “ Each user has one vote”. READ THE UPDATED VERSION HERE   Defining a one-to-one relationship In order to define this relationship, we call the  hasOne  method on the entity that owns the relationship. Here’s a code snippet defining the relationship. <?php namespace App \ Models ; use Illuminate \ Database \ Eloquent \ Model ; class User extends Model { /** * Get's this user's vote */ public function vote () { return $this ->hasOne(App\Models\Vote::class); } } What happens here is, we pass the n...