How Much Does a Parish Website Cost in the UK?

Parish websites vary enormously in cost — from nothing at all to several thousand pounds — depending on who builds them, what platform they run on, and what the site actually needs to do. If you’ve been asked to find out what a website for your parish would cost, or you’re wondering whether your current site represents good value, this guide walks through the real numbers.

The short answer

For a parish website in the UK, you should expect to pay somewhere in the following ranges:

None of these figures tells the whole story. The real question is not what the website costs to build — it’s what it costs to run, maintain, and keep accurate over several years.

What does a parish website actually need?

Before comparing costs, it’s worth being clear about what a functioning parish website has to do:

• Display Mass times and any changes to them
• List upcoming events and keep them current
• Publish a weekly bulletin or newsletter
• Provide contact details and a contact form
• Link to or integrate with an online giving platform
• Work well on mobile (the majority of your visitors)
• Be editable by non-technical volunteers
• Load quickly and securely (HTTPS)

Many parishes also need ChurchSuite integration, multilingual content for diverse communities, school or chaplaincy sections, and safeguarding policy pages. The more of these requirements you have, the more a generic off-the-shelf solution will frustrate you.

DIY website builders: free to £25/month

Platforms like Wix, Squarespace, and GoDaddy Website Builder let you get a site up quickly without any technical knowledge. Costs are low — often free at a basic tier, or £10–25 per month for a custom domain and additional features.

What you get: A good-looking site with a visual drag-and-drop editor. Easy for anyone to update.

What you don’t get: Any meaningful integration with ChurchSuite, a dedicated events module that understands recurring liturgical patterns, or the flexibility to build the site around your parish’s specific needs rather than generic templates. You’ll also find yourself fighting the platform whenever your content doesn’t fit neatly into its assumptions.

Hidden cost: The time your administrator spends workarounding platform limitations that were never designed for a parish.

Self-hosted WordPress with a theme: £500 – £2,000

WordPress powers roughly 40% of the web and there are themes designed specifically for churches. A technically confident parishioner can set up hosting (£5–15/month), install WordPress, buy a church theme (£40–100 one-off), and have something functional within a weekend.

What you get: A capable, flexible site with a large ecosystem of plugins. Broadly understood by developers if you ever need outside help.

What you don’t get: Out-of-the-box ChurchSuite integration. You’ll need a developer to build a custom connection to pull events or groups data from ChurchSuite’s API. The plugin ecosystem also creates ongoing cost: form plugins, SEO plugins, security plugins, caching plugins — individually inexpensive, collectively they add up, and each one needs updating.

Hidden costs: Hosting (£60–180/year), premium plugins (£50–200/year), developer time for ChurchSuite integration (£300–800), and the ongoing overhead of WordPress core and plugin updates. WordPress sites that aren’t actively maintained become security liabilities.

Agency-built WordPress site: £2,500 – £8,000+

A web agency will design and build a custom WordPress site to your brief. You get a professionally designed, properly configured site with content entered for you and usually a handover session for your team.

What you get: A site that looks and works exactly as specified, built by professionals, with proper testing across devices.

What you don’t get: An agency that necessarily understands parish life. Generic agencies build generic church websites. Requirements like ChurchSuite integration, term-aware event calendars, liturgical season handling, or multi-community structures are often treated as out-of-scope additions that push the quote higher. Ongoing support is usually charged separately, and rates vary significantly.

Hidden costs: Annual maintenance contracts (£300–1,200/year), plugin licence renewals, and the awkward reality that the agency who built the site is the only one who fully understands it.

Specialist parish CMS: £1,500 – £4,000 one-off

A CMS built specifically for parish and religious organisation websites — like Expanse CMS — costs more upfront than a DIY builder but considerably less than a bespoke agency build. The key difference is that the platform was designed for this exact use case from the start.

What you get: ChurchSuite integration built in — events pulled automatically from your ChurchSuite calendar with caching, featured event prioritisation, and multi-site support for multi-parish accounts. An admin interface shaped around parish content types rather than generic blog posts. Faster setup because the common parish patterns are already solved.

What you don’t get: The name recognition of WordPress or the flexibility of a fully bespoke build. If your requirements are unusual, you’ll need a conversation about what’s possible.

Ongoing costs: Hosting on a managed server (typically included or £10–20/month), no plugin licensing fees, and a developer relationship with someone who understands what a day of obligation is.

Hosting: the cost that catches parishes out

Whatever platform you choose, you need hosting. The differences matter:

Shared hosting (e.g. GoDaddy, Fasthosts): £3–10/month. Cheap but often slow and poorly configured for modern PHP. Support quality varies. Fine for a simple brochure site, unreliable for anything more demanding.

Managed WordPress hosting (e.g. Kinsta, WP Engine): £25–50/month. Fast, well-optimised, but expensive and tied to WordPress.

Managed server hosting (e.g. Laravel Forge on DigitalOcean or Hetzner): £15–30/month. A virtual private server managed via a server management platform gives you a properly configured, fast server that isn’t shared with hundreds of other sites. This is the infrastructure Expanse CMS runs on.

A parish site on cheap shared hosting that loads in 4 seconds will lose visitors. Core Web Vitals scores now affect Google rankings — a slow site is also a less-visible site.

Domain and email

A .org.uk or .co.uk domain costs £8–15/year. A .org costs £10–20/year. This is a trivial cost but don’t overlook it — parishes occasionally let domains lapse, losing their web address and email.

Parish email (e.g. [email protected]) is typically £3–6 per mailbox per month on Google Workspace or Microsoft 365, or free if managed through the hosting provider. Free email via hosting providers is functional but less reliable for deliverability.

Content migration

If you’re moving from an existing site, someone needs to migrate your content — pages, news posts, event history, images, documents. This is often underestimated.

A typical parish site might have 20–50 pages, several years of news posts, and a library of uploaded PDFs (bulletins, policies, safeguarding documents). Budget 4–12 hours of professional time for a content migration, or assign it to a volunteer with clear guidance on what needs to move and what can be left behind.

Ongoing maintenance: the cost that keeps going

All websites require maintenance. The relevant costs are:

Security updates: WordPress sites need core, theme, and plugin updates at least monthly. Neglected sites get compromised. Budget time or money for this — it’s not optional.

Content updates: Mass times change. Key contacts change. Events need adding. Someone needs to do this, and it needs to be easy enough that it actually gets done. A CMS with a poor admin interface creates content that goes stale.

Annual costs summary (ballpark):

What about free parish website schemes?

Some dioceses and Catholic bodies offer free or subsidised websites to parishes. These are worth investigating, but come with trade-offs: limited design flexibility, shared infrastructure, dependency on the diocese to maintain the platform, and sometimes slow response times when things go wrong. If your diocese offers something like this and the requirements are simple, it may be the right choice. If you need ChurchSuite integration, a distinctive identity, or the ability to move quickly on changes, a self-managed site will serve you better in the long run.

Getting the decision right

The cheapest option is rarely the cheapest in practice. A free website builder that costs your administrator two hours a week in manual workarounds costs the parish real time and goodwill. A poorly-maintained WordPress site that gets hacked and taken down during Holy Week costs far more than the developer time to keep it updated.

The right question is: what does this website need to do, and who will own it for the next five years?

If the answer is “a volunteer with limited technical knowledge needs to keep it accurate and it has to work with ChurchSuite”, that points strongly toward a purpose-built solution over a DIY builder or a generic agency WordPress site.

Expanse CMS is built specifically for parish and religious organisation websites, with ChurchSuite integration included as standard. Get in touch to discuss your parish’s requirements.