vibeyour website Hire us
All prompts
WordPress Religious Organization 15.9k chars

Vibe Code a Church Website

Free vibe coding prompt to build a WordPress church site. Sermons, events, online giving, plan-a-visit, ministries, and Church schema. Full religious organization setup.

Tested with: ChatGPT, Claude · Updated 2026-08-11 · License: do whatever you want, it's yours
wp-church.prompt · 15.9k chars
Plan and produce a complete WordPress site architecture for a church or
religious organization with sermons, service times, events, and online
giving. Output should be production-ready.

═══════════════════════════════════════════════════════════════
BUSINESS DETAILS
═══════════════════════════════════════════════════════════════
- Church name: [CHURCH NAME]
- Tradition / denomination: [TRADITION]
- City: [CITY]
- Service times: [SUNDAY 9AM / 11AM / WEDNESDAY 7PM etc.]
- Pastor: [NAME]
- Congregation size: [SMALL / MEDIUM / LARGE]
- Goal: welcome new visitors, equip current members, drive online giving
 + sermon engagement

═══════════════════════════════════════════════════════════════
BRAND
═══════════════════════════════════════════════════════════════
- Brand colors: warm cream + deep navy or wine accent + single warm gold
 accent for CTAs. Override if user provides; AA-contrast for body.
- Type: high-contrast serif for display (Lora, Cormorant) + Inter for
 body. Reverent without being old-fashioned.

═══════════════════════════════════════════════════════════════
PLUGIN STACK (WP-CLI)
═══════════════════════════════════════════════════════════════
 wp plugin install --activate 
 seriously-simple-podcasting 
 the-events-calendar 
 give 
 wordpress-seo 
 advanced-custom-fields 
 wp-rocket 
 fluent-crm
- Sermons: Seriously Simple Podcasting (creates podcast feed
 automatically) OR Sermon Manager. Recommend SSP.
- Events: The Events Calendar
- Giving: GiveWP OR Tithe.ly integration
- Optional: livestream embed (YouTube / Vimeo / Boxcast)

═══════════════════════════════════════════════════════════════
DATA MODEL
═══════════════════════════════════════════════════════════════
- CPTs:
 - `sermon`, fields: scripture (text, e.g., "John 3:16"), audio_file,
 video_url, sermon_notes_pdf, transcript, speaker (taxonomy),
 series (taxonomy), date, length
 - `ministry`, fields: name, description, leader, schedule, age_group,
 hero_image, contact
 - `staff`, fields: name, role, bio, photo, email
 - `event`, handled by The Events Calendar
- Taxonomies:
 - `sermon_series` (hierarchical, current series + past)
 - `speaker`
 - `topic` (Hope / Family / Stewardship / Justice / etc.)
 - `book_of_bible` (for sermon series)

═══════════════════════════════════════════════════════════════
SITE MAP
═══════════════════════════════════════════════════════════════
1. Home
2. I'm New / Plan a Visit (what to expect, parking, kids)
3. About (mission, beliefs, leadership)
4. Beliefs (statement of faith)
5. Pastor & Staff
6. Sermons (audio + video archive, filterable)
7. Ministries (children / youth / adults / music / outreach)
8. Events
9. Live Stream (with current service if streaming)
10. Connect / Get Involved (small groups, volunteer, member info)
11. Giving (online + recurring)
12. Resources (sermon notes, recommended books, devotionals)
13. Contact
14. Prayer Requests (gated or open form)

═══════════════════════════════════════════════════════════════
HOMEPAGE, BLOCK MARKUP
═══════════════════════════════════════════════════════════════
1. Hero: this Sunday's service time prominent + photo + "Plan a Visit"
 CTA + secondary "Watch Latest Sermon"
2. Welcome message from pastor (video or text, 2-3 paragraphs)
3. Service times card (multiple services with times, locations,
 livestream link)
4. Latest sermon card (with play button + title + speaker + date)
5. Upcoming events (3 next events with date blocks)
6. Ministries overview (grid of 4-6 ministries with photo + name +
 "Learn more")
7. Online Giving band ("Give securely from anywhere") + CTA
8. Newsletter signup ("Get weekly devotionals + service updates")

═══════════════════════════════════════════════════════════════
SERMONS ARCHIVE
═══════════════════════════════════════════════════════════════
- Filterable by series, speaker, topic, book of Bible, year
- Card grid with hero image (often series art), title, speaker, date,
 duration, "Listen" / "Watch" / "Notes" icons
- Search bar at top
- "Subscribe to podcast" buttons in header (Apple, Spotify, RSS)

═══════════════════════════════════════════════════════════════
SERMON DETAIL PAGE
═══════════════════════════════════════════════════════════════
- Hero with series art / video thumbnail
- Title + scripture reference + speaker + date + length
- Audio + video player (with timestamps for sections)
- "Download audio" + "Download notes PDF" buttons
- Full transcript (collapsible, SEO-friendly)
- Related sermons (same series, same topic)
- Discussion / comments (optional, moderated)

═══════════════════════════════════════════════════════════════
LIVE STREAM PAGE
═══════════════════════════════════════════════════════════════
- Embedded YouTube / Vimeo / Boxcast iframe
- Service order PDF (downloadable)
- "Connect card" form (visible during stream, name, prayer request,
 contact request, decision to follow)
- Children's program info during service
- Service times reminder

═══════════════════════════════════════════════════════════════
PLAN A VISIT PAGE
═══════════════════════════════════════════════════════════════
- "What to expect" section (parking, dress, length, kids' program)
- Map and directions (Google Maps embed)
- "I'm planning to visit" form (optional, name, when, kids' ages,
 questions)
- Photos of building/sanctuary
- Service times + locations
- Greeter contact for the day

═══════════════════════════════════════════════════════════════
GIVING PAGE
═══════════════════════════════════════════════════════════════
- One-time + recurring options
- Fund designation: General / Missions / Building / Specific Campaign
- Tithe vs offering vs special gift labels (where appropriate)
- Text-to-give QR code + number
- Tax receipt automation (annual statement for US members)
- Secure Stripe processing (highlight security visibly)

═══════════════════════════════════════════════════════════════
EMAIL FLOWS
═══════════════════════════════════════════════════════════════
- Welcome series after newsletter signup (3 emails over 7 days)
- Visitor follow-up (after "I'm planning to visit" form): day-of + day-after
- Weekly newsletter (Friday, this Sunday's service + sermon series
 context)
- Members-only digest (monthly, small group sign-ups, volunteer needs)
- Year-end giving appeal

═══════════════════════════════════════════════════════════════
SEO & LOCAL
═══════════════════════════════════════════════════════════════
- Schema: Church (LocalBusiness subclass), Event, AudioObject (sermons),
 Article (blog)
- Google Business Profile claimed and active
- Local SEO: "Churches near me" + "[CITY] [DENOMINATION] church"
- Photos on GBP (sanctuary, members, events)

ADDITIONAL SEO REQUIREMENTS (implement all of these):

On-Page SEO for Every Page:
- Yoast/RankMath meta title template: "[Page Title] | [Site Name]" (under 60 chars)
- Meta description per page: 150-160 chars, include primary keyword + CTA
- Exactly ONE H1 per page — use the real, human headline; keep keywords in the title and meta, not the visible H1
- Logical H2 > H3 heading hierarchy, never skip a level
- Headings should include secondary keywords naturally,
  keep the section's real, human label (keywords in title and meta, not stuffed headings)
- Every image must have a descriptive alt attribute with keywords
- Internal links between related content using descriptive anchor text

Structured Data (JSON-LD via Yoast/RankMath + manual where needed):
- Primary schema types: Church, Organization
- BreadcrumbList on all pages
- FAQPage schema on any page with an FAQ/accordion section
- Article schema on all blog posts (auto via Yoast)
- Validate schema with Google Rich Results Test before launch

Open Graph & Social Sharing:
- og:title, og:description, og:image, og:url on every page
- twitter:card=summary_large_image on every page
- Default OG image set in Yoast; per-page overrides for key landing pages
- OG images should be 1200x630px, branded, with clear text

Content SEO:
- Write real, useful body copy for every page (not just headings and CTAs).
  Every major section needs at least 2-3 sentences of descriptive text
  that search engines can index.
- Blog content strategy: 10 seed articles targeting long-tail keywords
  related to "church / religious organization". List the titles and target keywords.
- Use the primary keyword once or twice where it reads naturally; keep the rest in titles and meta, never stuffed.
- Every CTA should use descriptive anchor text with the service keyword.

Technical SEO:
- XML sitemap split by post type (auto via Yoast)
- Canonical tags on all pages (auto via Yoast)
- robots.txt: allow all, point to sitemap
- 301 redirects plan for any renamed/moved content
- Breadcrumbs enabled via Yoast + schema
- Clean permalinks: pick one post-permalink base that fits the site (do not force /blog/ on a post-centric site); /%postname%/ is fine for pages
- Lazy load all images below the fold, eager load hero/LCP image
- Core Web Vitals targets: LCP < 2.5s, CLS < 0.1, INP < 200ms

SECURITY, ACCESSIBILITY & HONESTY (required):
- Escape all output (esc_html/esc_url/esc_attr), sanitize all input (sanitize_text_field + wp_unslash), and use a nonce + current_user_can() on every form handler and custom action. Emit JSON-LD with wp_json_encode().
- Target WCAG 2.2 AA: visible :focus-visible states, <label for> on every field, full keyboard operability, and @media (prefers-reduced-motion: reduce) around all motion.
- Never fabricate business data, testimonials, ratings, credentials, or stats; leave labeled {{TODO}} placeholders for anything the user has not supplied.
- PLUGIN INSTALL: some listed plugins are premium or not in the wordpress.org directory, so a single `wp plugin install` will error out. Split the list into free (wp.org) vs premium (upload/license), verify each slug, and note that gallery/group ACF fields and ACF Blocks need ACF Pro.
- Commit to ONE paradigm: a block theme (theme.json + block templates) OR a classic theme/builder — never mix them. If a plugin already owns a post type or feed (inventory, sermons, courses, job listings, podcast feeds), extend it — do not re-declare that CPT or emit a second, conflicting schema block.

Local SEO:
- Full NAP (Name, Address, Phone) in footer, consistent across all pages
- Google Business Profile integration (link in footer + schema)
- Location keywords in at least 3 page headings
- Embedded Google Map on contact/location page
- Target keywords include city/region: "church / religious organization in [City]"

═══════════════════════════════════════════════════════════════
ACCESSIBILITY
═══════════════════════════════════════════════════════════════
- WCAG AA minimum
- Sermon transcripts make audio accessible to deaf community
- Live stream with captions (if possible)
- Large clear typography (older congregants)

═══════════════════════════════════════════════════════════════
ANTI-PATTERNS TO AVOID
═══════════════════════════════════════════════════════════════
- No emojis in headlines
- No "FREE GIFT WHEN YOU VISIT!" marketing tone
- No autoplay video with sound on hero
- No real denomination logos as images
- No "Voted Best Church!" badges
- No bright marketing gradients reminiscent of corporate sites
- No "Join us for our amazing services!" filler, describe what visitors
 will actually experience
- No script/handwritten fonts (avoid amateur-looking)
- No popup giving asks within first 5s of landing
- No buried unsubscribe links

═══════════════════════════════════════════════════════════════
DELIVERABLE
═══════════════════════════════════════════════════════════════
1. Site map
2. WP-CLI install commands
3. Sermon CPT + ACF JSON
4. theme.json
5. Homepage block markup
6. Sermon archive + detail template
7. Plan a Visit page (with visitor form)
8. Giving page setup with GiveWP
9. Live Stream page configuration
10. Email flow specs (5 flows)
11. Launch checklist (15 items)

This free prompt hands ChatGPT or Claude a full build plan for a church website, covering service times, a searchable sermon archive, an events calendar, online giving, and a plan-a-visit page for newcomers. It is written for congregations that want members and first-time guests to find worship times, catch up on past messages, and give online without digging through a cluttered menu. What comes back is a complete WordPress specification, not a one-page mockup.

What does the church website prompt build?

The spec lays out the pages a congregation uses week to week. The homepage leads with the next service time and a plan-a-visit call to action. A sermon archive stores each message with audio or video, the speaker, the series, and the scripture reference, so people can filter by book or topic. An events calendar carries recurring gatherings, seasonal services, and outreach dates with registration links. Separate templates handle ministries, an online giving page, a staff directory, and a prayer request form, all as Gutenberg block markup on a matching theme.json.

Who is this church prompt for?

It fits established congregations, church plants, parishes, and multi-campus ministries that have outgrown a free page builder. Volunteer communications teams lean on it because the structure is decided up front, so nobody has to guess where the giving link or the livestream belongs. A pastor or administrator can follow the plan directly, or pass it to a developer as a finished brief. Congregations that also run a day school can pair this with the school website prompt. If building it in-house is not realistic, our WordPress build service can take the same spec to launch, and what a WordPress build costs is published up front.

What’s inside the prompt?

  • A fill-in brand section for your congregation’s name, colors, denomination, and weekly schedule
  • A recommended stack built around the Church Content plugin for sermons and staff, GiveWP for online and recurring giving, The Events Calendar, and Yoast SEO
  • A data model with sermon, ministry, event, and staff structures plus series and scripture taxonomies
  • A theme.json design system for color, type scale, and spacing that keeps the site calm and legible
  • Full Gutenberg markup for the homepage, sermon archive, events, ministries, giving, plan-a-visit, staff directory, and prayer request pages
  • Church and Organization structured data, an XML sitemap, and keyword targets aimed at local “church near me” searches
  • Core Web Vitals targets and caching notes so media and livestream pages stay fast on a Sunday morning
  • A launch checklist and the mistakes to avoid, like burying service times below the fold

Frequently asked questions

Can first-time visitors find our service times and plan a visit?

Yes. The homepage puts your next service time and a plan-a-visit button above the fold, and the plan-a-visit page covers parking, what to wear, childcare, and what a first Sunday looks like. That cuts down on “when do you meet” emails and gets newcomers through the door.

Does the prompt set up online and recurring giving?

It specifies GiveWP for one-time and recurring gifts, with designated funds such as general, missions, and building. The giving page has a clear form, suggested amounts, and a note on how gifts are used, so members can tithe from a phone in under a minute.

Can we publish sermons with audio, video, and scripture references?

Each sermon is a separate entry with an embedded audio or video player, the speaker, the series it belongs to, and the Bible passage. Visitors filter the archive by series, preacher, or book of the Bible, and every sermon page is structured to be shared and indexed on its own.

How does it help our church show up in local search?

The plan targets “church near me” and denomination-plus-neighborhood phrases, and marks the site up with Church and Organization structured data alongside your address and service times. Church is a recognized schema.org type that describes your congregation to search engines and AI answers; it is not a review-style business listing, so the focus stays on accurate location and identity rather than star ratings.

Can it run our events calendar and small-group ministries?

Yes. The Events Calendar handles weekly gatherings, seasonal services, and outreach dates with registration links, while ministry pages describe each group, its meeting time, and a contact, so people find the right group without calling the office.

How to actually run this.

01

Copy the whole thing

All of it. Do not trim it down, every line is in there for a reason.

02

Swap in your details

Find the BUSINESS DETAILS part and drop in the real business. Name, what they do, all of it.

03

Paste and wait

Drop it into Claude for the first pass, or v0 if it is a landing page. Give it a minute.

04

Clean it up

Tweak the boring 10 percent. Spacing, mobile, that one cringe line. Ship it.

What’s next: from generated code to a website that works

The prompt did the hard 90 percent. What’s left is the boring 10 percent that turns a folder of code into a site people can actually find and trust. Here’s the whole checklist, in order.

1. Buy a domain

Grab your name at a registrar like Namecheap, Cloudflare, or Porkbun — about $10 to $15 a year for a .com. Skip the ten-year prepay and the upsells; you just need the domain and, ideally, the free WHOIS privacy most registrars now include.

2. Put it online

If the AI built you a static site (HTML, CSS, and JavaScript), you can host it for free: drag the folder into Netlify or Vercel, or connect a GitHub repo, then point your domain at it. If it built a WordPress theme, you need WordPress hosting — pick a managed host, install WordPress, upload the theme, and connect the domain. Either way, turn on HTTPS; it’s free and automatic on every modern host.

3. Wire up the parts AI skips

Generated sites almost always ship with a contact form that goes nowhere and a fake “success” message. Connect it to a real endpoint (Formspree, Web3Forms, or a plain mailto link) so leads actually reach you. While you’re in there: add a favicon, swap the placeholder images for your own compressed photos, and open the site on your phone to catch whatever breaks on a small screen.

4. Do the basic SEO and AI-search setup

This is what gets you found on Google and cited by ChatGPT, Perplexity, and AI Overviews. The essentials: a unique title tag and meta description on every page, one clear topic per page, an XML sitemap submitted to Google Search Console, basic structured data (Organization and FAQ schema), and an llms.txt file so AI crawlers can read you. If that reads like a foreign language, our SEO optimization service does it as a flat-fee pass, and our free SEO checklist walks the DIY route step by step.

5. Make it fast

AI builders love shipping four-megabyte images and render-blocking scripts. Compress your images, lazy-load anything below the fold, and run the page through PageSpeed Insights until Core Web Vitals turn green — speed lifts both rankings and conversions, so it’s the rare fix that pays twice. Our speed optimization service handles it if you’d rather not.

6. Get found locally, and measure it

Add analytics (GA4, or a lighter option like Plausible) so you can see what’s working instead of guessing. If you serve a local area, set up a Google Business Profile and use the exact same business name, address, and phone number everywhere — that consistency is what lands you in the map pack and in local AI answers.

7. Keep it alive

A website isn’t set-and-forget, especially on WordPress. Budget for backups, security, and updates so a routine plugin update doesn’t take the site down six months from now. Our care plans cover all of it from $290 a month, or you can do it yourself — you own all the code either way.

When it’s worth handing off

If any of these steps stall you — and hosting, DNS, and SEO stall a lot of people — that’s exactly what we’re for. We build the whole thing at a flat fee, ship it live, and hand you the code on GitHub, having read every line the AI wrote. Or take the free prompts and run with it yourself. Both outcomes are genuinely fine with us.

More from the stash.

You read. We build.

No free weekend? We will build it for you.

This is the exact prompt we would use. Flat fee, real deadline, code is yours.

Have us build this one Fixed fee · Fixed timeline