vibeyour website Hire us
All prompts
WordPress Membership Site 14.8k chars

Vibe Code a Membership Website

Free vibe coding prompt to build a WordPress membership site. Subscription tiers, gated content, forum, onboarding flow, and member analytics. Complete community architecture.

Tested with: ChatGPT, Claude · Updated 2026-08-11 · License: do whatever you want, it's yours
wp-membership-site.prompt · 14.8k chars
Plan and produce a complete WordPress membership / community site
architecture, including tier strategy, data model, plugin stack, and
retention engine. Output should be production-ready.

═══════════════════════════════════════════════════════════════
BUSINESS DETAILS
═══════════════════════════════════════════════════════════════
- Community name: [NAME]
- Audience: [WHO, e.g., indie hackers / fitness coaches / writers /
 developers]
- Value promise: [e.g., "Weekly office hours + a vetted Slack + monthly
 cohorts"]
- Founder: [NAME]
- Pricing model: monthly + annual + lifetime founder
- Goal: 200 paying members in 6 months, 90% annual retention

═══════════════════════════════════════════════════════════════
BRAND
═══════════════════════════════════════════════════════════════
- Brand colors: warm cream (#f8f4ee) + deep ink (#0a0e27) + single
 member-only accent (electric purple #6b46c1 OR brand color). Pass AA
 contrast for body.
- Type: display sans for headings (Manrope, Outfit) + Inter for body.

═══════════════════════════════════════════════════════════════
PLUGIN STACK (WP-CLI)
═══════════════════════════════════════════════════════════════
 wp plugin install --activate 
 memberpress 
 buddyboss-platform 
 fluent-crm 
 wordpress-seo 
 wp-rocket 
 shortpixel-image-optimiser 
 restrict-content-pro

- Membership: MemberPress (best for content protection + Stripe + tiers)
 , OR Paid Memberships Pro (free alternative)
- Community: BuddyBoss Platform (forums, groups, member directory)
- Payments: Stripe (subscriptions + tax) + Apple/Google Pay
- Email/CRM: FluentCRM (lives in WP)
- Optional: Discourse if forum needs heavy moderation
- Optional: Zapier for off-WP integrations

═══════════════════════════════════════════════════════════════
TIER STRATEGY
═══════════════════════════════════════════════════════════════
- Free, limited access (3 free articles + community read-only)
- Pro, $[X]/month or $[Y]/year, full content + Slack/forum + monthly
 Q&A
- Founding, $[Z] one-time lifetime, Pro + 1-on-1 onboarding + Founders
 Council
- Family / Team add-on, 5 seats for X% discount

═══════════════════════════════════════════════════════════════
SITE MAP
═══════════════════════════════════════════════════════════════
1. Home (sells the community)
2. Join / Pricing
3. About (founder + community story)
4. Member wall, gated index of premium content
5. Forum (BuddyBoss groups)
6. Member directory (filterable by tag/interest)
7. Live Events (zoom links gated per tier)
8. Library, downloads, courses, templates
9. Account / Subscription (cancel/upgrade/payment methods)
10. Login / Register
11. Public blog (SEO funnel for non-members)

═══════════════════════════════════════════════════════════════
CONTENT PROTECTION RULES
═══════════════════════════════════════════════════════════════
- Block-level: lock individual blocks within posts (MemberPress Block
 Protection)
- Drip content: new members see content unlocked on a 7-day schedule for
 first 30 days
- Tease snippets: show 3 paragraphs of premium articles to non-members,
 then "Become a member to read more" CTA
- "Already a member? Sign in" link visible on every paywall
- Search index: include premium titles but mark them as gated in
 result UI

═══════════════════════════════════════════════════════════════
ONBOARDING FLOW (first 7 days)
═══════════════════════════════════════════════════════════════
- Day 0: Welcome email + "Complete your profile" prompt on first login
- Day 0: Get the new member into a "Welcome" forum group automatically
- Day 1: "Connect with 3 members" prompt with suggested members based on
 shared tags
- Day 3: "Have you tried [feature]?" with screenshot
- Day 7: Live "New member tour" Zoom (calendar embed in dashboard)

═══════════════════════════════════════════════════════════════
PRICING PAGE, BLOCK MARKUP
═══════════════════════════════════════════════════════════════
- Eyebrow + headline ("Three ways *to join*")
- Annual/monthly toggle (small JS, no library)
- 3-card tier comparison (stack mobile)
- Each card: tier name (sans), price (display, accent color), 8-feature
 list in prose with check icons, CTA button
- Middle tier highlighted: "Most popular" accent tag
- Below cards: full feature comparison table (HTML, sticky header)
- FAQ accordion specific to membership concerns: cancellation, refunds,
 billing, content access, what if I stop being a member

═══════════════════════════════════════════════════════════════
COMMUNITY (BuddyBoss)
═══════════════════════════════════════════════════════════════
- Activity feed (personalized to followed members + groups)
- Member profiles with custom fields (role, location, interests)
- Forum groups: General, Help, Wins, Q&A with founder, Off-topic
- Member directory filterable by interest tags
- Direct messages (1:1 + group)
- Notifications (in-app + email digest, configurable)

═══════════════════════════════════════════════════════════════
RETENTION ENGINE
═══════════════════════════════════════════════════════════════
- Weekly newsletter to members only (founder's letter + community wins)
- Monthly live AMA with founder (Zoom, recorded, archived)
- Member spotlights (3/month, member profile featured on dashboard)
- Annual member-only cohort program (small-group accountability)
- Dunning: failed-payment grace period 7 days, retry 4x, then downgrade
 to Free (not cancel)

═══════════════════════════════════════════════════════════════
EMAIL AUTOMATION (FluentCRM)
═══════════════════════════════════════════════════════════════
- Welcome series (3 emails day 0/3/7)
- Re-engagement: 14 days no login → "Miss you" + 3 recommended threads
- Renewal: 14 days before annual renewal → "Your year in [community]"
 summary
- Cancellation save: pause subscription option + downgrade option offered
 before cancel

═══════════════════════════════════════════════════════════════
SEO & MARKETING
═══════════════════════════════════════════════════════════════
- Public blog with 1-2 posts/week for organic SEO
- Affiliate program for members (10% commission, 60-day cookie) via
 AffiliateWP
- Schema: Organization, FAQPage, Article, Event
- OG image template per content type

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: Organization, WebSite
- 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 "membership / community site". 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.

═══════════════════════════════════════════════════════════════
PERFORMANCE
═══════════════════════════════════════════════════════════════
- Object cache (Redis), MemberPress is query-heavy
- Page cache via WP Rocket (excluding /account, /forum, /login)
- Cloudflare for static assets

═══════════════════════════════════════════════════════════════
ANTI-PATTERNS TO AVOID
═══════════════════════════════════════════════════════════════
- No "limited time founding member" countdown unless real
- No emojis in headlines or tier names
- No fake "[NAME] just joined" social-proof popups
- No autoplay videos
- No "EXCLUSIVE" / "VIP" / "INSIDER" in headlines (overused)
- No script fonts
- No content auto-locking that prevents readers from finishing a paragraph
- No requiring credit card for "free" tier
- No buried cancel link, make it findable in account settings

═══════════════════════════════════════════════════════════════
DELIVERABLE
═══════════════════════════════════════════════════════════════
1. WP-CLI install commands
2. Tier setup walkthrough (MemberPress rules + Stripe products)
3. theme.json (complete)
4. Site map
5. Block markup for pricing page
6. Welcome email series (5 emails, written copy)
7. Onboarding checklist UX (sequence)
8. Retention email flows
9. Launch checklist (20 items)

This prompt gives ChatGPT or Claude a full WordPress build plan for a membership and community site — the kind where people pay a recurring fee for gated content, a members-only forum, and a directory of other members. It specifies subscription tiers, content-gating rules, an onboarding flow, and a member directory as Gutenberg block markup on top of a membership plugin like MemberPress or Paid Memberships Pro. You get a plan for a recurring-revenue site, not a one-off product page.

What does the membership and community website prompt build?

The plan covers a public homepage that sells the membership, a pricing page comparing tiers, gated content areas that only paying members reach, a member directory, and a community forum. It specifies an onboarding email sequence, drip-scheduled content so new members are not dropped into ten years of archives, and an account area for managing billing. Organization and WebSite structured data is built in, and the gated pages are marked so search engines index your sales pages without exposing member-only material. Prefer to skip the setup? Our WordPress build service ships the same architecture for a flat fee.

Who is this membership prompt for?

It is written for creators with a paying audience, professional associations, niche communities moving off Facebook Groups or Slack, and educators who sell ongoing access rather than a fixed course. It assumes recurring billing and members-only content, not a public blog.

What’s inside the prompt?

  • A business details block for your niche, membership tiers, pricing, and the promise each tier makes
  • A membership plugin stack — MemberPress or Paid Memberships Pro — with a forum and recurring billing
  • A data model with membership levels, content-access rules, and a member profile type
  • Gutenberg block markup for the sales homepage, tier comparison, member dashboard, and directory
  • An onboarding email sequence and drip-content scheduling
  • Organization and WebSite structured data, plus a keyword plan for your niche
  • Core Web Vitals targets and a launch checklist

Frequently asked questions

How does the site gate content for paying members only?

The plan defines access rules per membership level, so a page, post, download, or forum board is visible only to members on the right tier. Non-members see a preview and a join prompt instead of the full content, and search engines are told to index the sales page but not the gated body.

Can I offer more than one membership tier?

Yes. The pricing page spec compares multiple tiers side by side, and the access rules map each tier to its own content and forum boards. You can run a free tier as a lead magnet alongside paid levels, or gate everything behind a single plan.

Does it include a members-only forum and directory?

Yes. The spec sets up a community forum with boards restricted by tier and a searchable member directory built from member profiles. A community is what keeps members subscribed month after month, so both are specified rather than bolted on later.

How does the site handle recurring billing and cancellations?

Billing runs through the membership plugin’s Stripe or PayPal integration, which handles recurring charges, failed-payment retries, and self-service cancellation from the member’s account area. The prompt specifies the account pages; the payment processor holds the card data, not your WordPress install.

Which AI tools work with this prompt?

ChatGPT and Claude both return the full membership spec. If your model is really about selling structured lessons rather than ongoing access, compare this with the online-course prompt before you build — and browse the rest of our free AI website prompts for adjacent ideas.

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