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.

Iron Law, approval is per destination:

No external submission, account creation, paid placement, or review request
happens without explicit approval for that exact destination, copy, assets,
timing, and maximum cost. Approval for research or for another destination
never transfers. Any delta is re-approved before it ships.

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.

Workflow

Step 1: Readiness assessment (Phase 0)

Assess the selected directory against current requirements:

1. Is the product publicly accessible (no password wall)?
2. Is there a pricing page (even "free while in beta")?
3. Are privacy policy + terms live?
4. Are the required approved logo, screenshot, and video assets available?
5. Does the destination page match the proposed listing copy and CTA?
6. Is referral and conversion measurement configured?
7. Does the current directory policy allow this product, claim set, and category?
8. For review sites, are there genuine eligible users and a policy-compliant ask?
9. 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. At the block: stop work on that directory, name the blocker in one line ("<directory>: missing <requirement>"), list the resolution options (obtain the requirement, substitute a truthful destination, get explicit submission authority, or drop the directory from the tier), and wait for the user's pick before submitting there. Other gaps are prioritization inputs, not universal launch blockers.

Step 2: Choose the tiers

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

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). Work in evidence-backed approval batches of 3–5 directories. At the cap, submit, verify, and report that batch's results before opening the next one. Every submission is gated by the Iron Law: show the exact public copy, assets, account, destination, timing, and maximum cost first.

Per submission:

1. Verify the current form, rules, price, and account identity.
2. Prepare the exact field values and assets as a reviewable draft.
3. Obtain explicit approval for that destination (Iron Law).
4. Fill and upload only the approved values.
5. Pause before any changed price, upsell, or materially different rendered preview; re-approve the delta.
6. Submit once, then capture confirmation.
7. Log: date, URL, status, moderator notes.
8. Once live, fetch the canonical listing URL, locate the anchor pointing at the destination in the rendered HTML, and record its rel value, redirect behavior, resolved destination, and the check date in the tracker. Absence of rel in response headers does not prove link attributes: inspect the rendered page, and log the method used.

Reporting rule: a listing is reported live only when the tracker's Live URL, Rendered Link Attributes, and Destination Verified cells are all filled with a check date. Anything else is reported as submitted, unverified.

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:

1. Read the current official review and incentive policy for the chosen platform.
2. Record the source URL, check date, eligibility rules, deadlines, and maximum verified cost.
3. Identify real users with firsthand product experience; never manufacture, gate, pre-score, or script reviews.
4. Get explicit authorization for the recipient list, wording, channel, cadence, and any incentive before outreach.
5. 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.