Ask most pastors when they last updated their church website and you'll get a wince. Not because they don't care — they care a great deal — but because updating it means digging up a password they wrote down two years ago, logging into a dashboard they barely understand, hunting for the right page, and then praying they don't break the whole thing trying to change a service time. So the Easter banner stays up until June. The bulletin says the old phone number. The "upcoming events" haven't been upcoming since last fall.
I'm a pastor, and I build websites for churches. I have watched this exact frustration play out so many times that I went looking for a better way — and the better way turned out to be simpler than anyone expected. You can now edit your church website by simply telling an AI what you want changed, in plain English, the same way you'd text a friend. No dashboard. No code. No fear. Let me show you how it works.
The old way versus the new way
The old way of running a website assumed you would become, in your spare time, a part-time web technician. You'd learn a content management system, remember where everything lived, and do the fiddly work of formatting and publishing yourself. For a busy shepherd with sermons to prepare and sheep to tend, that was never realistic.
The new way flips it around. Instead of you learning the software, the software finally learned to understand you. You open a chat — in a tool you may already use, like ChatGPT or Claude — and you say what you want:
"Change our Sunday service time to 10:30."
"Put this Sunday's sermon title on the homepage."
"Add our Vacation Bible School to the events page — June 23rd through 27th, 9 to noon."
And it's done. The change goes live on your real website, usually in about thirty seconds, and the AI tells you in plain words exactly what it changed. You can even speak the request out loud instead of typing it. That's the whole experience. Say it; it's done.
What's actually happening behind the scenes
I never want a pastor to feel like he's trusting a black box with his church's front door, so let me pull back the curtain. The plain-English version is this: a small piece of software acts as a bridge between your chat and your website. In the AI world it's called an MCP server — but you can just think of it as a translator. Here's the trip a single request takes:
- You send a message in ChatGPT or Claude: "Update the Sunday time to 10:30."
- The AI reads it and works out exactly what needs to change.
- The bridge turns that into a precise edit to your website's actual files.
- The change is recorded as a tracked version — a permanent, dated entry of what changed and why.
- Your site rebuilds and republishes itself automatically.
Total time from your message to a live update: about thirty seconds. Nothing is hidden, and nothing is improvised — the AI isn't "guessing" at a redesign of your site; it's making the specific, small change you asked for, and showing you the result.
A safety net that means you can't really break anything
This is the part that puts pastors at ease, so I want to dwell on it. The single biggest fear people have about editing their own site is breaking it. With this approach, that fear is largely answered by something called version history.
Every change — every word, every photo, every service time — is saved as its own recorded step. It's the same kind of tracking professional software engineers rely on, which means two things for you:
- You can undo anything. Don't like an edit? Just say "undo that," and your site rolls back to exactly how it was. Made three changes and want to return to this morning? That's fine too.
- You can see the whole story. What changed, when it changed, and what it was before — all there, plainly, like a logbook of your site.
So you are never one wrong click away from disaster. You're working with a net under you the whole time. For a pastor who has been burned before by a website he was afraid to touch, that safety net changes everything. It turns the website from a source of anxiety into something you actually feel free to keep current.
"What once took hours of work, technical knowledge, and often outside assistance can now be accomplished in just minutes. Updating pages, posting events, changing images — it allows us to focus more of our resources on ministry while keeping our website fresh and professional." — Pastor Mike Carrier, Bellingham Bible Baptist Church
A worked example, start to finish
Let's walk through a real, ordinary week so you can see how undramatic this is.
It's Thursday. You just finalized Sunday's message, "Finding Peace in Anxious Times," and you want it on the homepage. You also realized the contact page still lists the office number that changed in the spring. Here's the entire process:
You open your chat and type: "Put 'Finding Peace in Anxious Times' as this Sunday's sermon on the homepage, and update the office phone number on the contact page to 555-0142."
The AI reads it, makes both edits, and replies: "Done. I've set this Sunday's sermon to 'Finding Peace in Anxious Times' on the homepage and updated the office number to 555-0142 on the contact page. Both are live now."
You glance at your site on your phone. There it is. Total time: under a minute, most of which was typing the sentence. No login screen, no formatting, no "save as draft and preview." If you misspelled the sermon title, you just say so and it's fixed. If you decide the old number was right after all, you say "undo that."
That's the rhythm of it. The website stops being a project you have to set aside an afternoon for, and becomes something you tend in the spare two minutes between a hospital visit and a counseling appointment.
The things pastors ask me about most
"Do I need to be technical?" No. If you can describe what you want in a sentence, you can do this. The whole point is that the technical layer is handled for you.
"What does it cost to use the AI?" ChatGPT and Claude both have free plans that work for this. You're not buying expensive software to talk to your own website.
"Is this safe? Will the AI go rogue and rewrite my site?" It only makes the change you ask for, it tells you what it did, and you can undo anything. It is far safer than handing your password to a stranger or wrestling a dashboard at midnight.
"What happens if I want to leave?" This matters, and it's where a lot of website services quietly trap you. With the approach I build, you own your site, its files, and your domain. It all lives in your account. If you ever want to walk away, you take everything with you. No hostage situations, no "we own your content now." That's a matter of conscience for me as much as it is good business.
Why this is worth doing at all
It would be easy to treat all this as a novelty. It isn't. Your website is, for a great many of your neighbors, the first place they meet your church — long before they ever walk through the doors. The man awake at two in the morning, the family new to town, the widow looking for a place to belong: they look you up online first. If what they find is stale, half-finished, or wrong, that's the impression they carry.
When updating your site is genuinely easy, you keep it alive. The events are real events. The times are right. The sermon is this week's. And keeping it alive is no longer a tax on your ministry — it's a two-minute conversation. The technology, used rightly, simply gives you back hours that belong to the actual work of shepherding.
We are told to redeem the time (Ephesians 5:16). Anything that hands a pastor back his hours, without asking him to become something he isn't, is worth a careful look.
Pastor Eli builds modern, AI-assisted websites for churches — designed by a fellow pastor, with no agencies, no contracts, and no jargon. You can see how the AI editing works, and request a free demo, at AI-Assisted Church Website Design. More pastor-to-pastor writing on websites, outreach, and ministry is at elijahdesent.com.