A website for every congregation, under a shared identity

By the We.Inc editorial team · Updated · Editorial policy

Ask a denomination or diocese office about its congregations' websites and you hear the same story: a few excellent sites, many built years ago by a volunteer who has since moved, and some congregations with nothing but a social page. This page is about offering every congregation, mission and ministry a decent website under the shared identity, with a light touch from the regional office.

TL;DR

The volunteer problem, stated plainly

Congregation websites rarely fail for lack of money. They fail because one person knew how the site worked, and that person moved, retired or lost interest. The domain lapses, the service times are wrong, the "new here?" page describes a pastor who left three years ago. Visitors who look a church up before their first Sunday see that.

A shared platform fixes the volunteer problem in two ways: the site is built and edited in plain language, so the next volunteer can pick it up, and the regional office can see every congregation's site and step in when one goes stale.

Who is who

Denominational structures vary (dioceses and parishes, conferences and charges, presbyteries, associations of autonomous churches, planting networks). The mapping still follows one pattern:

Your structureWe.Inc role
Denominational, diocesan, conference or network officeBrand owner and admins
Communications staff who help congregationsTeam members, for example the designer preset (edit any site, no billing)
Congregation, parish, mission or church plantClient
Schools, camps, retreat centres, ministriesClients of their own, or additional sites under a congregation
The parish secretary, pastor or volunteerThe person signed in as the client

Where congregations are fully autonomous, as in many Baptist and congregational traditions, the office cannot require anything. The platform then works as an offer: a shared, good-looking option a church may choose, with the network's look and help.

Client register on a demo brand with tags, Active or Invited status, and a search box

*The register of every client. Tag congregations by deanery, district or region, and note the contact and review date.*

Add client form on a demo brand with email, name, company and plan fields

*Inviting a congregation. The invitation goes out in your name.*

What a congregation's site needs

A congregation site does not need to be large. The pages visitors look for, roughly in order:

  1. Service times and location, with parking and accessibility information.
  2. "Plan your visit" or "new here": what to expect, what to wear, children's arrangements.
  3. Who the clergy and staff are, with a way to contact them.
  4. Ministries and groups, with when and where they meet.
  5. Giving, linked to the congregation's own giving platform.
  6. Safeguarding or child-protection contact, where your denomination requires it.
  7. News and events.
Client dashboard on a demo brand host with a greeting, a prompt box and the client's website

*The congregation's home in your portal. A volunteer describes the church and the AI builds a first version.*

The client's editor on a demo brand host with a template site loaded

*Edits happen in this editor by clicking or asking in chat, so the next volunteer does not need the last one's know-how.*

Rules for launch and for links

Publication 1828, the IRS tax guide for churches and religious organisations, has a section on websites. It says that "a website is a form of communication" and that if an organisation posts something on its website that favours or opposes a candidate for public office, it "will be treated the same as if it distributed printed material, oral statements or broadcasts that favored or opposed a candidate." It also says an organisation that links to another site "is responsible for the consequences of establishing and maintaining that link", even without control over the linked content.

The rules on churches and political speech have been the subject of recent litigation: in 2025 the IRS agreed a proposed consent decree on how the rule applies to communications with a congregation, and in March 2026 a federal court dismissed that case without entering it. Your denomination's legal counsel is the right source for current guidance. *This page is general information, not legal or tax advice.*

Practical rules that fit the platform:

Brand-wide defaults titled What your clients can do, with switches including Publishing needs my approval

*Defaults for every congregation, including approval before publishing. Any switch can be changed for one congregation.*

Waiting for your approval queue showing one demo site with Approve and publish and Ask for changes

*A single-step approval by the office. (The request in this screenshot was staged for the picture.)*

Giving, prayer requests and personal information

Keep giving on the platform your congregations already use and link to it. Site forms are fine for "contact us" and "plan a visit". Think twice before collecting prayer requests, pastoral care needs or children's details through general web forms; that information is sensitive, and a pastoral care system or a phone call is often the better route.

Who pays

Denominations fund this in different ways: the office covers it as a shared service, congregations pay a contribution, or larger congregations pay and small ones are subsidised. If congregations pay, they can be billed under your brand through your own Stripe account, at prices you set.

Client billing page on a demo brand host saying access is provided by the demo brand

*What a congregation sees under billing: access provided by your office.*

When a congregation leaves

Congregations close, merge and sometimes leave a denomination. The website should not become part of the dispute. Agree the rule in advance: the congregation's own content is theirs to take, the shared name and look come off, and the site's full code can be downloaded or synced to the congregation's own GitHub. If the site sits on a subdomain of the denomination's domain, redirect it to a "find a church" page after the transition period.

Where We.Inc fits, and where it does not

Book a demo and bring three congregations: one with a good site, one with an outdated site and one with none.

Sources

Last checked 2026-10-25.

Book a demo. Pricing is tailored to your volume and setup, and you get your exact price on the call. 0% transaction fee.

Frequently asked questions

Can every congregation in our diocese or conference have its own website under our identity?

Yes. Your office is the brand owner and each congregation, school or ministry is a client with its own site and editors, under default rules your office sets.

Can the regional office check a congregation's site before it goes live?

Yes. Approval before publishing can be on by default and changed per congregation. It is a single approval step by your office.

Does a church website count as church communication for IRS purposes?

IRS Publication 1828 says a website is a form of communication and treats candidate content on it like printed material, and that links carry responsibility. Ask your denomination's counsel for current guidance.

Does it replace our church management software?

No. Membership, giving, check-in and scheduling stay in your existing systems. Congregation sites link to them.

Keep reading

More in White Label

We.Inc is an AI-powered website builder you can resell under your own brand. Launch a branded client dashboard, bill on Stripe Connect, and deliver AI-generated websites in minutes. White-label pricing is tailored to your volume and setup: book a 30-minute demo for a quote.

Product

Who It's For

Features

Resources

Company

View Sitemap