A church website has one primary job: get a stranger through the door on Sunday. That means service times, the address, and what to expect must be findable in under ten seconds on a phone. Below is the full playbook: the seven sections a church site actually needs, the exact prompts that build each one (copy and paste them), what online giving really involves, an honest look at free website builders, and the questions church volunteers ask most.
Why most church websites fail the only person who needed them
I want you to picture somebody specific, because church websites get built for the wrong person almost every time.
It’s Saturday night. Somebody in your town has had a hard year. They’ve decided — tentatively, and they might change their mind by morning — that they’re going to try church tomorrow. They search, they land on your site, and they are looking for three things and nothing else: what time, where, and will I be the only one who doesn’t know anybody.
And what they usually find is a hero image of hands raised at a worship night, a scrolling banner about the building campaign, a pastor’s welcome letter, and a menu with eleven items. Service times are on a page called “Plan Your Visit,” two clicks in, and the address is in the footer in 11-point grey. Somewhere there’s a Christmas Eve service listed from two years ago.
Here’s the thing. That person is not shopping for doctrine at 9pm on a Saturday. They are trying to work out whether they can walk in without being embarrassed. Everything else on the site — the ministries, the sermons, the giving page — matters to people who already come. The homepage belongs to the one who doesn’t.
Most churches know this and still can’t fix it, for a reason that has nothing to do with theology: the site was built once, by a volunteer, in a free account, and that volunteer moved to Denver. Nobody has the login. So the wrong service time stays up, and every stranger who shows up at the wrong hour never comes back — and you never learn it happened.
Can AI really build a church website?
Yes — and the only skill it needs is the one your greeters already have: telling a newcomer plainly what happens and where to go. Designer Talk is an AI page builder that lets you build WordPress pages by describing them in plain English — no drag-and-drop, no design skills. You describe a section the way you’d say it out loud — “a section with our service times, the address, which door to use, and where to park” — and it appears in a live preview. Too formal? Say so. Want the times bigger? Say that. Each section is its own conversation.
What you end up with is a real WordPress site, on a domain the church owns, that any volunteer on the team can update in a sentence — which is the actual problem being solved here.
Get started with Designer Talk today and build along as you read — every prompt below is copy-paste, and the whole build is an afternoon.
“Your homepage belongs to the person who has never been. Everyone else already knows what time you start.”— Vincent Jordan
What should a church website include?
Not eleven menu items. Seven sections, in this order:
| # | Section | Why it matters for a church |
|---|---|---|
| 1 | Header with Service Times and Give | Two audiences in two buttons. The visitor needs the time; the member needs to give. Keep both on every scroll so neither has to hunt. |
| 2 | Hero saying who you are and when you meet | “A neighborhood church in south Springfield — Sundays at 9 and 11” beats a photo with no words on it. Say the name of the town. People search for church near me, and your site should read like it belongs to that map pin. |
| 3 | Service times, address, parking & which door | The single most-read block on any church site. Put the times in large type, the address as a real map link, where to park, and which entrance to use. This is the section that decides whether a nervous person walks in. |
| 4 | What to expect on your first visit | How long the service runs, what people wear, what happens with kids, whether anyone will make you stand up. Answering the “will I be embarrassed” question in plain words does more for attendance than any amount of design. |
| 5 | Giving | Members will look for this on a phone, mid-week. One obvious button to whatever giving platform you use, plus a plain sentence about other ways to give. Don’t make generosity a scavenger hunt. |
| 6 | Ministries, groups & kids | What actually exists, with real ages and real meeting times. Parents in particular are checking one thing: is there something for my seven-year-old, and is it safe and staffed. |
| 7 | Sermons, livestream & what’s coming up | Recent teaching for people deciding whether this is their kind of church, and a short list of upcoming events. Keep it current — a stale events list quietly tells people the church is stale too. |
That’s the whole site. One page, seven sections, and a stranger can find the door.
What a free church website actually costs
Let me deal with this honestly, because “free website for churches” is one of the most-searched things in this entire category, and I’m not going to pretend that isn’t a real budget question. Church money is somebody’s tithe. Spending it carefully is the right instinct.
So here’s the straight version. Some free options are genuinely free. Google Sites costs nothing, carries no ads, and will point at a domain you own. If your entire need is one page with service times and a map, that is a real answer and I’m not going to talk you out of it.
The free tiers on the big builders are a different animal. On Wix’s free plan you get their ads on your page and a yoursite.wixsite.com address, with a custom domain and ad removal starting on a paid tier — around $17/month billed annually at the time of writing. That shape is typical across the free plans: branded ads, a subdomain instead of your own address, storage caps.
And a subdomain is the part that quietly hurts a church, because a church address isn’t a link. It goes on the sign out front, in the bulletin, on the van, on a sticker on somebody’s water bottle. bellwoodchurch.org can move to any host on earth. bellwood.wixsite.com/home can’t move anywhere, and every place you printed it is now pointing at a company you don’t control.
But the real cost of the free build usually isn’t the ads or the address. It’s whose account it lives in. Free sites get built in a personal login — a volunteer’s, a college student’s, a staff member who’s since taken another call. When they leave, the site doesn’t come with them, and it doesn’t stay with you either. It just sits there, uneditable, with last year’s Christmas Eve time on it. I’ve watched that exact thing happen to more congregations than I can count.
Free isn’t a price. It’s a landlord. Sometimes a perfectly good one — but know which one you’ve got, and make sure the church, not a person, holds the keys. (That’s worth ten minutes on its own: see who actually owns your website.)
The exact prompts to type (copy and paste these)
These are real prompts, in build order, for a fictional congregation — Bellwood Community Church in Springfield, Missouri, two Sunday services, led by Pastor Ray Alcott. Swap in your church, your town, your times, and your ministries, and type them into Designer Talk one at a time. Your site won’t look like anyone else’s — the AI designs each section fresh — but it’ll match what you asked for.
Two things before you type the first one. First, open Brand Settings and set your colors and font once — every section after that comes out already matching, which is why none of these prompts mention colors. Second, photos never go in section prompts: the layout builds with placeholders. And for a church the photos should be your actual people and your actual room — more on that below.
create a header for Bellwood Community Church — links to Plan a Visit, Ministries, Sermons, and About, with the service times showing right in the header and a Give button on the right.
create a hero section for Bellwood Community Church in Springfield Missouri — headline A Neighborhood Church in South Springfield, a line that we gather Sundays at 9 and 11 and everyone is welcome exactly as they are, and two buttons, Plan Your Visit and Watch a Sermon.
Now the hero photo. The honest option here is a real one of your building or your room on a normal Sunday (+ → upload → Insert). If you don’t have a decent one yet, generate a placeholder of the space to hold the spot. Hit +, choose Generate Image, and describe it:
A simple bright church sanctuary with wooden chairs and morning light through tall windows, empty and calm, shot wide, no people.
It saves straight to your Media Library. Click Insert and tell the section “use this as the hero background.” Replace it with your own room as soon as someone takes a decent photo — a real congregation always beats a generated one, and a stock photo of a church that isn’t yours is a small lie a visitor notices the moment they walk in.
create a service times and location section — Sundays at 9 and 11 in large type, our address on South Campbell Avenue with a map, free parking in the lot behind the building, use the east entrance under the awning, and a note that services run about 70 minutes.
create a what to expect section for first time visitors — most people wear jeans, nobody will single you out or ask you to stand, coffee is in the lobby from 830, kids check in at the desk by the east door, and you can just slip out afterward if you would rather not talk to anyone.
create a giving section — a short line about why we give, one big Give Online button, and small text saying you can also give in person on Sunday or set up a recurring gift.
Point that button at whatever giving platform your church already uses. Worth knowing before you pick one: processing fees are real, they vary a lot between providers, and many platforms let the giver optionally cover the fee. That’s a treasurer conversation, not a website one — the site’s only job is to make the button easy to find.
create a ministries section with cards for Kids ages 0 to 11, Students grades 6 to 12 on Wednesdays at 630, Womens Bible study Tuesday mornings, and Mens breakfast the first Saturday — each with who it is for, when it meets, and who to contact.
create a sermons and events section — a spot for the most recent sermon video, a link to the full archive, and a short list of upcoming events with dates.
For photos throughout: use your own people, with permission, and be careful with pictures of children — most churches have a media policy for exactly this reason, and if yours doesn’t, this is a good week to write one. Never AI-generate a photo of “your congregation.” A visitor who recognizes nobody in the pictures has already learned something about how honest the site is.
Seven short prompts. Read them back — there’s nothing technical in a single one of them. And nothing is final: every section is a conversation, so when something isn’t right, you just say so:
Make the service times the biggest thing on the page.
Move What to Expect up above Ministries.
Add a line that we have a Spanish translation headset.
Two tips from watching a lot of these builds: put the service times in the header itself, not just in a section — it’s the one fact worth repeating twice. And give two people the login. Not one. The whole reason church sites go stale is that the person who could edit it moved away.
What does a church website cost in 2026?
| Option | Upfront cost | Ongoing cost | Time to launch | Who does the work |
|---|---|---|---|---|
| Web design agency | $2,500–$8,000 | $50–$200/mo maintenance | 4–8 weeks | Them — and every service-time change is a ticket |
| Church-website platform | Setup fee common | Monthly, forever | Days | Them, on their platform — leaving means starting over |
| Wix / Squarespace (paid) | $0 | $192–$588/yr, forever | Days–weeks | You, with drag-and-drop, on their platform |
| Free builder tier | $0 | $0 — paid in ads, a subdomain, and whose account it lives in | Hours | A volunteer — until that volunteer moves |
| AI page builder + WordPress hosting | A fraction of an agency build | Standard WordPress hosting | An afternoon | Anyone on the team, by describing what they want |
The honest comparison for a church isn’t really the money — most of these are affordable on a small budget. It’s who can change it on a Tuesday. A site nobody can edit is the most expensive one on this table, whatever it cost, because it will be wrong within a year and stay wrong.
Common questions
What should a church website include?
Service times, the address with a map, parking and which entrance to use, what to expect on a first visit, a giving button, your ministries with real meeting times, and recent sermons. In that order. Everything else is optional, and most of it is for people who already attend.
Can we just use a free website builder?
Sometimes, honestly, yes. Google Sites is genuinely free, has no ads, and works with a domain you own — if all you need is service times and a map, that’s a real option. The free tiers on the big builders are different: they place their ads on your page and give you a subdomain rather than your own address. The bigger issue with any free route is whose personal account it lives in.
Who should own the church’s website account?
The church, not a person — and at least two people should have the login. Register the domain to the church with a church email address, keep the hosting on a church account and a church card, and write the details somewhere the board can find them. Nearly every dead church website is dead for this reason and no other.
Do we need online giving on the site?
If you want gifts from anyone under about fifty, yes. Point one obvious button at whatever giving platform you already use rather than building something new. Processing fees are real and vary by provider, and many platforms let the giver choose to cover them — but that’s a decision for your treasurer, not a website feature.
Do we need to livestream?
Not necessarily, but you should post something people can watch before they visit. A recent sermon tells a cautious visitor more about whether they’ll fit than any “about our beliefs” page. If you already stream to Facebook or YouTube, just embed the latest one — there’s no need for separate streaming infrastructure.
What photos should we use?
Your own building, your own room, your own people — with permission, and following your media policy for children. A real photo of a plain room beats a beautiful stock photo of a church that isn’t yours, because the visitor is going to walk into the real one. Never AI-generate an image of your congregation.
Will it help people find us on Google?
It helps if the site plainly says what you are and where. Name the town in your headings — “a neighborhood church in south Springfield” is a real search. The builder includes an SEO optimization step that adds alt text, structures headings, and generates schema markup. Then claim your Google Business Profile and keep the service times accurate there too, because most “church near me” searches resolve in the map results first.
How long does this actually take?
Budget an afternoon: about an hour building and refining the seven sections, and the rest on the two things worth doing slowly — writing the “what to expect” section honestly, and getting a couple of real photos. Both matter more than anything visual on the page.
Build it before Sunday
The seven prompts above are the whole playbook. Copy them, put your real service times in the header, write the what-to-expect section the way you’d say it to someone standing nervously in the lobby, and give two people the keys. The site isn’t there to impress your congregation. It’s there for the person who drove past four times last month and hasn’t come in yet.
Seven prompts, real service times, and a first-visit section that answers the question nobody asks out loud — on a WordPress site the church owns.
Get Started Today