When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Guides forum promotion, community invitation, and vertical community marketing. Community-led growth (CLG) costs ~90% less than paid acquisition with ~3.2x higher customer LTV. Indie Hackers delivers ~23% conversion vs Product Hunt ~3%; HN and Reddit require sustained engagement. For cold start planning (first users, launch channels), see cold-start-strategy. For indie hacker strategy (first 100 users, Build in Public content framework, Indie Hackers tactics), see indie-hacker-strategy.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and brand voice.
Identify:
| Platform | Audience | Use |
|---|---|---|
| Indie Hacker | Indie makers, founders | Sustained engagement; authentic journey posts; ~23% conversion vs PH 3% |
| Hacker News | Tech, startups | Show HN launch; ~1,300 posts/day; front page = luck + timing |
| Hackernoon | Dev, tech readers | Content distribution |
| Industry forums | Niche verticals | Discount codes for leads; search "[industry] forum"; post event/activity promotion; see discount-marketing-strategy for code strategy |
| Subreddit-specific | See reddit-posts; 90/10 rule; 29+ posts for traction | |
| Discourse (self-hosted forum) | Community-specific | Owned forum; full SEO/GEO control; see Discourse SEO section below |
If you run a Discourse forum (or similar self-hosted forum), SEO/GEO considerations differ from posting on third-party platforms:
| Practice | Guideline |
|---|---|
| Guest access | Allow anonymous reading for categories meant to attract traffic; login-only mode severely limits indexed pages |
| Topic structure | First post carries SEO weight; write clear titles and substantive opening posts; avoid fragmented short topics |
| Sitemap & robots | Discourse generates sitemaps automatically; monitor in GSC as a separate property (subdomain or subdirectory) |
| Content quality | Merge duplicates, mark resolved threads, surface FAQ topics—forum-level quality signals affect crawl and citation |
| GEO | Structured topic titles and well-formed opening posts are extractable by AI tools; forum format with timelines and accepted answers lends credibility |
| Subdomain vs subdirectory | Discourse recommends subdomain for operational reasons; search engines do not inherently favor either for ranking—choose based on infrastructure, not SEO alone |
| Practice | Guideline |
|---|---|
| Title | "Show HN: [Product] - [specific problem solved]"; honest, no clickbait |
| Timing | Tue-Thu; peak US hours; avoid weekends, Mon, Fri |
| First comment | Invitation to engage; product status (beta/MVP); differentiated solution; try-it link |
| Assets | Live demo, GIFs, screenshots, 30-60s demo video |
| Expectation | Traffic spike, not sustained growth; partly luck-dependent |
For full Indie Hackers tactics, Build in Public content framework (40/30/20/10), first 100 users → indie-hacker-strategy.
| Channel | Method |
|---|---|
| Welcome email | Post-signup automation; 4x open, 5x CTR vs regular campaigns |
| Homepage CTA | Button, popup, banner; above-the-fold upgrade CTA |
| In-site placement | High-visibility areas; user-focused sections (e.g. dashboard, settings) |
| Banner | Homepage, carousel below hero |
| Registration emails | Success/confirmation email with community link |
| EDM campaign | Newsletter + banner, interview-for-membership |
| Discord | Post event/community info; founder engagement 2-3h/day |
| Vertical forums | Search "[industry] forum"; post event/activity promotion |
| Post-login form | In-app signup form shown after login; high-intent placement |
Welcome email best practices: One clear CTA per email; front-load value in subject; personalize (signup source, interests); link to best content, events; ask questions (~75% reply rate). Automated 2-4 email sequence.
| Principle | Guideline |
|---|---|
| Target | Find channels where target audience gathers |
| Niche over broad | Industry-specific subgroups; avoid mass posting |
| Caution | Mass posting risks removal; match community tone; choose wording carefully |
| Examples | Reddit subreddits, Discord servers, Quora, X, Hacker News, Stack Overflow, niche B2B communities |
| Regional | Large communities by locale—event/activity promotion; target vertical channels within each; see localization-strategy |
Community-led growth: Engage before promoting; build trust; contribute value first.
| Channel | Use |
|---|---|
| Hashtags | Social tag optimization |
| Facebook groups | Indirect referral |
| Giveaways | Attention and conversion |
| Platform | Use |
|---|---|
| Wikipedia | Global; neutral, cited content; brand credibility |
| Quora | Q&A; brand discussion, thought leadership, long-term SEO |
| Stack Overflow | Tech/dev; expertise signals, backlinks |
| Regional | Local encyclopedias and Q&A by locale; verified credentials; see localization-strategy |
Wikipedia: Neutral language, credible references, no promotional content. Regional platforms require verified credentials; prioritize local search share. Free and sustainable; supports long-term conversion while search habits persist.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
日本語の概要は準備中です。原文の説明を表示しています。