Suede Directory Submissions

Suede Directory Distribution

Suede treats directory distribution as a verifiable discovery layer, not a submission-count contest. Build the user's backlink and buyer-discovery foundation by selecting the right directories, sequencing them around real launch moments, adapting truthful positioning, and checking that each listing and backlink actually landed.

Before Starting

Check for product marketing context first:

If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Core Philosophy

Directory submissions can add discovery surfaces, referral paths, and backlinks, but

their value varies by product, directory, listing quality, and current platform

rules. Treat each benefit as a hypothesis to verify with listing status, referral

analytics, search data, and qualified outcomes. A directory plan complements

destination pages and other distribution; it does not guarantee authority,

citation, traffic, ranking, or leads.

The full directory catalog lives in references/directory-list.md. The positioning variant library lives in references/positioning-variations.md. The submission tracker template lives in references/submission-tracker-template.csv.

Three Operating Rules

Rule 1: Foundation before submission

Before recommending a submission, verify the directory's current official

requirements and record the source URL and check date. The linked page should be

publicly reachable, truthful, useful to the directory's audience, and measurable.

Prepare only the assets the current form requires, using real product screenshots

and approved brand files. Add pricing, legal pages, video, schema, or additional

formats when the product, jurisdiction, or verified directory rules call for them;

do not invent universal prerequisites.

Rule 2: Destination pages before directories

Choose the most relevant verified destination for each audience: a homepage,

use-case page, integration page, comparison page, template, or documentation page.

It must accurately fulfill the listing promise and have a measurable next step.

Do not impose a fixed page count or block a suitable listing merely because an

unrelated content type does not exist.

Rule 3: Positioning varies by directory type

Adapt the description to the directory's verified fields, audience, and rules.

Reuse approved facts, but change emphasis when that improves relevance; do not

claim that duplicate descriptions trigger a search or AI penalty without current

evidence. See references/positioning-variations.md for templates.

| Surface | Lead with | Why |

|---|---|---|

| Startup directories | Outcome | Audience is other founders. They care what it does. |

| SaaS directories | Alternative framing | People search "[competitor] alternative" — meet them there. |

| AI directories | AI-first architecture | TAAFT/Futurepedia audiences explicitly want AI tools. |

| Agent/MCP directories | Agent/MCP angle | Use only for a live compatible capability. |

| No-code directories | Ease + power | Audience values speed-to-build over depth. |

| Dev directories | Technical depth | Dev audiences reward technical substance. |

| B2B review sites | ROI + use case | Buyers want outcomes and case studies. |

Workflow

Step 1: Readiness assessment (Phase 0)

Assess the selected directory against current requirements:

• Is the product publicly accessible (no password wall)?
• Is there a pricing page (even "free while in beta")?
• Are privacy policy + terms live?
• Are the required approved logo, screenshot, and video assets available?
• Does the destination page match the proposed listing copy and CTA?
• Is referral and conversion measurement configured?
• Does the current directory policy allow this product, claim set, and category?
• For review sites, are there genuine eligible users and a policy-compliant ask?
• Who has authority to create the account, accept terms, and submit?

A missing current platform requirement, truthful destination, or submission

authority is a hard block for that directory. Other gaps are prioritization inputs,

not universal launch blockers.

Step 2: Choose the tiers

Full catalog in references/directory-list.md. Summary:

| Tier | When | Illustrative candidates to verify |

|---|---|---|

| Flagship launch | Around a relevant launch | Product Hunt, BetaList, HN Show HN, Fazier, DevHunt |

| Startup/SaaS | Launch and rolling | AlternativeTo, SaaSHub, G2, Capterra, F6S |

| AI directories | If the product has a substantiated AI capability | TAAFT, Futurepedia, Toolify, Future Tools |

| Agent/MCP registries | If a live compatible integration exists | Glama, APITracker, LF MCP Registry |

| No-code directories | If the product genuinely serves that audience | NoCodeFinder, No Code MBA |

| Integration marketplaces | When the integration ships | The integration owner's official marketplace |

| Profiles and vertical directories | When audience and category fit | Relevant company profiles or industry-specific catalogs |

Triage rule: Only submit where the product is a genuine fit under the

platform's current eligibility and category rules.

Step 3: Prepare asset variations

For each tier, prep distinct variants from

references/positioning-variations.md only after inspecting the destination's

current form:

• Tagline sized to the verified field limit
• Short description sized to the verified field limit
• Long description sized to the verified field limit
• Category tags limited to the verified taxonomy and product fit
• Logo assets
• Screenshots + demo video URL
• Founder story (2–3 sentences)

Keep facts consistent and approved. Adapt length and emphasis to each verified

form without inventing features, customers, outcomes, or platform support.

Step 4: Batch submit

Set up the tracker spreadsheet (references/submission-tracker-template.csv).

Prioritize a small evidence-backed batch. Before any external submission, show

the exact public copy, assets, account, destination, timing, and maximum cost,

then get explicit approval for that submission. Approval for research or

another directory does not transfer.

Per submission:

• Verify the current form, rules, price, and account identity.
• Prepare the exact field values and assets as a reviewable draft.
• Obtain explicit approval for that destination, copy, assets, timing, and

maximum cost.

• Fill and upload only the approved values.
• Pause before any changed price, upsell, or materially different rendered

preview; re-approve the delta.

• Submit once, then capture confirmation.
• Log: date, URL, status, moderator notes.
• Once live, record the canonical listing URL and inspect the rendered link or

page HTML for rel, redirect, and destination behavior. Absence of rel in

response headers does not prove link attributes. Log the method and check date.

Flagship Launch Listing

For any time-sensitive launch surface, research the platform before building the

plan. Use its current official help, submission form, and community rules; record

the URLs and check date. Do not present remembered algorithm behavior, ideal

launch times, asset dimensions, hunter effects, or engagement thresholds as facts.

Preparation milestones

• Confirm eligibility, account standing, moderation rules, scheduling options,

required assets, and prohibited promotion.

• Draft truthful positioning, an approved maker story, real product visuals, and

a working destination CTA in the exact current form limits.

• Preview the listing and test the product, signup, analytics, and support path.
• Build a communication plan from channels the user owns or is authorized to use.
• Assign a responder for genuine questions and feedback.

Launch and follow-through

• Publish only after the user authorizes the listing, timing, and public copy.
• Follow current solicitation and outreach policies. Do not manipulate voting,

fabricate engagement, or message people without a legitimate relationship and

authorization.

• Respond helpfully, log referrals and qualified outcomes, and capture lessons.
• Share a recap only where current community rules permit it.

Reviews Playbook

Review directories can help buyers evaluate products, but eligibility, incentive,

moderation, badge, report, and paid-plan rules change. Before recommending a

campaign:

• Read the current official review and incentive policy for the chosen platform.
• Record the source URL, check date, eligibility rules, deadlines, and maximum

verified cost.

• Identify real users with firsthand product experience; never manufacture,

gate, pre-score, or script reviews.

• Get explicit authorization for the recipient list, wording, channel, cadence,

and any incentive before outreach.

• Track requests, completed reviews, moderation status, referral outcomes, and

complaints. Set targets from the actual eligible pool and user goals.

Do not claim a badge threshold, report cutoff, ownership relationship, incentive

permission, plan price, or expected response rate unless it was verified from a

current authoritative source. A small customer base is a planning constraint, not

automatic proof that a listing is worthless.

Destination Pages Strategy (What the Backlinks Point At)

Match each listing to the most useful truthful page available. A homepage can be

appropriate when it satisfies the audience and promise; a specialized page may be

better when evidence supports it.

1. Alternative pages

Use when current customer or search evidence shows comparison intent:

• /alternatives/[competitor-1]
• /alternatives/[competitor-2]
• /alternatives/[competitor-3]
• /alternatives/[competitor-4]

Use verified features and prices, clearly state when each option fits, and add

FAQs or structured data only when appropriate and valid.

Critical: Be honest. Verify material competitor claims, date the comparison,

and correct it when facts change.

2. Use-case / ICP pages

Create a dedicated ICP or use-case page when current demand and product evidence

justify one:

• /for/[audience] — coaches, agencies, ecommerce, SaaS, consultants, etc.
• /use-cases/[use-case] — lead qualification, onboarding, product recommendations, etc.

3. Template / asset gallery (if applicable)

Use when templates provide standalone value and product activation can be

measured:

• One indexable page per template at /templates/[slug].
• Use a descriptive title, useful instructions, real screenshot, and clear CTA.
• Link genuinely related templates.
• Set output volume from quality capacity and measured demand, not a borrowed

traffic or revenue story.

4. "Best of" listicles you wrote yourself

Write honest, current roundups only when the team can research the category and

disclose its methodology. Include a useful set of alternatives rather than a

fixed count, and do not promise ranking or AI citation.

5. Integration pages (when integrations ship)

Create an integration page when the integration is live and the page helps users

understand setup, capabilities, and limits. Measure its results rather than

projecting another company's traffic.

GEO (Generative Engine Optimization)

Directories and destination pages may appear in search and answer engines. Treat

visibility as an observable outcome, not a guaranteed effect of authority scores

or markup.

Tactics that get pages cited

• Use a clear title and logical heading hierarchy for readers.
• Publish accurate facts with primary sources, dates, definitions, and caveats.
• Add only schema that matches visible page content and current specifications.
• Use comparison tables when they improve comprehension and can be maintained.
• Explain what the product is and who it serves early on the page.
• Earn genuine third-party discussion; do not seed or fabricate citations.
• Publish original research only with a reproducible method and rights-safe data.
• Maintain authorized company profiles with consistent verified entity facts.
• If applicable, maintain accurate registry entries for live integrations.

Measurement

Use authorized, currently callable tools or manual checks to sample relevant

queries. Record engine, account context, prompt, locale, date, result, and whether

the result is reproducible. Verify any tracking product and its cost before

recommending it.

Community & Ongoing Distribution

Most directory submissions are episodic; community participation is ongoing.

Measure each as a separate source before combining funnel conclusions.

Reddit and forums

Read the current rules of each community before recommending or publishing a

link. Participate with relevant firsthand value, disclose affiliation, and use

promotion threads only when the current rules allow it. Membership counts and

recurring-thread availability are volatile; verify them if they affect selection.

Candidate formats include approved firsthand numbers, real screenshots, lessons,

and mini case studies. Test them under the community's current rules rather than

claiming a universal winning format.

LinkedIn

Use the channel when the actual audience and account analytics support it.

Experiment with approved firsthand stories, original research, useful analysis,

and document formats. Set cadence from production capacity and observed response;

do not promise a lead share or engagement multiplier.

Twitter/X (indie hacker + dev channel)

Share authorized technical lessons, decisions, and outcomes where they serve the

audience. Measure referral and search results; do not claim indexing or answer

engine effects in advance.

Indie Hackers

• If current rules permit it, share an authorized build-in-public update around a

relevant launch milestone.

• Test a sustainable cadence for approved revenue, shipping, or lesson updates.
• Build authentic participation before sharing promotional links.

Dev.to + Hashnode

Cross-post only where current terms permit it and use a canonical URL when the

platform supports one. Verify the rendered link and referral results.

KPIs & Tracking

Set baselines and goals from the user's current analytics, eligible audience,

capacity, and launch objective. Do not use generic day-based forecasts.

| Metric | Baseline | User-approved goal | Source and check date |

|---|---:|---:|---|

| Listings submitted and live | | | |

| Verified referring links | | | |

| Directory referral sessions | | | |

| Qualified conversions by listing | | | |

| Review requests and published reviews | | | |

| Search or answer-engine observations | | | |

| Cost and team time | | | |

What NOT to Do

• Don't buy a mass-submission package without diligence and explicit approval. Verify exact destinations, editorial standards, data handling, rights, maximum cost, and refund terms.
• Don't submit to low-quality or deceptive directories. Evaluate audience fit, moderation, live traffic evidence, existing listings, outbound-link behavior, and reputation rather than relying on one authority score.
• Don't submit with the wrong positioning. Re-read the positioning table per tier. Generic descriptions waste the listing.
• Don't treat directories as your entire GTM. Compare them with content, community, reviews, partnerships, and other measured channels.
• Don't run a review campaign from remembered rules. Verify current eligibility, disclosure, and incentive policies first.
• Don't manipulate votes or reviews. Follow the platform's current solicitation rules.
• Don't churn listings without evidence. Set a review cadence from product

changes, platform notices, and observed listing issues.

• Don't submit before the destination page exists. Link equity needs a destination.
• Don't force identical copy into mismatched fields. Keep facts consistent while adapting emphasis and length.

10. Don't lie on comparison pages. Verify material claims and date the comparison.

11. Don't over-index on launch-day spike. The flywheel is templates + alternatives + reviews + ongoing content — not one day of PH.

12. Don't create or change company profiles without authority. When authorized, keep verified entity facts consistent.

Task-Specific Questions

• What are you launching? (Category changes tier mix — AI vs traditional SaaS vs no-code vs dev tool.)
• When is launch day? (Work backward from verified platform requirements.)
• Do you have destination pages built? (Alternatives, use cases, templates — if not, build first.)
• Which flagship surface is being considered, and what do its current rules require?
• How many eligible users could receive a policy-compliant review request?
• Do you have a live tested MCP or agent capability? (If yes, verify compatible registries.)
• Existing integrations? (If yes, verify each owner's marketplace eligibility.)
• Which owned audiences can be contacted, and has the user authorized outreach?
• Current DR and referring domain count? (Baseline for measuring the compounding effect.)

Output Format

When the user asks for a directory plan, return:

• Readiness assessment — which Phase 0 items are missing, which block submission
• Tier selection — which tiers apply, which to skip, why
• Submission order — evidence-backed batches mapped to current requirements
• Destination page list — what to build first if missing
• Positioning variants — the actual copy per tier (from references/positioning-variations.md)
• Flagship listing timeline — mapped from current rules to calendar dates
• Policy-compliant review plan — eligible audience, authorization, copy, cadence
• Weekly measurement plan — baselines and user-approved goals
• Tracker — link to or include the CSV from references/submission-tracker-template.csv

Keep the plan actionable. Every item should be something the user can do today.

Boundaries

• Do not claim a directory is dofollow, indexed, high-authority, or producing leads without a current check.
• Do not submit listings, create accounts, publish copy, buy placements, or request reviews without explicit authorization.
• Do not fabricate traffic, ranking, review, or citation outcomes; label estimates and record the evidence date.
• Do not decide positioning or public product claims when the required product context is missing.

Routing

• Use suede-launch-packaging for the broader launch sequence.
• Use suede-programmatic-seo for destination pages and suede-seo-audit for search or citation checks.
• Use suede-competitors for comparison-page strategy and suede-content-strategy for editorial support.
• Use suede-free-tools for interactive destination assets and suede-community-marketing for community distribution.