Most church websites don't fail because they look bad when they launch. They fail a year later, when the "latest news" section still shows last Christmas's carol service and the vicar listed left eighteen months ago. Nobody planned for that. It just happens, quietly, because updating the site turned out to be harder than anyone expected.
Most church websites are built on a content management system: a login, an editor, a dashboard. That's fine in theory. In practice, the one volunteer who understood it moves away, or stops having the time, and updating the site becomes a job nobody wants and nobody's sure how to do. The site keeps existing. It just stops being current.
Removing the login, not adding a better one. A hand-built site has nothing to log into, so there's no system for a volunteer to learn and nothing to hand over when they step back. Instead, whoever has the news — a churchwarden, the vicar, whoever's organising the fete — sends it to me directly, and I build and publish it myself.
Every sponsored site gets a weekly update round: send through whatever's happened during the week, and it's built and published on a weekly cycle. There's no cap on how much you can send, and no charge for sending more. See Keeping Your Site Current for exactly how that works.
For a benefice, the same principle solves a second problem: several churches sharing one site, each with someone different looking after their own news. Rather than everything funnelling through one overworked webmaster, whoever looks after each church can send updates for their own section directly. See Groups & Benefices.
A website stays current when updating it takes one message, not a login. That's the entire idea behind how this service works, and it's free for the church either way.
Free for your church, every time — sponsors cover the cost, weekly updates included.
Get Started