How to Make a Church Website in 2026 (Step by Step)

Somebody handed you the church website. Maybe you volunteered, maybe you are the pastor and there was nobody else, and now there is a line on a meeting agenda with your name next to it.

Almost every guide on how to make a church website starts the same way: pick a platform. That is step four. The churches whose sites still look good three years later did the first three steps first, and not one of them involves a builder. We have been building church websites for years and audited hundreds more, so here is the order that actually works.

Start with the five things the site has to do

Before you touch a builder, name the job. For a church under a couple hundred people, the whole list is five items long.

Your service times and address, in plain text, visible without scrolling.
What to expect on Sunday, written for someone who has never been to church.
Your sermons, one or two clicks from the homepage.
A way for a guest to reach out that lands in front of a human.
Something that follows up when they do.

That is the whole thing. Not one of those is a five thousand dollar problem, and everything else people will suggest to you (a mobile app, a member portal, a page for every ministry) is optional. Write those five on a sticky note and put it on your monitor. Every decision from here gets measured against it.

Write the words before you touch a builder

Here is what nobody warns you about: most church websites do not look bad because of the design. They look bad because they are empty. A beautiful template with "Welcome! We are a church that loves God and loves people" in the hero is still a blank page wearing nice clothes.

So write the copy first, in a document, before you log into anything.

Give yourself 150 words for the homepage. Then write the "what to expect" paragraph, and take your time with it, because it is the most valuable copy on the entire site. What time does it actually start. How long does it actually go. What do people actually wear. Where do the kids go. Will anyone make a visitor stand up and introduce themselves. Answer the questions a nervous person is too embarrassed to ask.

Then get photos of your actual room. A phone in decent light beats every stock photo of a crowd worshipping in a building that is not yours. A guest is trying to picture themselves in your space, so show them your space.

Put the domain and the logins in the church’s name

This step takes twenty minutes and saves your church about a thousand dollars four years from now.

Buy the domain in an account that belongs to the church, using a church email address, on a payment method the church controls. Not the youth pastor’s personal Gmail. Not a volunteer’s credit card with auto-renew quietly running. yourchurch.org is fine, and .org still reads as church to most people.

Then write down, somewhere a future person will find it: where the domain is registered, who has that login, where the site is hosted, and who has that login. Keep it with the insurance paperwork, not in someone’s head.

The most common way a church website dies is not a hack or a crash. It is that the person who built it moved away and nobody has the key. The rescue quote for that runs eight hundred to fifteen hundred dollars, and every dollar of it pays someone to guess.

Now pick how your church website gets built

With the copy written and the domain in hand, this decision gets much easier, because you are no longer choosing a tool. You are choosing who does the work.

Do it yourself on a generic builder. Wix or Squarespace, $16 to $49 a month, and a genuinely good editor. You will assemble sermon pages and service-time layouts out of generic blocks yourself, and you own the upkeep forever. The right answer if you have a tech-comfortable person with real time.

Use a church platform. $39 to $250 a month depending on the platform and its add-ons, with the church-specific parts (sermons, events, giving links, follow-up) built in. The right answer for most churches under a couple hundred people. Watch the add-on math, because the advertised price and the real price are often different numbers. We ranked the builders churches actually shortlist.

Have someone build it for you. A freelancer at $2,000 to $8,000 up front, or an agency at $99 to $500 a month. The right answer when your church has real complexity, or when the honest truth is that nobody on staff should have to think about the website again.

Whichever way you lean, run the numbers before you commit. Here is what churches are actually paying in 2026, including the setup fees and add-ons that never make the pricing page.

Build six pages, not fourteen

Home. What to Expect. Sermons. Events. Give. Contact.

That is the site. A visitor with a question can reach the answer in one click from anywhere, which is the entire job of a menu.

The temptation is to give every ministry its own page, because every ministry leader will ask for one. Hold off. Eleven menu items on a church of ninety makes the site harder to use and hands you eleven pages to keep current, which in practice means eleven pages that go stale together. Put your ministries in one section on one page. If a ministry outgrows that, give it a page then, and you will be doing it because it earned one.

The pre-launch check that takes ten minutes

Run through this before you tell anyone the site is live.

Look at it on a phone, and look there first. Most of your visitors will never see the desktop version.
Submit your own contact form, then confirm the email arrived. Silent forms are the single most common broken thing we find on church sites, and nobody catches it, because a form that drops mail looks exactly like a form nobody used.
Read the homepage on a phone without scrolling. If the service time and the address are not both there, fix that before anything else.
Set page titles to your church and your town. "Home" is not a page title. "Grace Church | Middletown, CT" is.
Point your Google Business Profile at the new URL. More people will find you there than on any page you just built, which is why local SEO deserves an afternoon of its own.

The step that decides whether any of this worked

A website is not finished at launch. It is started. Two things decide whether the effort was worth it, and both happen after you are done celebrating.

Who updates it, and is it easy enough that they will? Not "could they, in theory, if someone showed them again." Church websites go stale for a boring reason: posting the sermon is a Monday task competing with real Monday tasks, and it loses every single week. The fix is not more discipline. It is making the update take ninety seconds, or making it happen on its own.

What happens to the guest who reaches out? Someone fills out your form on a Sunday afternoon. If that becomes an email sitting in an inbox until Tuesday, your site is a brochure. If it becomes a warm note that same day and a real follow-up over the next two weeks, your site is doing ministry. This is the piece almost every church skips, and it has the highest return of anything on this list.

Wrong service times cost you first-time visitors, which is the most expensive loss a church website can have and the only one that never shows up on an invoice.

Where we land

If you are a church plant or a church under about a hundred and fifty people: write the five things, write the copy, buy the domain in the church’s name, then get something real live this month. Do not spend six months designing.

If you are bigger, or your identity needs building rather than picking, or nobody on your staff should have to own this: have it built for you, and budget the year-two upkeep while you are at it.

We build both ends of that. Church Studio is our $39-a-month version with everything included and a 14-day trial, and our custom work starts at $295 a month. But the reason this guide leads with copy and domains instead of platforms is that those first three steps shape how the site turns out no matter who builds it. Do them in order and you will end up with a website your church can actually keep.

Photo by Chris Flaten on Pexels.