Directory Submission

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.

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.

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.

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)

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 chars): Core value + one differentiator
• Long (400-600 chars): Problem -> solution story; features + benefits

Rich Content Base (Build First, Use Everywhere)

Even if a directory form does not require it, build a full reference so you can tailor per platform and for SEO/GEO. Search the web when info is missing.

Multiple Versions for Differentiation (SEO & GEO)

Do not submit identical copy to every directory. Duplicate content hurts SEO and reduces GEO citation diversity. Generate at least 2-3 distinct versions per field (tagline, short, long) so:

• Different directories show different angles
• AI tools and search engines see varied, non-duplicate signals
• Users can pick the best fit per platform or A/B test