What should a church website have on it?
Start with the handful of pages people actually open: a first-time visitor usually wants one fact and gives up if it takes three clicks.
| Page | What goes on it | Who keeps it current |
|---|---|---|
| Home | This week's service times, the address, a Watch live button, one line about who you are | Office manager |
| Plan a visit | Parking, what to wear, children's ministry, access for wheelchairs, how long a service lasts | Welcome team |
| Watch | The live player, the next service time, past services | Media volunteer |
| Give | A short note on why, and a button to your giving provider | Treasurer |
| Events and news | Dated posts: dinners, youth nights, closures | Any trusted writer |
| Contact | Phone, a church email address, office hours, the pastor's name | Office manager |
Beliefs, history and staff photos can come later. Six current pages beat thirty pages showing last year's Christmas schedule.
Gather these five things first
- A domain name -- the address people type, such as yourchurch.org. You can register one here, and connecting it to your site takes a few plain steps.
- Hosting with WordPress -- the computer that stores your site and hands it out. WordPress itself recommends PHP 8.3 or newer, MariaDB 10.11 or MySQL 8.4 or newer, and HTTPS (the padlock in the browser).
- A giving provider -- the service your church already uses for online donations, or one your treasurer chooses.
- Two people who can log in -- never just one, in case a volunteer moves away.
- Photos you have permission to use, ideally of real Sundays rather than stock pictures.
Which hosting plan suits a church?
Most congregations fit on the smallest plan, and the WordPress versions save you the install. Our web hosting with WordPress set up for you comes with free SSL renewed for you, PHP 8.1 to 8.4 chosen per site (pick 8.3 or 8.4 to match the WordPress recommendation), mailboxes at your own domain, nightly backups free for the first 12 months, and weekly WordPress core updates. A domain is free for its first year on a term of 12 months or more.
- WordPress Simple Hosting -- one website and 25 GB of storage, 100 mailboxes. Right for a single congregation.
- WordPress Premium Hosting -- up to 10 websites, so a school, a youth group or a food bank can each have its own, plus a staging copy where you can try a new theme without touching the live site.
- Enterprise or Agency -- for a diocese, a network of parishes or a group of church plants that wants many sites under one account.
Every site sits behind Turbo, the page cache in front of our hosting servers, which keeps finished pages in memory. When the whole town looks up your Christmas Eve times at once, they get pages that are already waiting rather than a queue. The site never carries advertising, on any plan.
Set up the site, step by step
- Order a WordPress plan, then sign in to your new site's WordPress Dashboard (your site's address followed by /wp-admin). You should see the Dashboard with its menu down the left.
- Open Settings > General. Type your church's name into Site Title and a short line into Tagline, choose your city under Timezone, then click Save Changes.
- On the same screen, check that the Anyone can register box under Membership is not ticked. A church site rarely needs public sign-ups, and leaving it open invites spam accounts.
- Under Pages, create Home, Plan a visit, Watch, Give and Contact, plus an empty page called News. Publish each one.
- Open Settings > Reading, choose A static page under Your homepage displays, set Homepage to Home and Posts page to News, and save. Your front page is now fixed, and dated posts collect on News.
- Open Settings > Privacy and click Create New Page. WordPress opens a draft with suggestions; adapt it to what your church actually collects, then publish. WordPress says keeping it accurate is your responsibility.
- Add the new pages to your site's navigation menu, then open the site on your phone. You should see service times without scrolling.
Put your Sunday stream on the site
Your Watch page should play the service right there, with no app or sign-in. A live video channel takes the feed from OBS Studio, vMix, Wirecast, Larix or a hardware encoder and gives you an embeddable player without ads that works in any browser. The Free plan suits a small gathering of up to 10 viewers; Pro carries 1,000 viewers at once and adds a video library for past services.
- Copy the player's embed code from your channel's dashboard.
- Edit the Watch page, type
/htmlin an empty line and press Enter to add a Custom HTML block. - Click Edit HTML, paste the code, check the preview beside it, then click Update and publish the page.
WordPress only keeps embed code (an iframe) for users with the unfiltered_html capability: on an ordinary single-site install, Administrators and Editors; under Multisite, Super Admins alone. If an Author or Contributor pastes the player, WordPress strips it out when the page is saved. Have an Editor or Administrator place it once; it then stays put every week.
Two things to settle first. Music: CCLI says its Streaming License lets a church live stream or upload services, worship songs included, to its own website, so ask CCLI which licences your church needs. Bandwidth: read what upload speed a stream needs and test it from the sanctuary, not the office.
Giving and events without the headaches
The safest donation page is one that hands people to your giving provider's own secure checkout. Put a clear button on the Give page and in the menu, and never build your own form asking for card numbers: the provider handles payment, receipts and security.
For events, a dated post on the News page is often enough: title, date and time, place, who it is for, and how to sign up. If your calendar is busy, an events plugin adds a proper calendar view; choose one that is actively maintained, and delete it if you stop using it. Remove past events or let them drop off the page, so a visitor never turns up for last month's potluck.
Who updates what: roles for volunteers
WordPress gives every login a role, and picking the right one is how you let ten people help without anyone breaking the front page. Add people under Users and choose their role as you create each login.
| Role | What it can do | Give it to |
|---|---|---|
| Administrator | Everything: plugins, themes, users, settings | Two people, such as the pastor and one trusted volunteer |
| Editor | Publish and change any post or page, including other people's | The office manager who changes service times |
| Author | Publish and manage their own posts; cannot edit pages | Ministry leaders who share news |
| Contributor | Write posts but not publish them | Youth or teen writers, whose drafts an Editor checks |
A simple weekly routine keeps it alive: on Monday the office manager checks the front page times, the media volunteer adds the latest service, and anything older than a month comes off the News page.
Keeping the site safe and current
- Updates. WordPress plans get weekly core updates. For plugins, open Plugins and click Enable auto-updates beside each one; for a theme, use the same link in its details under Appearance > Themes.
- Fewer plugins. WordPress's own security guidance says to delete any plugin you are not using.
- Logins. Use the password strength meter, avoid the username admin, and turn on two-step sign-in for every Administrator.
- Backups. Nightly backups are free for the first 12 months; the panel restores a file, the database or the whole site from an earlier day. After that year backups become an add-on you choose, so decide before it ends.
- Photos. Give each meaningful picture a short description (alt text) for people using screen readers, and get permission from parents before posting children.
When a different tool serves you better
If your church wants a member directory, check-in for children and giving records all in one system, a dedicated church management service will do that better than a WordPress site, and you can still link to it from your menu. If no volunteer can spare an hour a week, choose fewer pages rather than a bigger site: an out-of-date site costs more trust than a short one.