// Guide · 26 min read · Updated July 2026
Church Website
The 2026 blueprint for a church website that actually converts guests, ranks in Google + AI answer engines, and reflects the church you actually are. Pages, platforms, plan-a- visit, sermons, SEO, performance, analytics, and maintenance.
// In this guide
- 01.What a church website is actually for
- 02.The 10-minute homepage audit
- 03.The 10 pages every church needs
- 04.Choosing your platform
- 05.Homepage architecture
- 06.The plan-a-visit page
- 07.The sermon library
- 08.SEO + AI optimization
- 09.Performance + accessibility
- 10.Analytics that matter
- 11.The maintenance rhythm
- 12.When to redesign
- 13.FAQ
What a church website is actually for
Hint: it isn't your congregation.
The primary user of your church website is the guest who has never been there. Your existing congregation already knows the service times, the address, the parking, and the vibe. They aren't the audience the site needs to serve — and every decision the site makes for them at the expense of the guest is a step in the wrong direction.
The website has three jobs, in this order: (1) help a stranger become a guest, (2) help a guest become a returning attender, (3) help an attender become a rooted, giving, serving, sending part of the church body. Everything on the site should ladder to one of those three jobs. If a page doesn't, it's noise.
The AI-search era changes this only slightly. The primary user of your website is now split between the human guest and the AI answer engine that will summarize your church to that guest before they ever visit the site. Structure content so it works for both — semantic HTML, structured data, answer-first copy patterns. See the AI Search Optimization guide for depth.
Build the site for the guest you don't yet know, not the member who's been there twenty years. The member won't leave over a slightly modernized site. The guest will leave over a confusing one.
// Diagnostic
The 10-minute homepage audit
Grab your phone. Open your homepage on 4G, not wifi. Run these 8 questions. Score yourself honestly. If you fail 3 or more, the site needs work now, not next year.
Check 01
Can I find your service times in under 3 seconds?
Passing: Yes, above the fold on the homepage.
Failing: Buried in a submenu, in a graphic, or (fatal) missing entirely.
Check 02
Can I plan a visit in under 60 seconds?
Passing: Clear CTA, dedicated page, short form, auto-response.
Failing: Contact form, phone call required, or 8-field intake.
Check 03
Does the homepage load in under 2 seconds on mobile?
Passing: Compressed images, minimal scripts, fast hosting.
Failing: 5MB hero video autoplay, 12 fonts, uncompressed PNGs.
Check 04
Can a parent immediately see kids-ministry info?
Passing: Kids link in top nav or homepage above the fold.
Failing: Kids info hidden inside 'ministries' → 'family' → 'children.'
Check 05
Is your latest sermon accessible in one click?
Passing: Sermons link in top nav, latest sermon featured on home.
Failing: 'Media' → 'Watch' → 'Archives' → search.
Check 06
Does the site work on a phone in landscape?
Passing: Responsive layout at every breakpoint.
Failing: Broken on iPad, or requires horizontal scrolling on iPhone.
Check 07
Are your beliefs findable and honest?
Passing: Beliefs page linked from About, plainly written, complete.
Failing: Generic statements copied from a template site.
Check 08
Are your staff photos current (past 24 months)?
Passing: Yes, all named staff with real photos + short bios.
Failing: Missing photos, headshots from 2015, or no staff page at all.
The 10 pages every church needs
The minimum. Nothing beyond these ten unless a real audience actively searches for it. Every extra page dilutes the important ones and adds maintenance debt.
Home
Must include: Church name, city, service times, primary CTA (Plan a Visit), this week's series, sermons link, kids info, next-steps section.
Plan a Visit
Must include: Answers the 7 guest questions. Short form. Auto-confirm. Parking + entry directions. Photo of the actual building.
Sermons
Must include: Filterable library. Latest sermon featured. Video + audio + notes + scripture + series link on each. Structured schema.
About + Beliefs
Must include: Story of the church, lead pastor bio, staff, elders, honest and complete statement of beliefs.
Kids
Must include: Age ranges, security process, sample curriculum, drop-off flow with photos, allergy handling, first-visit walk-through.
Students
Must include: Middle school + high school schedules, ministry leaders, sample events, parent-facing FAQs, sign-up.
Groups
Must include: Group-finder tool or list. What to expect. Meeting formats. How to lead. Contact for questions.
Give
Must include: One primary method (recurring). Backup methods (text, mail, app). Impact story. Transparent fund allocation. Tax info.
Contact
Must include: Address (map embed), phone, email, staff contact by role, office hours, pastoral care contact separate from general inquiries.
Events
Must include: Upcoming events list. One page per event with Event schema. Add-to-calendar. Registration or details CTA on each.
Choosing your platform
Six candidates. Match to church size, technical capacity, and long-term ambition. The wrong platform tax is real — a bad platform choice costs 3–5× the platform fee in wasted staff hours over its lifetime.
| Platform | Best for | Worst for | Cost |
|---|---|---|---|
| Squarespace | Small to mid churches. Non-technical admin. Fast build, decent SEO, great templates. | Complex custom features. High-volume dynamic content. Very custom design. | $25–65/month |
| Webflow | Design-forward churches with a savvy admin. Custom design + strong SEO + good CMS. | Non-technical admin (steeper learning curve). Complex user-account flows. | $25–75/month + designer |
| WordPress | High-volume content publishing, blog-heavy churches, complex custom needs. | Non-technical admin (maintenance burden). Vulnerable to plugin bloat + security issues. | $15–50/month hosting + dev |
| Wix | Very small church plants prioritizing speed to launch over long-term flexibility. | Anything mid-size or growing. SEO ceiling. Design ceiling. Migration difficulty. | $17–36/month |
| Custom (React/Next/TanStack) | Very large churches with in-house engineering. Highly custom digital experiences. | Any church that doesn't have a dedicated developer. Over-engineering is the default failure mode. | $40k–200k+ build + $20k+/year maintenance |
| Church-specific CMS (Ekklesia360, Sharefaith, etc.) | Rarely. Sometimes works for churches with very specific denominational needs. | Most cases. Poor SEO history, locked-in data, template ceiling, above-market pricing. | $100–500/month |
Homepage architecture
Eight sections, in order. Nothing more. Every section earns its place.
1. Hero (above the fold)
Church name + city + service times + primary CTA. That's it. No 10-slide carousel. No 90-second autoplay video. A single, still, on-brand image. One button.
2. This week (below the fold)
Current sermon series graphic + one-line 'what we're studying right now' + link to sermons. Answers: 'if I came this Sunday, what would I hear?'
3. First-time guest strip
Second CTA for Plan a Visit + 3 quick reassurances (kids, service length, dress code). Short. Confident. No apologies.
4. Ministries at a glance
3–6 tiles: Kids, Students, Groups, Serving, Next Steps, Give. Each links to its section. No 12-tile grid that overwhelms.
5. Story / testimony
One short story of transformation. Real person, real photo, real name. This is where the church becomes real to a stranger.
6. Upcoming events (dynamic)
Next 3 events, pulled live from the events CMS. Update automatically as events pass. Never stale.
7. About-in-brief
One paragraph on who the church is + link to full About page. Not the mission statement — the human introduction.
8. Footer
Address, service times (again), contact, staff, social, legal. This is the fallback for anyone who scrolled past everything else.
The plan-a-visit page
The most important page on the site after the homepage. Answers the seven questions every first-time guest asks — then makes it stupid-easy to submit a name + email. Convert-rate benchmark: 25–45% of page visitors submit the form.
The 7 questions every guest asks
- 01.What time does service start (and end)?
- 02.Where exactly is the building — and where do I park?
- 03.What do I wear?
- 04.What about my kids — where do they go, is it safe, what's the age range?
- 05.How long is service?
- 06.Do I have to sign in or introduce myself?
- 07.What happens if I don't know anyone?
The form: name, email, service time, kids' ages. Four fields max. Anything more, conversion drops.
The auto-response: immediate. Confirms the service time. Includes address + parking link + entry instructions + a photo of the building so they know what to look for. Names the person who'll greet them.
The follow-up: a real human sends a personal text or email 48 hours before the service, and a real human follows up on Monday. See the church email marketing guide for the guest sequence.
The sermon library
Usually the second-most-visited section after Plan a Visit. Also the largest compounding SEO asset most churches have — and the one most churches waste. Five parts.
The library page
Filterable by series, topic, speaker, scripture, year. Search bar. Latest sermon featured at top. Grid of thumbnails below. Pagination or infinite scroll.
The series page
One page per series with hero graphic, series description, list of sermons in the series, small-group discussion guide download.
The sermon detail page
Video embed (YouTube or Vimeo, lazy-loaded). Audio player. Sermon title, date, speaker, scripture, series link. Transcript (full text, for SEO + accessibility). Sermon notes PDF. Share buttons. Discussion questions.
The schema
SermonEpisode, VideoObject, and CreativeWork schema on every sermon page. AudioObject for the audio version. This is how AI answer engines and Google Video results discover and cite sermons.
The repurpose engine
Every sermon should output ~5 pieces of content: full video, audio podcast, transcript blog post, short-form clips for social, quote graphic. See the content strategy guide for the workflow.
SEO + AI optimization
Five layers. Miss any one, and everything above it gets capped. Full detail lives in the SEO guide, AI Search Optimization guide, and Answer Engine Optimization guide — below is the summary applied specifically to your website.
Local SEO
Google Business Profile 100% complete. LocalBusiness schema on the site. NAP (name, address, phone) consistent across every mention on the internet. City name in title, H1, and body copy of the homepage.
Technical SEO
HTTPS. Mobile-first. Fast (Core Web Vitals all green). Semantic HTML. sitemap.xml. robots.txt. Canonical tags. Structured data on every content page. No JS-only navigation.
Content SEO
Pages for the questions your community actually searches: 'churches near me,' '[city] churches with kids programs,' '[denomination] church [city],' '[pastor name],' plus topical resources tied to sermon themes.
Sermon SEO
Each sermon a unique page with transcript, schema, and internal links. Sermons are the largest compounding SEO asset most churches have and the one most churches waste.
AI + Answer Engine Optimization
Structured content that answer engines can quote: FAQ schema, clear entities, semantic HTML, answer-first copy patterns, About pages with real biographical schema. See the AI Search Optimization guide.
Performance + accessibility
Six baseline standards. Fail any of these and you're capping every other investment on the site.
Core Web Vitals — all green
LCP under 2.5s, INP under 200ms, CLS under 0.1. Test with PageSpeed Insights. Failing here caps every other SEO effort.
Images optimized
Every image compressed, next-gen format (WebP or AVIF), lazy-loaded, appropriately sized. Images are the #1 source of slow church sites.
Fonts minimal
Two font families max. Self-hosted or from a fast CDN. font-display: swap. Avoid loading 12 font weights.
Scripts minimal
One analytics script. One embed script (video). Kill everything else. Every plugin/tracker adds load time and privacy risk.
Accessible (WCAG 2.1 AA)
Alt text on every image. Semantic HTML. Color contrast 4.5:1+. Keyboard navigation. Captioned videos. No color-only communication.
Mobile-first everything
Design for iPhone SE first, expand up. Test on real devices, not just browser DevTools. 70%+ of traffic is mobile.
Analytics that matter
Six metrics. Track them monthly. Everything else is noise or a leading indicator of one of these six. Use GA4 or Plausible.
| Metric | Healthy target | Why it matters |
|---|---|---|
| Plan-a-Visit conversion rate | 25–45% of Plan-a-Visit page visitors submit the form | The single best proxy for whether your website is doing its primary job. |
| Sermon plays | Track weekly. Trend matters more than absolute number. | Sermons are your most-consumed content. Plays declining = brand energy declining. |
| Give-page conversion rate | 10–20% of Give page visitors complete a gift | Below 10% signals friction (too many steps, unclear amounts, mobile broken). |
| Homepage bounce rate | Under 55% for a healthy homepage | Above 65% signals a message-audience mismatch or a page-load problem. |
| Mobile vs desktop split | 70/30 mobile/desktop typical | Confirms mobile-first is the right investment prioritization. |
| Top landing pages | Home, Plan a Visit, sermons, staff bios usually top | If evergreen pages don't appear, your discovery mix is unbalanced. |
The maintenance rhythm
Websites decay without a scheduled cadence. Assign one named owner. Block the calendar. Below: the sustainable rhythm most church teams can hold long-term.
Weekly (30 min)
Publish new sermon. Update events. Rotate homepage graphics if series changed. Verify all forms working. Check GA4 for anomalies.
Monthly (2 hours)
Retire expired events. Update staff/leadership changes. Check for broken links (Screaming Frog free scan). Review top 10 pages for freshness. Check Core Web Vitals.
Quarterly (half day)
Full site audit vs. audit checklist. Update seasonal content (Back-to-school, Easter, Christmas prep). Review analytics trends. Update Google Business Profile.
Annually (1–2 days)
Visual refresh review. Content audit — retire dead pages. Reassess platform fit. Update About page + staff pages. Review site speed + accessibility comprehensively.
When to redesign
Six triggers. Any one is a strong signal. Any three simultaneously = redesign this year, not next.
It's been 4+ years since structural rebuild
Design language shifts every 3–4 years. A 5-year-old site signals to guests that the church may not be current.
Mobile experience is broken
If the site was built pre-2020 and hasn't been refactored for mobile-first, it likely fails on modern iPhones/Android. Fix now — 70%+ of your traffic is mobile.
You can't publish a sermon in under 15 minutes
Sermon publishing friction kills the content strategy. If the CMS is fighting you every week, the platform is wrong.
Analytics show consistent bounce > 65% on homepage
A high-bounce homepage is a message-audience mismatch or a page-load problem. Either is a strong signal for redesign.
Site fails accessibility or Core Web Vitals
These aren't nice-to-haves. Failing accessibility is a legal risk; failing Core Web Vitals caps SEO. Rebuild.
Church has evolved but site hasn't
New senior pastor, changed vision, new campuses, refreshed brand — the site must reflect the current church, not a previous era.
Frequently asked questions
What makes a great church website in 2026?+
Six things: (1) A guest can plan a visit in under 60 seconds. (2) Every page loads in under 2 seconds on mobile. (3) Sermons, service times, and location are visible without scrolling on the homepage. (4) The content is structured for AI answer engines (schema, semantic HTML, clear entities). (5) Kids and youth ministry pages honestly answer parent anxieties. (6) It reflects the actual voice, aesthetic, and personality of the church — not a generic template.
What pages does a church website absolutely need?+
Home, Plan a Visit, Sermons, About/Beliefs, Kids, Students, Groups, Give, Contact, and Events. That's the minimum ten. Anything beyond that should exist because a specific real audience actively searches for it, not because the CMS made it easy to add. Every extra page dilutes the important ones and adds maintenance debt.
How much should a church spend on its website?+
Build cost: $8k–40k depending on scope and platform. Ongoing: $1k–4k per year for hosting, domain, plugins, and small updates. Redesign cadence: every 4–6 years for structural refresh, every 2–3 years for visual refresh. Websites that skip redesigns for a decade are almost always the reason a church loses relevance online — not the ad budget.
What platform should a church use for its website?+
For most churches: Squarespace (best default — easy, decent SEO, great templates), Webflow (best for design-forward churches with a savvy admin), or WordPress (best for high-volume content publishers). For very small plants: Wix or Squarespace. Avoid: custom-built React apps (over-engineered), Church-specific CMS (locked-in, poor SEO history), or anything with 'church.com' in the URL.
Do church websites need to be optimized for mobile?+
Yes — over 70% of church website traffic is mobile, and often 80%+ of first-time-guest traffic. Mobile-first is not optional. The homepage must load in under 2 seconds on a 4G connection, buttons must be tappable without zooming, and the plan-a-visit flow must complete in fewer than 5 taps on a phone.
What should be on a church homepage?+
Above the fold: church name, city, service times, one primary CTA (usually 'Plan a Visit'). Below the fold, in order: this Sunday's series/message, sermons link, kids/families info, groups/next-steps, giving, upcoming events, and a brief 'about' section. Never bury service times in a submenu. Never require guests to hunt for the address.
How do we design a plan-a-visit page that actually converts?+
Answer the seven questions every first-time guest asks: What time? Where? What do I wear? What about my kids? How long is service? Do I have to sign in? What happens if I don't know anyone? Then a single form: name, email, service time, kids' ages. Nothing else. Auto-send a confirmation with parking + entry instructions. Convert rate benchmark: 25–45% of visitors to the page should submit the form.
How do we optimize a church website for SEO?+
Five layers: (1) Local SEO — Google Business Profile claimed and complete, LocalBusiness schema on the site. (2) Technical SEO — fast, mobile-first, semantic HTML, sitemap.xml, robots.txt. (3) Content SEO — pages for the questions your community actually searches. (4) Sermon SEO — every sermon is a page with transcript, schema, and share assets. (5) AI/answer engine optimization — content structured to be quoted by ChatGPT, Claude, Perplexity, Google AI Overviews. See the church SEO guide for full detail.
Should church websites have a sermon library?+
Yes, and it's usually the second-most-visited section after Plan a Visit. Best practice: each sermon gets its own URL, video embed, audio, transcript, series page, scripture references, and structured schema. Aggregate view for seekers who don't yet know the pastor. Filter by series, topic, scripture. Compounding SEO asset over time.
How should a church website handle events?+
One events page with all upcoming events, one detail page per event, structured Event schema for each, one-click 'add to calendar,' registration or 'more info' CTA on every event. Retire events after they happen — don't leave the January 2024 Vision Sunday page live in November 2025. Old events kill site trust.
How do we make a church website accessible?+
Follow WCAG 2.1 AA at minimum. Alt text on every image, semantic HTML (real headings, real buttons), color contrast 4.5:1 or higher, keyboard-navigable, captioned videos, no reliance on color alone to convey information. Accessibility is both a legal risk mitigation and a real ministry — 25%+ of adults live with some kind of disability that affects web use.
Should we use AI-generated imagery on our church website?+
Sparingly, and never depicting real people or real congregational moments. AI imagery is fine for illustrative background art or icon systems. Not fine for pretending to show your actual community. Real photos of real people always outperform AI-generated stock aesthetics for trust.
How often should we update our church website?+
Content: weekly (new sermon, blog post if applicable, updated events, updated series graphics). Design refresh: every 2–3 years. Structural rebuild: every 4–6 years. Set a named owner and a weekly maintenance calendar block, or the site will decay in months.
What analytics should a church track on its website?+
Five essentials: Plan-a-Visit form conversion rate, sermon video plays, giving page conversion, average pages per session, mobile vs desktop split. Use GA4 or Plausible. Skip vanity metrics like 'total pageviews' — they don't drive decisions. See the church analytics guide for the full stack.
What's the biggest church website mistake?+
Building it for the existing congregation instead of for the guest. The existing congregation already knows service times and where the parking is. The website's primary job is helping the guest who has never been there. Every design decision, every headline, every navigation choice should be evaluated against: does this help a first-time guest?
People also ask
Beginner
Can I build a church website by myself?
For a plant or a small church, yes — Squarespace and Wix are designed for it. Budget 20–40 hours for the initial build if you're using a template. Beyond that, budget for a professional designer or agency. DIY works for launch; it rarely holds up as the church grows.
Should we use a free church website builder?
For temporary use in a plant's first 90 days, sure. For anything beyond that, no. Free platforms have poor SEO, limited customization, and 'powered by X' branding that hurts credibility. Real cost of a good website is $25–65/month — well below the cost of a bad one.
How do I write good church website copy?
Answer the question the guest is actually asking, in the shortest respectful way. Not 'welcome to our beautiful community of faith' — that says nothing. Say 'Sunday at 9 & 11 a.m. at 123 Main St. Kids programs birth through 5th grade. Come as you are. Here's what to expect →' Real information, low friction, no religious jargon.
Do I need a blog on my church website?
Only if you'll actually maintain it weekly. A dormant blog signals 'this church isn't active.' If you can't commit to a weekly rhythm, skip it and invest in the sermon library instead — sermons are better SEO than blog posts for most churches anyway.
Intermediate
How do we migrate from an old church website to a new one?
Plan the migration in this order: (1) Audit current content and decide what carries over. (2) Build the new site in staging. (3) Set up 301 redirects for every old URL to the new equivalent. (4) Update sitemap.xml and submit to Google Search Console. (5) Cutover on a low-traffic day. (6) Monitor 404s + rankings for 30 days. Skipping the 301 redirects is the #1 way churches lose 40% of SEO traffic overnight.
How do we handle a church website across multiple campuses?
One main site (churchname.com) with a campus-selection experience for service times, staff, and events. Each campus gets a dedicated URL (churchname.com/campus/city) with its own LocalBusiness schema, address, times, and campus pastor. Never build separate domains per campus — you'll fragment SEO authority and confuse guests.
Should our church have a separate site for the church plant?
For the first 6–12 months, yes — a plant-specific site (plantcity.church) with LocalBusiness schema for the plant's city outperforms a subpage on the mother-church site. After the plant is established, migrate to a subdomain (city.mothersite.com) or a full multi-campus experience on the mother site.
How does the church app relate to the church website?
Separate audiences, separate jobs. The website is for guests and everyone using search. The app is for the already-engaged: sermon notes, group chat, event registration, giving, push notifications. Never assume guests will download the app. Never neglect the website in favor of the app. Both matter.
Advanced
How do we optimize a church website for AI answer engines (ChatGPT, Perplexity, Google AI Overviews)?
Six moves: (1) FAQ schema on every page with a FAQ pattern. (2) Semantic HTML — real headings, real lists, real definitions. (3) About pages with Person + Organization schema. (4) Answer-first copy: lead with the direct answer in the first 40–60 words. (5) Consistent NAP + entity signals across the web (Wikipedia, Wikidata where relevant, Google Business Profile, denominational directories). (6) Sermon transcripts as long-form authoritative content. See the AI Search Optimization guide for the full 6-layer citation stack.
What's the ROI of a church website redesign?
For a mid-size church (500–1,500), a good redesign typically produces: +30–60% Plan-a-Visit form submissions, +20–40% giving-page conversion, +30–70% organic search traffic within 12 months. On a $20k build, that's often equivalent to 30–80 additional first-time guests annually — well ahead of a similar spend on any other single marketing initiative.
How do we A/B test on a church website?
Most churches shouldn't. Traffic volume rarely produces statistical significance in a reasonable time. Instead, run sequential 30-day tests — try version A for 30 days, version B for 30 days, compare. Save formal A/B testing for high-traffic pages (Home, Plan a Visit, Give) at churches with 5,000+ website visits per month.
What are the biggest church website trends for 2026–2028?
AI answer engine optimization becoming table stakes. Voice search + smart speaker optimization for local queries. Web Vitals + accessibility standards tightening. Video-first homepage patterns replacing static hero. Personalization (returning-visitor vs. new-visitor experiences). Consolidation on 3–4 dominant platforms (Squarespace, Webflow, WordPress, custom). Church-specific CMSs continuing to lose share as generic platforms improve.
How do we know if our current church website is actually broken?
Run these 5 tests: (1) Timed guest task — ask 5 non-church-attending friends to plan a visit; observe. (2) Mobile speed test — Google PageSpeed Insights, all green? (3) Analytics review — is Plan-a-Visit conversion above 25%? (4) Accessibility scan — free axe-core browser extension, any critical failures? (5) Homepage recall — can a new team member describe your church accurately after 60 seconds on the homepage? Failing any of these = the site is broken enough to justify a rebuild.
Build for the guest. Rank for the algorithm. Reflect who you actually are.
At NACMC you'll audit your homepage in real time, rewrite your Plan-a-Visit page, and leave with a rebuild plan mapped to your church's stage. Laptops open. Real work. No panels.