How to build a church website: the step-by-step process from first meeting to launch day

A working plan for pastors, church administrators and media teams, with a realistic timeline, a launch checklist and the roles that keep the site current after it goes live.

To build a church website, decide who the site is for and who will update it, choose a platform, register a domain in the church's name, write the core pages (home, plan your visit, sermons, give, events, about, contact), connect sermons, giving and forms, test it on phones and with a first-time guest, then launch and hand weekly updates to a named owner. A small or mid-size church can usually go from first meeting to launch in six to ten weeks when the content is gathered early. The steps below are the order we recommend, because doing them out of order is how church website projects stall.

If you are still deciding what your site should include or comparing builders against custom design and cost, start with our companion guide on church website design. This guide is the build process itself.

Step 1: Plan who the site serves and who will run it

Every good church web design starts with two lists, not a template.

The first list is your audiences, in order. For most congregations it looks like this: first-time guests checking service times on a phone, members looking for this week's sermon or event, people who want to give, and families checking children's ministry. Write the top three questions each group asks. Those questions become your navigation.

The second list is people. Name one site owner (the person accountable for the whole site), one person who posts sermons every week, and one person who approves anything that goes on the home page. Write the names down before you pick a platform, because the platform should fit the people who will use it.

Set two or three goals you can measure, such as more plan-your-visit form submissions, more recurring online gifts or more people watching sermons on the site instead of only on social media.

Step 2: Pick a platform that fits your team

You have three realistic paths:

  • A church website builder (Tithely, Nucleus, Ekklesia 360 and similar). Church-specific templates with sermon, event and giving tools built in. Best when a staff member or volunteer will run the site and your needs are standard.
  • A general builder or WordPress (Squarespace, Wix, WordPress). More design freedom; sermon libraries and giving are added through embeds or plugins.
  • A professionally designed site built by a church website designer. Best when you need a distinct identity, original photography and video, or a large content library such as years of sermons with transcripts.

Pick the platform and the giving provider at the same time. The giving form has to open in one tap from your "Give" button, and some builders bundle giving while others only link to it. Published builder pricing and design market ranges are compared in our church website design guide.

Step 3: Set up the domain, hosting, email and security

Choose the domain. Most churches use .org or .com. The .org extension is open to anyone, not only nonprofits, according to Public Interest Registry's FAQ, so a church can register one through any accredited registrar. Keep it short and easy to say from the pulpit: the church name, or the name plus the city if the plain name is taken.

Register it to the church. Use a church email address (an office or admin account), not a volunteer's personal Gmail. Turn on auto-renew and record the registrar login in the church's password manager. Domains lost when the one volunteer holding the login moves away are a painful and avoidable problem.

Use HTTPS from day one. Most builders include a security certificate. It matters more than ever: as of October 2026, Chrome asks users to approve the connection the first time they visit a public site that uses plain HTTP, per Google's Chrome security announcement. A guest who sees a warning on your home page may simply leave.

Set up church email on the domain (pastor@, office@, give@) so your website, receipts and Google profile all match.

Step 4: Map the pages and write the content

Content is the slowest part of any church website build. Start writing in week one, not after the design is done.

A practical page map for launch:

  1. Home: service times, address, "Plan your visit" button, this week's sermon, next events, Give.
  2. Plan your visit: parking, entrance, service length, what to wear, children's check-in, accessibility, what happens after.
  3. Sermons: the full library with search by series, scripture and speaker.
  4. Give: the giving form, funds explained, mailing address for checks.
  5. Events: a current calendar with registration where needed.
  6. About: beliefs, history, leadership and staff with real photos.
  7. Ministries: children, youth, adults, music, outreach, care.
  8. Contact: form, phone, office hours, prayer request.

Write for a guest who has never been inside a church building. Replace insider terms ("Narthex," "VBS," "the 8:30") with plain words, keep paragraphs short and put the answer first. Gather photos at the same time: one planned Sunday photo session can supply the home page image, plan-your-visit photos, ministry images and staff headshots. Get written permission from parents before any child's photo goes online.

Step 5: Set up sermons and media

  • One page per sermon with title, date, speaker, scripture, series and a short summary.
  • Video embedded from YouTube, Vimeo or your streaming platform, with audio for listeners on the go.
  • Transcripts or full notes under each message. They serve members who are deaf or hard of hearing and give search engines the full text of the sermon to index.
  • Series pages that group messages with the series artwork.
  • A "Watch live" page with the next service time and the stream embedded. Our church live streaming guide covers cameras, audio and platforms.

Decide on a weekly routine before launch: the sermon goes up by Monday at noon, with transcript, video and series tag. A library that stops at last spring tells guests the site is unattended.

Step 6: Connect giving, events and forms

Giving. Put a "Give" button in the header of every page. Test it on a phone with a real gift, including Apple Pay or Google Pay if your provider supports them, and test recurring giving. Add a short line about funds (tithes, offerings, missions, building) and the mailing address for checks.

Events. Use a calendar your team will actually update, ideally the same system that handles registration so nothing is entered twice. Archive past events automatically.

Forms. At minimum: plan your visit, contact, prayer request and new member interest. For every form, decide who receives it and how fast they answer. A guest who fills out "I'm visiting Sunday" and hears nothing has had a worse experience than no form at all.

Step 7: Build accessibility in, not on

Older members, visitors with low vision and people using screen readers all need to find service times and give. Build to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. In practice that means:

  • Color contrast of at least 4.5:1 for body text and 3:1 for large text, per WCAG's contrast criterion. Gold or light gray text on white usually fails.
  • Captions on prerecorded video, a Level A requirement under WCAG's captions criterion. Review auto-captions before publishing; names and scripture references often come out wrong.
  • Alt text that describes each meaningful image.
  • Labeled form fields, visible focus outlines and full keyboard navigation.
  • Text that enlarges without breaking the layout.

Test with a phone's built-in screen reader (VoiceOver on iPhone, TalkBack on Android) on the home page, the giving form and the plan-your-visit form before launch.

Step 8: Set up search, Google Business Profile and analytics

Google Business Profile. Claim and verify your church's profile so it appears in map results. Google chooses the verification method (video, phone or text, email, live video call or postcard), and review can take up to five business days, so start this in week one rather than launch week. Match the name, address and phone exactly to the website.

Google Search Console. Verify the site and submit your sitemap through the Sitemaps report, as described in Google's sitemap documentation. Most builders generate the sitemap for you.

Structured data. Mark up the church with the Schema.org Church type (address, phone, service schedule) and mark up public events. Google supports Event structured data, which requires at least the event name, start date and location.

Page titles. Give each page a title with the church name and city ("Plan Your Visit | [Church Name], [City]") and write one honest sentence describing the page for search results.

Analytics. Install a privacy-respecting analytics tool and decide which numbers you will review monthly: plan-your-visit submissions, giving page visits and sermon views.

A realistic church website timeline

This is the plan we use for a small to mid-size church with a builder or a professionally designed site. Large or multisite churches with many ministries and years of archived sermons should add time to weeks 3 through 6.

WeekPhaseWhat gets done
1PlanAudiences, goals, site owner named, domain and logins secured, Google Business Profile verification started
2Platform and contentPlatform and giving provider chosen, page map approved, content writing assigned
3PhotographySunday photo session, staff headshots, welcome video filmed
3 to 4DesignHome page and one inner page designed mobile first, colors checked for contrast
4 to 6BuildAll launch pages built, sermons imported, giving, forms and calendar connected
6 to 7TestPhone testing, screen reader checks, test gift, first-time guest test, broken link check
7 to 8LaunchDomain pointed, HTTPS confirmed, sitemap submitted, announced from the pulpit and on social media
9 and onMaintainWeekly sermon and event updates, monthly review of forms and analytics

Content is what pushes projects past ten weeks, so give every piece a person and a due date in week two.

Church website launch checklist

Run this list the week before launch, on a phone first and then on a laptop.

CheckDone when
Service times and addressVisible on the home page without scrolling on a phone
Plan your visitParking, entrance, kids check-in and accessibility answered; form tested and someone receives it
GivingTest gift completed on a phone, recurring option works, receipt arrives
SermonsLatest message posted with video, audio, transcript and series tag
EventsOnly upcoming events showing; registration tested
FormsEvery form delivers to a named person; confirmation message shows
AccessibilityContrast passes, images have alt text, videos captioned, keyboard navigation works
SpeedHome page loads quickly on a cellular connection; large photos compressed
SecurityHTTPS on every page, no browser warnings
Domain and loginsRegistered to the church, auto-renew on, logins in the church password manager
SearchSearch Console verified, sitemap submitted, page titles written, Google profile linked to site
LinksNo broken links, social icons point to the right accounts
Old siteOld page addresses redirected to the new ones so search traffic and bookmarks still work
Guest testSomeone who has never attended found service time, parking and kids check-in on their own

Who maintains the site after launch

A church website stays useful when the work is divided into small, regular jobs with names on them.

RoleResponsibilityRhythm
Site ownerFinal say on home page, renewals, logins, vendor contactMonthly review
Sermon publisherVideo, audio, transcript, series tagEvery week
Events editorAdd, update and archive eventsEvery week
Form responderAnswer visit, prayer and contact formsWithin one business day
Pastor or approverReview new pages and announcementsAs needed

Put the weekly tasks on the staff calendar. Review the whole site each quarter: refresh the home page photo, update staff, check every form and remove anything out of date. Your church social media and a church app, if you have one, should point back to the website so it remains the single source of truth.

How to choose a church website designer

If you hire a church website designer or a Christian website design firm, ask to see live church sites they built, not just mockups, and open them on your phone. Then ask:

  • Who owns the domain, the site and the content when the project ends?
  • Which platform will we be on, and can our staff update it without calling you?
  • Who writes the content, and who takes the photos and video?
  • How do you handle sermons, transcripts and giving integration?
  • Do you build to WCAG 2.2 AA, and how do you test it?
  • What happens after launch: training, support and who to call when something breaks?

Strong answers include original photography of your congregation and staff training at handoff.

Frequently asked questions

How much does it cost to build a website for a church?

Church website builders charge a monthly fee; Tithely Websites, for example, lists $19 a month on its pricing page. For professional help, Thumbtack's national data puts a typical website developer project at $614 to $1,817, averaging $1,057, per Thumbtack. Custom builds for large churches cost considerably more; our church website design guide lists published market ranges.

How can I create a church website for free?

Some general builders offer free plans. Wix's free plan includes Wix branding and a wixsite.com address, and connecting your own domain requires a paid plan. Tithely offers free online giving with standard processing fees, but its website product is paid. For a church, owning your domain and removing another company's branding is worth a modest monthly fee.

What website domain should a church use?

Most churches use .org or .com. The .org extension is open to anyone, per Public Interest Registry. Choose a short name members can say from memory, register it in the church's name with a church email address, and turn on auto-renew.

How do you design a website for a church?

Start with your audiences and their top questions, map the pages around those questions, write the content, then design mobile first with real photos of your congregation. Put service times, address and a plan-your-visit button at the top of the home page, and keep navigation to a handful of clear items.

What does a church website need?

Service times and address on the home page, a plan-your-visit page, a sermon library, online giving, a current events calendar, beliefs and staff, ministries and contact forms. Accessibility, HTTPS and a verified Google Business Profile belong on the list too.

What is the 80% rule for churches?

The 80% rule is a church growth rule of thumb that a worship space feels full at about 80 percent of capacity. Influence Magazine describes it as the point when it is time to add a service, and notes it applies to the whole facility, including children's areas and parking. When you add a service, update the website, Google profile and plan-your-visit page the same week.

How long does it take to build a church website?

For a small to mid-size church, six to ten weeks from first meeting to launch is a realistic plan when content is assigned early. Large or multisite churches with extensive sermon archives take longer.

How Leo Operations approaches this

Leo Operations is a national video production and photography company headquartered in Nashville, and we build church websites as part of a full media operation. We built the new website for St. Andrew's Presbyterian Church in North Nashville with service times, weekly sermons with transcripts, events and a plan-your-visit page. Our church work also includes films, weekly vertical sermon clips and service graphics for Cathedral of Praise, and photography for congregations including First Baptist Church Capitol Hill, Allen Chapel AME and Mount Bethlehem Baptist. Our design team, led by Partner and Creative Director Morganne Norwood, produces church media, so the photos, video and graphics on your site are original to your congregation.

We start with a planning conversation about who you want to welcome and what your team can maintain, then follow the process in this guide: content first, mobile-first design, accessibility built in, and clear roles at handoff. If your church is planning a new website, email us your church, your current site and your target launch date, and we will tell you honestly what it takes. See our church work and website design services.

Keep reading
Work with us
From our work
Start a project

Ready towin?

Tell us what you’re running for, building or launching. We’ll tell you how we make people remember it.

Email Leo Operations →