Being responsible for at least one web site, if not more, there are things you may not give much thought because they seem beyond your control, of little interest, or of any value to your users. Security usually falls in this category.

In spite of all that, anyone who maintains a site has the task of taking the initiative when it comes to security. If you don't, your visitors may find one day a new version of your site - a defaced one. Or, your host may suspend your account because a script on your site is causing a high server load. So, you have to do something.

Where do you start? Most of us will need guidance when it comes to security, server configuration and optimization. There is good news - help is readily available, if you ask for it! I spent some time reviewing the security notes for the different aspects of running a web site and spoke with a few people to get some useful tips to protect your investments of time and effort.

There are a variety of skills needed to build and maintain a church's web site - technical, editorial, graphical, planning, teaching and leading. Rare is the person who has all these skills AND has the time to devote to your church's web site. Clearly defining the roles and skills needed will help you build a team you need for your web ministry.

Millions of people are on the Internet every day - how do you get just some of them to visit your site? Here are some easy to follow guidelines for building your site to draw people to it. Start by looking at the URL, the title and the description of each page.

Search engines and users rely on you to provide information about your site's content - leverage your XOOPS meta tags and begin to improve your position on search engine results page (SERPs)

There are numerous web sites devoted to the technical, design aesthetics and usability aspects of web sites, but few help you with the editorial aspect (content) of your site. We start a discussion about what (and what not) to put on your church's web site.

One of the first features you will want to consider carefully for your church or ministry site is the ability to accept prayer requests. People everywhere have joys and concerns they can offer in prayer and your web site can be part of their prayer lives. The web offers global availability - 24 hours a day, 7 days a week. But, it will be up to you to connect with those people and their prayers.

In a post on Church Marketing Sucks, Brad Abare posted a series on producing church web sites that don't suck. Let's face it - it is just as easy to produce a web site that sucks as it is to create one that doesn't suck. Follow these tips so your site is good for more than just serving as a bad example.

Every web master needs a basic understanding of how the web works. Educate yourself about the fundamentals of Apache, PHP and MySQL and you will have a much easier time managing your site and a lot less frustration in maintaining it. The aim here is to introduce some of the common concepts of the three primary web applications supporting your web site.

As a web master, at some point you will undoubtedly begin to work on your search engine optimization, or think you need to work on optimizing your site for the search engines. Before you do, read this article and stop to think about who's more important - your readers or the robots?

The last thing you want is an ineffective web site. Your church web site must share your story and connect with your intended audience. To do this, you must determine who will build it and maintain it and what tools and resources they will need.

You also need to know what to look for when evaluating possible platforms for your church web site. Have a clear set of requirements ready as you look for your solution for an effective web site.