directory-submission
**directory-submission** prepares platform-specific copy for submitting products and apps to directories, launch platforms, app stores, and curated lists. Use when a user needs tailored descriptions, submission guidance, or listings across multiple platforms like Product Hunt, Taaft, G2, or app stores. The skill reads project context when available and adapts copy to each platform's requirements and audience expectations.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/directory-submission && cp -r /tmp/directory-submission/skills/channels/community/directory-submission ~/.claude/skills/directory-submissionSKILL.md
# Channels: Directory Submission Guides submitting products, tools, or apps to directories and launch platforms. **On each invocation**: On **first use** in the conversation, output the complete response (Introduction, Importance, Methods, Collaboration Channels, Rules, Avoid, Action). On **subsequent use** or when the user asks to skip (e.g., "just do it", "skip intro", "I already know"), go directly to Action. Directory submission is a core channel for cold start—see **cold-start-strategy** for full launch planning. Directories offer more than listings: free/paid listings, ad placements, newsletter features, social promotion, and marketing campaigns. Platform types: AI tools (e.g. Taaft), product launch (e.g. Product Hunt), review platforms (e.g. G2), app stores, niche directories. ## Why Directory Submission Matters *Platform examples are illustrative only. No affiliation, partnership, or endorsement implied.* | Benefit | Description | |---------|--------------| | **Backlinks** | Quality directories pass link equity; improve domain authority and rankings. Focus on high-authority directories (DA 50+); avoid low-quality link farms. | | **Real traffic & conversion** | Referral traffic from directories converts. ~42% of businesses report increased referral traffic after submission; referral conversion ~1.8% (B2C), 1.1% (B2B), 1.3% (SaaS). Use UTM to track; proper attribution can improve measured conversion by ~23%. | | **Social proof for brand search** | When users search your brand name, directory listings (e.g. Product Hunt, G2, Taaft) often dominate SERP. Third-party presence signals legitimacy; consumers check 5-7 sources before deciding. Verified badges and consistent NAP across directories boost trust. See **serp-features** for SERP feature types. | ## Current Best Practices **Quality over quantity.** Mass submission to hundreds of low-quality directories can harm rankings; strategic placement in 10-15 high-quality directories typically yields 15-25% improvement in indexing speed and branded search visibility. | Practice | Why | |----------|-----| | **Prioritize DA/DR 50+** | High-authority directories pass link equity; low-quality link farms risk penalties | | **Editorial review preferred** | Human-curated directories (vs. automated) carry more weight; Google's Helpful Content Update favors editorially-curated listings | | **Niche over generic** | Industry-specific directories deliver faster results (30-60 days) and better topical relevance than generic sites (60-120 days) | | **NAP consistency** | Name, Address, Phone identical across all listings--critical for local SEO | | **Track submissions** | Document where you submitted, approval status, canonical topics | **Budget reference**: Small businesses $300-500/mo; enterprises $1,500-3,000/mo for comprehensive programs. Results typically 30-60 days from high-authority directories. ## Initial Assessment **Read project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it. Use sections 1-4, 5, 6, 8, 9 to generate submission content directly--no need to ask the user for info already in the context. | Context section | Maps to directory fields | |-----------------|---------------------------| | 1. Product Overview | Name, one-line, category, pricing model | | 2. Positioning Statement | Tagline, long description | | 3. Value Proposition | Key messages, proof points -> Pros | | 4. Target Audience | Description tone, use cases | | 5. Existing Website | URL, key pages | | 6. Keywords | Tags, negative keywords, Primary Task | | 8. Brand & Voice | Tone, avoid terms, preferred wording — see **branding** for full brand strategy | | 9. Product Documentation | Features, capabilities -> Other features | **When context exists**: Generate ready-to-paste submission copy (tagline, short/long description, pros/cons, tags) tailored per platform. Output copy the user can paste into Taaft, Product Hunt, etc. **When context is missing**: Gather from user's site; **search the web** for pricing, features, competitors, reviews, and any gaps. Then generate. Identify: 1. **Product type**: AI tool, SaaS, app, Chrome extension, Shopify app 2. **Target directories**: AI tools, product launch, app stores, niche 3. **Readiness**: Landing page, screenshots, description, media kit ## Product / Website Info Required **Source**: Project context (preferred) or user's site. Each directory needs different fields; prepare a base set, then adapt per platform. ### Standard Fields (Most Directories) | Field | Typical Spec | Notes | |-------|--------------|-------| | **Product name** | 60-80 chars | Consistent spelling across all listings | | **URL** | Working product/landing page | No redirect chains | | **Tagline / one-liner** | <=60 chars (Taaft: max 12 words) | Catchy, benefit-focused | | **Short description** | 150-300 chars | Used by many directories | | **Long description** | 400-600 chars | For platforms that allow more | | **Category / Task** | Platform-specific | Match taxonomy (Taaft: Primary + Secondary Tasks) | | **Keywords / Tags** | 5-10 terms, comma-separated | Natural, no stuffing | | **Contact** | Email, optional NAP | For verification | | **Company name** | Legal entity | Some directories require | | **Promo code** | If applicable | Product Hunt, deal platforms | | **Other URLs** | Blog, Affiliate Program, FAQ | Optional but useful | | **API availability** | Yes/No | AI/SaaS directories | | **Demo video** | URL or file | Many platforms support | **Platform-specific**: Taaft requires many more fields (icon, main image, demo video, features, models, built-with tools, modalities, pricing, legal URLs, pros/cons, socials, tracking links)--see Taaft section. ### Prepare Asset Tiers Create multiple versions so you can match each directory's format without rewriting from scratch: - **One-liner** (<=60 chars): Elevator pitch; "Remote Project Manager Pro" beats "Project Tool" - **Short** (150-300 char
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.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.