Message

Error
  • JFile::read: Unable to open file: 'http://tinyurl.com/api-create.php?url=http://ivmwebsolutions.com/does-your-church-website-work.html'

Warning: fopen(http://tinyurl.com/api-create.php?url=http://ivmwebsolutions.com/does-your-church-website-work.html) [function.fopen]: failed to open stream: HTTP request failed! in /home/content/I/V/M/IVMROB/html/IVMWEBSOLUTIONS/libraries/joomla/filesystem/file.php on line 240
Does Your Church Website Work?
Written by Rob McBryde   
Friday, 07 August 2009 15:26

The Gospel and the World Wide Web

 

In my humble opinion, church websites are among the most important on the web. They have the potential to extend the reach of the Gospel throughout your city as well as around the world.

Your church website can and should be taking advantage of online calendars, downloadable audio or video sermons (podcasts), and ministry updates. This info should be updated regularly so visitors have a reason to return. If the website remains static, people will realize this and not come back.

Beyond staying updated, your website should allow for interactions between you, your church members and those outside of your church. Consider the popularity of Facebook and Twitter. It's the interactions that make these websites interesting.

 

CASE STUDY: A few months ago, I webcasted a special event for The River Church from a restaurant. On the web you could see and hear the discussion and interact through a chat room on the website. It wasn't an extravagant production, but it resulted in someone connecting with the church. That was in May. The woman, who previously was not attending church, has been attending The River Church ever since and is involved in a weekly small group. I've heard her testify about new found hope and seen transformation happening in her life.

Is your church website connecting with people?


Written on Friday, 07 August 2009 15:26 by Rob McBryde

Viewed 1055 times so far.
Like this? Tweet it to your followers!

Rate this article

(0 votes)
blog comments powered by Disqus